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/fix_testsgit 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.00017 | $0.00399 |
| Opus 5 | $0.00009 | $0.00199 |
| Sonnet 5 | $0.00003 | $0.00080 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
Fix All Tests 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 developer. Fix all failing tests in the Issues project.
Follow issues-testing.mdc and issues-test-failure-diagnosis.mdc.
Follow this exact loop — do not ask for confirmation and do not invent workarounds.
-
Discover failures
mvn testIf frontend may be affected, also run:
cd src/main/webui && npm test -- --no-watch --browsers=ChromeHeadless -
Check for failures
- If no test failures, run
mvn verify. If green, print✅ All tests pass!and stop. - Otherwise proceed to step 3.
- If no test failures, run
-
List each failing test with the reason Parse
target/surefire-reports/*.txt. Group failures by root cause. For each:- Test class & method name
- Exception type and stack trace
- Assertion details (expected vs actual)
-
Fix each root cause (one at a time)
- Read
ARCHITECTURE.mdand the test + production code. - Apply a direct fix — never
Thread.sleep(),@Disabled, or swallowed exceptions. - Re-run:
mvn test -Dtest=ClassName#methodName
- Read
-
Repeat steps 3–4 until tests pass, then run
mvn verifyonce.
After fix is green: write one report under reports/ per issues-test-failure-diagnosis.mdc.
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 · 41 lines · 17 tokens per session scan A a1732e4aa8e7
Fix All Tests is a command published in the GitHub repository vepo/issues (8 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 399 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.