Borrowing it
Nothing to install: this file belongs to adaline/gateway. 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/adaline/gateway/main/.claude/agents/test-runner.mdgit clone --depth 1 https://github.com/adaline/gatewayWrote 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/adaline/gateway/test-runner)<a href="https://agentmods.dev/agents/adaline/gateway/test-runner"><img src="https://agentmods.dev/badge/agents/adaline/gateway/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/adaline/gateway/test-runner"><img src="https://agentmods.dev/badge/agents/adaline/gateway/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.00018 | $0.00122 |
| Opus 5.5 | $0.00007 | $0.00049 |
| Sonnet 5.5 | $0.00004 | $0.00024 |
| Haiku 4.5 | $0.00002 | $0.00012 |
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 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 for the Gateway monorepo and analyze results.
- Run:
pnpm run test(all) ornpx turbo run test --filter=@adaline/<package> - If tests fail: identify root cause (test bug vs code bug)
- Report: which tests failed, why, and suggested fix
- If all pass: report success with summary
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 · 14 lines · 18 tokens per session scan A 0dd86be6261f
test-runner is an agent published in the GitHub repository adaline/gateway (607 stars, last pushed 3mo ago), licensed MIT. It adds 18 tokens to every session and 122 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-30.
Other agents, from other repositories
gan-evaluator
GAN Harness — Evaluator agent. Tests the live running application via Playwright, scores against rubric, and provides actionable feedback to the Generator.
gan-generator
GAN Harness — Generator agent. Implements features according to the spec, reads evaluator feedback, and iterates until quality threshold is met.
pr-test-analyzer
Review pull request test coverage quality and completeness, with emphasis on behavioral coverage and real bug prevention.
test-strategist
Test strategy and policy expert for the ClosedLoop plugin monorepo. Owns coverage policy, test pyramid decisions, fixture design, golden-fixture regression design, and what kind of test is appropriate for which behavior. Does NOT run pytest or fix failures — that is test-engineer's domain.
build-validator
Discovers and runs project validation commands (test, lint, typecheck, build). Caches discoveries as learnings for future runs.
test-engineer
Specialized in Python testing with pytest. Expert in running tests, fixing failures, and ensuring test coverage. Use when running tests, fixing failing tests, or validating test coverage. Does NOT write new tests - focuses on running and fixing.