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.
npx agentmods add skills/kensaurus/cursor-kenji/plan-test-coveragenpx skills add kensaurus/cursor-kenji --skill plan-test-coveragegit 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/skills/kensaurus/cursor-kenji/plan-test-coverage)<a href="https://agentmods.dev/skills/kensaurus/cursor-kenji/plan-test-coverage"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/plan-test-coverage.svg" alt="Measured on agentmods" 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.00072 | $0.01357 |
| Opus 5 | $0.00036 | $0.00678 |
| Sonnet 5 | $0.00014 | $0.00271 |
| Haiku 4.5 | $0.00007 | $0.00136 |
Grade A, and why
plan-test-coverage 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Coverage Audit + Plan (User-Story-Driven)
Degree of freedom: MIXED — story derivation and fake-green judgment are HIGH; coverage commands run exactly. Stay plan-only. No tests written in this pass.
Role: Senior QA / test engineer.
Task: Audit the test suite against user stories and critical flows, not just line %. Find untested, weakly tested, and fake-green tests. Build traceability matrix + burndown. Audit & plan only — do not write tests in this pass.
This skill vs neighbors
| Skill | Does |
|---|---|
| plan-test-coverage (this) | Story-driven coverage plan |
test-unit |
Write unit/integration tests (execution) |
test-qa |
Live QA crawl |
test-playwright |
E2E verification after changes |
workflow-spec-tdd |
Spec + TDD during feature build |
plan-stub-checker |
Finds unwired UI — feed into critical-path tests here |
Loop position: plan-stub-checker → wiring approval → plan-test-coverage → plan-perf-audit / plan-security-audit → plan-docs-sync
How to reason (every plan item)
- Propose — the given/when/then spec for a gap or a fake-green replacement
- Risk — critical flow ships untested, or a green suite that cannot fail
- Keep-working — stories that already have honest, asserting tests
- Phase — Critical+fake-green → Error-edge → Important → Minor (do not execute)
Worked example
Propose: add an e2e for "authed user exports data" covering the newly wired Settings control; replace
expect(true).toBe(true)inexport.test.ts. Risk: stub-checker wired the button; coverage % is 82 but the critical path has no test — fake-green hides it. Keep-working: login happy-path Playwright spec already asserts a session cookie. Phase: Phase 1 — Critical uncovered + fake-green. Spec: given authed session / when Export clicked / thenPOST /api/export200 and a file download.
⛔ Preservation Contract
Read references/preservation-contract.md. Acknowledge in output #1.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 167 lines · 72 tokens per session scan A a940f0bc5a5c
plan-test-coverage is a skill published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 8d ago), licensed MIT. It adds 72 tokens to every session and 1,357 once invoked, about $0.0004 per session on Opus 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-09-03.
Other skills, from other repositories
agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
patrol-e2e-testing
Use when writing E2E/integration tests, testing native interactions like permissions or system dialogs, capturing UI regressions, or validating cross-platform behavior (Patrol 4.x).
testing
Use when writing or reviewing Flutter/Dart tests (unit, widget, golden), fixing flaky tests, adding coverage, or choosing between unit and widget tests.
133-java-testing-acceptance-tests
Use when you need to implement acceptance tests from maintainer-sanitized Gherkin scenario facts for framework-agnostic Java (no Spring Boot, Quarkus, Micronaut) — confirming @acceptance scenarios before coding, happy path with RestAssured, DB/Kafka test fixtures, WireMock for external REST only, and AT classes run by…
323-frameworks-spring-boot-testing-acceptance-tests
Use when you need to implement acceptance tests from maintainer-authored or maintainer-sanitized Gherkin scenario facts for Spring Boot applications — including selecting scenarios tagged @acceptance, implementing happy path tests with TestRestTemplate, @SpringBootTest, Testcontainers with @ServiceConnection for…
423-frameworks-quarkus-testing-acceptance-tests
Use when you need to implement acceptance tests from maintainer-sanitized Gherkin scenario facts for Quarkus applications — including @acceptance scenarios, @QuarkusTest, BaseAcceptanceTest with QuarkusTestResourceLifecycleManager for Testcontainers and WireMock, REST Assured for full HTTP pipeline testing, WireMock…