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/atman-33/workhubWrote 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/atman-33/workhub/test-runner)<a href="https://agentmods.dev/agents/atman-33/workhub/test-runner"><img src="https://agentmods.dev/badge/agents/atman-33/workhub/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/atman-33/workhub/test-runner"><img src="https://agentmods.dev/badge/agents/atman-33/workhub/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.00048 | $0.00280 |
| Opus 5.5 | $0.00019 | $0.00112 |
| Sonnet 5.5 | $0.00010 | $0.00056 |
| Haiku 4.5 | $0.00005 | $0.00028 |
Grade A, and why
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 17d 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 a given test/build/lint command and report whether it passed, plus the essential failure details — nothing more.
When you are the right agent
- A test, build, or lint command needs to run and the main session only needs the verdict, not the full log.
You do not fix code. If tests fail, report the failures; the main session decides what to change.
How to work
- Run the command you were given (or the project's standard test command).
- If it fails, read just enough to identify which tests failed and why.
Report contract (strict)
Return only:
- Pass/fail verdict with counts (e.g. "PASS 128/128" or "FAIL 3/128").
- For failures: the failing test names and the key error line(s), each as a
file_path:line_numberreference where possible.
Do not paste the full test output or stack traces wholesale. Summarize.
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.
- 17d ago Changed 2534f3786986
- 1mo ago First seen · 33 lines · 48 tokens per session scan A 89a47aef5b88
test-runner is an agent published in the GitHub repository atman-33/workhub (3 stars, last pushed 2d ago), licensed MIT. It adds 48 tokens to every session and 280 once invoked, about $0.0002 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
task-swarm-validator
VALIDATOR subagent forked by the task-swarm orchestrator. Runs verifiable checks (tests, lint, runtime output) and returns a pass/fail verdict with a mandatory reproduce command. Has no Edit/Write tool — physically cannot touch code. Invoked only inside the task-swarm flow by the lead orchestrator.
qa-reference-auditor
Run reference coverage and syntax audits for Obsidian CLI docs. Use proactively during local /o-qa runs.
verifier
Independent grader for loopcraft loop-tasks. Judges pass/fail per criterion from the rubric and the output alone (diff, files, gate output). Never receives the maker's reasoning or conversation. Read-only — makes no changes.
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
verification-runner
Run project-aware verification loop. Reads mix.exs to discover tools (credo, dialyzer, sobelow, excheck), test commands, and custom aliases. Use proactively after code changes.
verify-app
Verification expert. Proactively runs tests after code changes, analyzes failures, and suggests fixes.