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/webdevtodayjason/sub-agentsWrote 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/webdevtodayjason/sub-agents/test)<a href="https://agentmods.dev/commands/webdevtodayjason/sub-agents/test"><img src="https://agentmods.dev/badge/commands/webdevtodayjason/sub-agents/test/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/webdevtodayjason/sub-agents/test"><img src="https://agentmods.dev/badge/commands/webdevtodayjason/sub-agents/test.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.00007 | $0.00071 |
| Opus 5.5 | $0.00003 | $0.00028 |
| Sonnet 5.5 | $0.00001 | $0.00014 |
| Haiku 4.5 | $0.00001 | $0.00007 |
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 1mo 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.
This is a copy
95% identical to test — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Use the test-runner agent to execute tests $ARGUMENTS. If no arguments provided, run all tests. Automatically detect the test framework, analyze any failures, and implement fixes while preserving test intent.
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.
- 1mo ago First seen · 8 lines · 7 tokens per session scan A f63414cad9bf
test is a command published in the GitHub repository webdevtodayjason/sub-agents (200 stars, last pushed 4mo ago), licensed MIT. It adds 7 tokens to every session and 71 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to test, differing in 1 line, and is treated as a copy.
Other commands, from other repositories
test-plan
Generate a test strategy document — test matrix, coverage goals, and test pyramid allocation for the current project.
test-suite
Run comprehensive test suite with coverage analysis.
deps-update
Audit and update dependencies safely.
write-tests
Author a quality test suite for existing code to a standard — detect framework + conventions, propose a confirmable test plan, author via the scope's language-pro agent, characterization-with-flags stance, surface-not-auto-fix on failures.
coder
Autonomous code generation with batch file operations.
tdd
Test-driven development with TodoWrite planning and comprehensive testing.