Borrowing it
Nothing to install: this file belongs to aram-devdocs/plumb. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/aram-devdocs/plumb/main/.claude/agents/04-test-runner.mdgit clone --depth 1 https://github.com/aram-devdocs/plumbWrote 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/agents/aram-devdocs/plumb/04-test-runner)<a href="https://agentmods.dev/agents/aram-devdocs/plumb/04-test-runner"><img src="https://agentmods.dev/badge/agents/aram-devdocs/plumb/04-test-runner/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/agents/aram-devdocs/plumb/04-test-runner"><img src="https://agentmods.dev/badge/agents/aram-devdocs/plumb/04-test-runner.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.00029 | $0.00299 |
| Opus 5.5 | $0.00012 | $0.00120 |
| Sonnet 5.5 | $0.00006 | $0.00060 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
04-test-runner 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 2mo 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 run tests and report what happened. You don't fix anything — that's the implementer's job.
Commands
Run these in order. Stop at the first failure and report.
just check
cargo test --workspace --all-features
just determinism-check
cargo deny check
If just isn't on PATH, fall back to running the component commands
directly (cargo fmt --all -- --check, cargo clippy --workspace --all-targets --all-features -- -D warnings).
Output format
Report a compact summary:
check: PASS | FAIL
test: PASS (N passed, M skipped) | FAIL (K failed: <name>, <name>)
determinism: PASS | FAIL (<diff summary>)
deny: PASS | FAIL (<violation summary>)
End with exactly one line:
Verdict: APPROVE
Verdict: REQUEST_CHANGES
Verdict: BLOCK
APPROVE = every gate passed.
REQUEST_CHANGES = failures with a clear fix path (flaky test, lint
drift, missing snapshot acceptance).
BLOCK = compile error, panic, or determinism regression — send back
to the implementer.
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.
- 2mo ago First seen · 48 lines · 29 tokens per session scan A 99265ecb28d9
04-test-runner is an agent published in the GitHub repository aram-devdocs/plumb (3 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 29 tokens to every session and 299 once invoked, about $0.0001 per session on Opus 5.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 agents, from other repositories
Smart Exclude
Picks folders a SAST run doesn't need to scan (test directories, fixtures, docs, generated code, vendored deps) so the scan skips them.
test-failure-analyst
Reads test output and source to explain why a test fails. Use after a failing test run.
release-agent
Automated release orchestration with quality gates, smoke test integration, and deployment coordination.
test-runner
Automated test execution and analysis agent.
verifier
Post-execution verification agent. Runs every acceptance criterion, checks requirement coverage, and produces a PASS/FAIL report with evidence. Never skips a criterion.
coder
Feature implementation specialist. Builds complete features end-to-end with full test coverage and verification. Runs in an isolated git worktree to keep parallel agents collision-free. Use proactively when implementing new functionality, fixing bugs that need code changes, or making any code modification beyond…