In short:
ak-testworks out what a change has to prove, runs the smallest check you can trust, investigates every failing test, then states exactly what was checked. If it passes, it hands off toak-git. If a failure needs deeper investigation, it hands off toak-debug. It never turns tests green by loosening them.
Disclosure: I maintain AgentKit and have an affiliate relationship with it: the AgentKit link in this post is an affiliate link; buying through it gets you 30% off.
Summary
Use it when you just finished a feature or fixed a bug and need evidence that it works. Beyond running tests, you can use it to create, optimize and audit a whole test suite.
flowchart LR
A["ak-cook or ak-fix done"] --> B["ak-test"]
B --> C["Tests pass within scope"]
C --> D["ak-git"]
B --> E["Failing test needs deeper investigation"]
E --> F["ak-debug"]
B --> G["create, optimize, audit the suite"]On every run, it answers 4 questions:
| Point | Question | Example |
|---|---|---|
| The contract to prove | What must this change get right, and per which requirement? | The API returns 403 when a user accesses another workspace, per the permissions spec |
| The lowest layer you can trust | Which smallest check proves it? | Discount logic is checked with a unit test, no browser needed |
| Can a past result be reused | Does the previous run still match the current code? | Tests passed yesterday but files changed today without a commit, so it reruns |
| Five operations | Do you want to run tests, test the UI, or create, optimize or audit the suite? | /ak-test with a description, ui with a URL, create, optimize, audit with a scope |
The report always opens with the verdict: checked within scope, violation found, or not enough evidence. A required check that was skipped never counts as a pass, and a rerun does not erase the first failure.
Sample prompt for checking after you finish coding:
/ak-test Check the per-plan pricing change in <billing module>.
Expected: the Pro plan gets 20% off, the Free plan price stays the same.
Constraint: do not edit existing tests to match the new results.The three flags below only apply to create, optimize, audit:
| Flag | What it is for | Since ak |
|---|---|---|
--advice | An advisor agent reviews at key checkpoints | 2.13.0 |
--ultra | 5 independent analyses, one judging step | 2.13.0 |
--interview | Approve each group of changes before it is applied | 2.13.0 |
Below is the detailed version: the run flow, 5 situations with prompts, each flag explained (when to use it, when you do not need it, what you get, which flags it combines with), the change history by ak release, and common pitfalls. The detailed version and the interactive page are for subscribers. Your agent can also search them through the portal's MCP.
Opens when your account has subscriber access
This guide is for subscribers
Once your account has access, the full piece, the interactive visual and the agent call all open.
- Sign in or create a modernEngineer accountReading access belongs to your account email.
- Choose a plan on the pricing page1, 3 or 12 months, paid by VietQR bank transfer. Access opens about a minute after the money arrives.
- Or redeem a Facebook subscriber codePeople supporting the page on Facebook get an activation code by message each month.
Already a subscriber? Sign in to read.
Use this piece in your agent
Get an API keyCopy the text below and paste it into Claude Code, Codex or whichever agent you use. The agent reads the piece and checks it against the repo you have open.
Read "ak-test: run the right tests, report what was checked" on modernEngineer and apply it to this repo.
1. Call the content_get tool of the modernengineer MCP server with locale "en", slug "ak-test". If the modernengineer MCP server is not connected, stop and walk me through connecting it from https://modernengineer.dev/en/mcp.
2. Summarize the main steps of the piece and point out which apply to this repo.
3. Propose concrete changes and ask me before editing any file.Connect MCP in Claude Code (once)
claude mcp add --transport http modernengineer \
https://api.modernengineer.dev/mcp \
--header "Authorization: Bearer <API key>"Reading the full piece over MCP needs an API key from a subscriber account or one that bought this guide. Without access, the agent only gets the opening.
- Version
- v1.0.0
- Updated
- 22/10/2026
- Licence
- All rights reserved
- Slug
- ak-test
