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/jjmartres/ai-coding-agents/testgit clone --depth 1 https://github.com/jjmartres/ai-coding-agentsWhat 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.00004 | $0.00119 |
| Opus 5 | $0.00002 | $0.00060 |
| Sonnet 5 | $0.00001 | $0.00024 |
| Haiku 4.5 | $0.00000 | $0.00012 |
Grade A, and why
test 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
Detect and run the appropriate test command:
- If a
Makefileexists at the project root:- Run
make test-in-ciif the target exists - Otherwise fall back to
make test
- Run
- If no
Makefileexists, runpytest --coverage(or the project's native test runner if identifiable from config files)
Always show the full coverage report.
For every failing test:
- Show file, line, and error message
- Diagnose the root cause
- Propose a concrete fix
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 · 19 lines · 4 tokens per session scan A 300368297594
test is a command published in the GitHub repository jjmartres/ai-coding-agents (43 stars, last pushed 2mo ago), licensed MIT. It adds 4 tokens to every session and 119 once invoked, about $0.0000 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-30.
Other commands, from other repositories
publish
Release a new package version — semver bump from commits, tag, registry publish, GitHub Release.
rebase
Rebase the current branch on main, a local branch, or a remote branch (with fetch).
python-review
Comprehensive Python code review for PEP 8 compliance, type hints, security, and Pythonic idioms. Invokes the python-reviewer agent.
test-coverage
Analyze test coverage, identify gaps, and generate missing tests to reach 80%+ coverage.
release
Bump version, update CHANGELOG.md, and prepare a release.
fix-issue
Investigate and fix a GitHub issue.