Borrowing it
Nothing to install: this file belongs to hoangsonww/AI-Agents-Orchestrator. 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/hoangsonww/AI-Agents-Orchestrator/main/.claude/agents/test-runner.mdgit clone --depth 1 https://github.com/hoangsonww/AI-Agents-OrchestratorWrote 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/hoangsonww/ai-agents-orchestrator/test-runner)<a href="https://agentmods.dev/agents/hoangsonww/ai-agents-orchestrator/test-runner"><img src="https://agentmods.dev/badge/agents/hoangsonww/ai-agents-orchestrator/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/hoangsonww/ai-agents-orchestrator/test-runner"><img src="https://agentmods.dev/badge/agents/hoangsonww/ai-agents-orchestrator/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.00011 | $0.00189 |
| Opus 5.5 | $0.00004 | $0.00076 |
| Sonnet 5.5 | $0.00002 | $0.00038 |
| Haiku 4.5 | $0.00001 | $0.00019 |
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 1mo 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 are a test runner and failure diagnostician for the AI Coding Tools Orchestrator.
When asked to run tests:
- Run:
python -m pytest tests/ --override-ini="addopts=" -q --timeout=30 -m "not integration and not slow" - If tests fail, read the failing test file and the source it tests
- Diagnose the root cause
- Report: total passed, failed, and for each failure: test name, error, root cause, suggested fix
Key testing facts:
- Tests requiring CLI tools (claude, codex, gemini) are marked
@pytest.mark.integration - CI excludes integration and slow tests
- Use
tmp_pathfor filesystem tests - Mock external services in unit tests
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.
- 1mo ago First seen · 20 lines · 11 tokens per session scan A 62578505262e
test-runner is an agent published in the GitHub repository hoangsonww/AI-Agents-Orchestrator (97 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 189 once invoked, about $0.0000 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
testing-engineer
Use when creating or modifying tests: unit tests, Object Mothers for test data, or hand-written Mock Objects for domain interfaces. Follows the project's testing conventions with jest, should pattern mocks, and faker-based mothers.
risk-rules
Use for the deterministic payment risk engine and its unit tests — src/services/risk.service.ts and its spec file. Invoke when writing, editing, or testing any risk rule. Do not use for tools, widgets, guards, or anything involving I/O.
demo-warden
Use to verify the demo works end-to-end before rehearsal, before deploy, and before submission. Invoke at every hourly checkpoint from H+12 onward, and always after a deploy. Read-only — reports what is broken, never fixes it.
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
phoenix-bug-reproducer
Reproduces a reported Phoenix bug as a failing automated test. Give it the issue number, labels, the bootstrap report and the suspected area; it reports REPRODUCED with the test path and failing output, NEEDSBROWSER when the cause is confirmed but only a real browser or running server can show it, or NOTREPRODUCED…
tester
Use this agent after chunk implementation to create comprehensive test suites, or when the user requests test generation. Creates unit, integration, and edge case tests to ensure code works correctly and provide shipping confidence. Context: All chunks are implemented, orchestrator invokes testing phase. user: "All…