Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/kensaurus/cursor-kenjiWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/kensaurus/cursor-kenji/test-plan)<a href="https://agentmods.dev/commands/kensaurus/cursor-kenji/test-plan"><img src="https://agentmods.dev/badge/commands/kensaurus/cursor-kenji/test-plan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/kensaurus/cursor-kenji/test-plan"><img src="https://agentmods.dev/badge/commands/kensaurus/cursor-kenji/test-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00014 | $0.00148 |
| Opus 5.5 | $0.00006 | $0.00059 |
| Sonnet 5.5 | $0.00003 | $0.00030 |
| Haiku 4.5 | $0.00001 | $0.00015 |
Grade A, and why
test-plan scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 27d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Test Coverage Plan
Run the plan-test-coverage skill: build a user-story traceability matrix,
find untested paths and fake-green tests, then produce a coverage plan. Audit
and plan only — write no tests until the plan is approved.
Emit gaps ranked by risk with a phased coverage checklist. After approval,
execute with test-unit, workflow-spec-tdd, and test-playwright.
The full playbook lives in the plan-test-coverage skill.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 27d ago Changed · +2 lines db4371f978d2
- 1mo ago First seen · 16 lines · 14 tokens per session scan A 96f2be5b55c6
test-plan is a command published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 22d ago), licensed MIT. It adds 14 tokens to every session and 148 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
gauntlet-loop
Beat a real-world quality bar via builder/critic loops; critics alone decide when each part passes.
prompt-eval-debug
Debug any prompt with a tiny eval suite (control, edge, boundary), failure diagnosis, and smallest next change, no blind rewrite.
tdd
Canon TDD (specify, encode, fulfill) with one test at a time, approval gates, and kitchen-cleaning refactor when needed.
run-all-tests-and-fix
Run full test suite and fix failures.
write-unit-tests
Write meaningful unit tests for target code.
check-coverage
Check test coverage, identify gaps, and suggest which code needs tests.