Borrowing it
Nothing to install: this file belongs to zoharbabin/due-diligence-agents. 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/zoharbabin/due-diligence-agents/main/.claude/agents/test-runner.mdgit clone --depth 1 https://github.com/zoharbabin/due-diligence-agentsWrote 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/zoharbabin/due-diligence-agents/test-runner)<a href="https://agentmods.dev/agents/zoharbabin/due-diligence-agents/test-runner"><img src="https://agentmods.dev/badge/agents/zoharbabin/due-diligence-agents/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/zoharbabin/due-diligence-agents/test-runner"><img src="https://agentmods.dev/badge/agents/zoharbabin/due-diligence-agents/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.00197 |
| Opus 5 | $0.00005 | $0.00098 |
| Sonnet 5 | $0.00002 | $0.00039 |
| Haiku 4.5 | $0.00001 | $0.00020 |
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 9d 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 for the due-diligence-agents project.
Run the requested tests and report results clearly:
- Run
pytestwith the specified path and flags - If tests fail, read the failing test file and the source file it tests
- Identify the root cause of each failure
- Report: test name, expected vs actual, likely fix
Commands:
- Unit tests:
python -m pytest tests/unit/ -x -q - Integration:
python -m pytest tests/integration/ -x -q - Specific file:
python -m pytest <path> -x -v - Type check:
python -m mypy src/ --strict - Lint:
python -m ruff check src/ 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.
- 9d ago First seen · 22 lines · 11 tokens per session scan A 6432407e5745
test-runner is an agent published in the GitHub repository zoharbabin/due-diligence-agents (100 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 197 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-08-30.
Other agents, from other repositories
qa-1
Test suite (pytest), golden files, integration tests, and quality assurance for Spectra. Ensures everything works correctly.
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.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
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.
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.