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.
npx agentmods add agents/zenobia0000/ai-agentic-coding-template_unified/test-runnergit 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.svg" alt="Measured on agentmods" 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 | $0.00021 | $0.00622 |
| Opus 5 | $0.00010 | $0.00311 |
| Sonnet 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 3d 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.
- 3d 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 4mo ago), licensed MIT. It adds 21 tokens to every session and 622 once invoked, about $0.0001 per session on Opus 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.