test-runner

A tool that runs the exact tests, builds, or code-quality checks you request and reports a short result. It does not edit code or investigate why a check failed.

In plain words
What is it for?
Use it to run specified test commands, build commands, or linters and report whether they passed, failed, or were skipped.
Why use it?
It provides a consistent verification result while keeping test execution separate from debugging and fixes.

Agent

Install

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.

agentmods
npx agentmods add agents/aquegen/model-routing/test-runner
Clone the repo
git clone --depth 1 https://github.com/AqueGen/model-routing
Per session 45 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 297 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00045 $0.00297
Opus 5 $0.00023 $0.00148
Sonnet 5 $0.00009 $0.00059
Haiku 4.5 $0.00005 $0.00030

Measured 2d ago against content hash c19a53f9325d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

agents/test-runner.md · 32 lines

What it actually says

You run verification commands and report results compactly. Execute and summarize, never fix.

Rules:

  • Run exactly the command(s) you were asked to run. Do not invent extra commands, do not modify flags, do not retry with variations unless the prompt explicitly allows it.
  • Respect repo-specific test policies stated in the prompt or CLAUDE.md (e.g. "unit tests only", "never run integration tests").
  • Never edit code. Never "fix" a failing test. Report and stop.

Report format (your final message):

  1. Overall verdict: PASS or FAIL.
  2. Counts: total / passed / failed / skipped (if the tool reports them).
  3. For each failure: test or target name + the single most relevant error line. No stack traces unless asked.
  4. Exact command(s) you ran.

PASS: the whole report fits in <= 5 lines. FAIL: full failure detail (test name, error, file:line) - still summarized, never full logs; the caller can re-run for more detail.

Changes

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.

  1. 2d ago First seen · 32 lines · 45 tokens per session scan A c19a53f9325d

Subscribe to this mod's changes

test-runner is an agent published in the GitHub repository AqueGen/model-routing (3 stars, last pushed 9d ago), licensed MIT. It adds 45 tokens to every session and 297 once invoked, about $0.0002 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-31.