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 commands/vepo/issues/increase_coveragegit clone --depth 1 https://github.com/vepo/issuesWhat 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 | $0.00018 | $0.00322 |
| Opus 5 | $0.00009 | $0.00161 |
| Sonnet 5 | $0.00004 | $0.00064 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
Increase Code 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.
What it actually says
You are an expert Java test engineer for Issues. Raise both JaCoCo instruction and branch coverage (target ≥ 80% unless pom.xml defines other thresholds).
Loop
-
Measure
mvn clean verify jacoco:reportReport:
target/jacoco-report/jacoco.xmland HTML undertarget/site/jacoco/. -
Check thresholds Stop when both ≥ 80%: print
✅ Coverage target reached!Otherwise list 5 lowest branch-coverage classes (min 20 instructions).
-
Per class
- Prefer removing genuinely dead code over testing unreachable paths.
- Add
*Test.javaundersrc/test/java/dev/vepo/issues/. - Every test method must assert return values, state changes, or error paths.
- Run single test:
mvn test -Dtest=ClassName#methodName
-
Re-measure after each class:
mvn verify jacoco:report -
Repeat until targets met.
Rules
- Do not delete or weaken existing assertions.
- Record instruction % and branch % in
reports/coverage_log-{sequential}-{dd-MM-yyyy-HH-mm-ss}.md. - Follow issues-testing.mdc for test placement.
Start the loop now.
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 · 38 lines · 18 tokens per session scan A f17423b4a4fc
Increase Code Coverage is a command published in the GitHub repository vepo/issues (8 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 18 tokens to every session and 322 once invoked, about $0.0001 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-08-31.
Other commands, from other repositories
plan
Run /plan — see .claude/commands/plan.md for the authoritative spec.
wire-harness
Run /wire-harness — see .claude/commands/wire-harness.md for the authoritative spec.
build
Run /build — see .claude/commands/build.md for the authoritative spec.
ship
Run /ship — see .claude/commands/ship.md for the authoritative spec.
onboard
Run /onboard — see .claude/commands/onboard.md for the authoritative spec.
review
Run /review — see .claude/commands/review.md for the authoritative spec.