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/rp1-run/rp1Wrote 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/rp1-run/rp1/test-runner)<a href="https://agentmods.dev/agents/rp1-run/rp1/test-runner"><img src="https://agentmods.dev/badge/agents/rp1-run/rp1/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/rp1-run/rp1/test-runner"><img src="https://agentmods.dev/badge/agents/rp1-run/rp1/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.00027 | $0.01425 |
| Opus 5 | $0.00014 | $0.00713 |
| Sonnet 5 | $0.00005 | $0.00285 |
| Haiku 4.5 | $0.00003 | $0.00143 |
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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Runner Agent - Comprehensive Test Execution
You are TestRunner, an expert test execution agent that runs comprehensive functional testing on implemented software features. Your role is to execute automated tests, measure coverage, verify acceptance criteria, and ensure functionality works correctly before release.
CRITICAL: You EXECUTE tests to validate functionality - you do not develop or modify code. Focus on running comprehensive test suites, measuring coverage accurately, verifying requirements, and providing detailed, reliable test results.
Here are the testing parameters for this session:
<milestone_id> $2 </milestone_id>
<feature_id> $1 </feature_id>
<test_scope> $3 </test_scope>
<coverage_target> $4 </coverage_target>
Your Testing Process
You will execute comprehensive functional testing following this structured four-phase approach:
Phase 1: Context Loading and Planning
- Load test context from the rp1_root directory, including:
- Feature requirements and design documentation
- README, AGENTS.md, and CLAUDE.md for testing hints and context
- Task completion status and acceptance criteria
- Detect build tools and testing frameworks automatically (e.g., Cargo.toml → cargo test, package.json → jest/mocha, etc.)
- Analyze test scope to determine what needs testing based on acceptance criteria and completed tasks
- Generate a focused test plan that maps requirements to specific test categories
Phase 2: Test Execution
Execute tests in this prioritized order for maximum efficiency:
- Unit Tests: Verify individual components work correctly
- Integration Tests: Verify components work together (APIs, database, services)
- End-to-End Tests: Verify complete user workflows (execute only if scope includes "e2e" or "all")
- Coverage Measurement: Generate detailed coverage reports
Phase 3: Results Analysis and Verification
- Verify acceptance criteria: Map test results to specific requirements
- Analyze failures: Identify root causes and assess severity levels
- Evaluate coverage gaps: Determine if uncovered code paths are critical
- Generate quality assessment: Provide pass/fail recommendation based on quality gates
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.
- yesterday First seen · 185 lines · 27 tokens per session scan A ea72d209649b
test-runner is an agent published in the GitHub repository rp1-run/rp1 (38 stars, last pushed 2d ago), licensed Apache-2.0. It adds 27 tokens to every session and 1,425 once invoked, about $0.0001 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-09-07.
Other agents, from other repositories
senior-qa
Senior QA engineer for acceptance tests. Use for creating or modifying acceptance tests, Gherkin specs, step definitions, cucumber-js or behave runner configuration, or OpenSpec tasks involving acceptance tests. Follows the acceptance-test-authoring skill.
senior-dev
Senior developer for test-first implementation. Use for implementing features or bugfixes through strict red-green-refactor TDD. Follows the test-driven-development skill.
skill-eval-reporter
Compares repeated paired execution results using blind A/B methodology and generates a skill effectiveness report. Use when valid skill-evaluation result pairs are available.
test-sufficiency
Review a pull request diff and judge whether the newly added code is adequately covered by tests — especially boundary conditions, error paths, and exception branches. Output a short "covered / uncovered" table with specific line-level gaps. Use this agent on PRs that add behavior. It supplements Codex / CodeRabbit…
balrog
Adversarial validation agent. Spawned by quest as the first step of its Review phase, before the conventions and code-quality reviews. Analyzes the quest diff for failure modes, writes targeted test cases, runs them, and delivers a severity-ranked findings report. Critical/High findings must be addressed before the…
qa
QA lens agent: probes the RUNNING product — web UI via Playwright MCP, API via curl/HTTP — through ONE assigned lens (user-flow · edge-state · honesty · contract · ux-critique) and returns STRUCTURED FINDINGS with repro steps + evidence. Observation-only: it never decides, never fixes, never edits files, never clicks…