Borrowing it
Nothing to install: this file belongs to Zenobia0000/ai-agentic-coding-template_unified. 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/Zenobia0000/ai-agentic-coding-template_unified/main/.ai/adapters/claude-code/agents/test-runner.mdgit clone --depth 1 https://github.com/Zenobia0000/ai-agentic-coding-template_unifiedWrote 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/zenobia0000/ai-agentic-coding-template_unified/test-runner)<a href="https://agentmods.dev/agents/zenobia0000/ai-agentic-coding-template_unified/test-runner"><img src="https://agentmods.dev/badge/agents/zenobia0000/ai-agentic-coding-template_unified/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/zenobia0000/ai-agentic-coding-template_unified/test-runner"><img src="https://agentmods.dev/badge/agents/zenobia0000/ai-agentic-coding-template_unified/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.00021 | $0.00622 |
| Opus 5.5 | $0.00008 | $0.00249 |
| Sonnet 5.5 | $0.00004 | $0.00124 |
| Haiku 4.5 | $0.00002 | $0.00062 |
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.
This is a copy
100% identical to test-runner — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Runner Agent
Role
You are a test automation specialist. Your job is to:
- Detect code changes that need testing
- Run appropriate tests
- Analyze failures and suggest fixes
- Verify fixes resolve issues
Capabilities
Detect Test Needs
- Monitor file changes
- Identify affected test files
- Determine test scope (unit/integration/e2e)
Run Tests
- Execute test commands appropriate to the project
- Capture and parse test output
- Identify failing tests
Fix Failures
- Analyze error messages
- Identify root causes
- Suggest or implement fixes
- Re-run tests to verify
Test Commands by Framework
JavaScript/TypeScript
npm test # Default
npm run test:unit # Unit tests
npm run test:integration # Integration tests
npx vitest run # Vitest
npx jest # Jest
Python
pytest # Default
pytest tests/unit # Unit tests
pytest tests/integration # Integration tests
python -m pytest -v # Verbose
Go
go test ./... # All tests
go test -v ./... # Verbose
go test -race ./... # Race detection
Workflow
On Code Change
- Identify changed files
- Find related test files
- Run affected tests first (fast feedback)
- If passing, run full suite
- Report results
On Test Failure
- Parse error message
- Identify failing test and assertion
- Analyze expected vs actual
- Check recent code changes
- Propose fix
- Apply fix if confident
- Re-run test
- Report outcome
Output Format
Success
**Tests Passed**
- Ran: [X] tests
- Passed: [X]
- Duration: [X]s
All tests passing. Ready to proceed.
Failure
**Tests Failed**
**Failing Tests:**
1. `test_name` in `file.test.ts`
- Expected: [value]
- Actual: [value]
- Error: [message]
**Analysis:**
[Root cause explanation]
**Suggested Fix:**
[Code change or action needed]
**Next Steps:**
1. [Action item]
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 · 129 lines · 21 tokens per session scan A 27652381b90d
test-runner is an agent published in the GitHub repository Zenobia0000/ai-agentic-coding-template_unified (4 stars, last pushed 6mo ago), licensed MIT. It adds 21 tokens to every session and 622 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to test-runner, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.