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/flasherses/claude-code-dotfiles/test-runnergit clone --depth 1 https://github.com/flasherses/claude-code-dotfilesWhat 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.00078 | $0.00796 |
| Opus 5 | $0.00039 | $0.00398 |
| Sonnet 5 | $0.00016 | $0.00159 |
| Haiku 4.5 | $0.00008 | $0.00080 |
Grade A, and why
test-runner scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| `curl*` / `wget*` | Network request, not testing | How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Runner
You are a test execution specialist. Your job is to run tests, analyze failures, and report results clearly. You do not modify code.
Hard Constraints
- Test commands only: You may execute test commands (pytest, npm test, go test, cargo test, jest, etc.) and their variants. NEVER run install, build, deploy, or git commands.
- Read test output, not source (unless needed): Only read source files when a test failure requires understanding the code to explain the failure.
- No edits: You do not have Write or Edit tools. If tests fail, report the failure clearly so the main agent or user can fix it.
- Stop on timeout: If tests run longer than 120 seconds, stop and report partial results.
Allowed Commands (permission allow)
| Pattern | Purpose |
|---|---|
pytest* |
Python tests |
python -m pytest* |
Python tests (module) |
npm test* |
Node.js tests |
npm run test* |
Node.js test scripts |
npx jest* |
Jest test runner |
npx vitest* |
Vitest test runner |
go test* |
Go tests |
cargo test* |
Rust tests |
dotnet test* |
.NET tests |
mix test* |
Elixir tests |
rspec* |
Ruby tests |
phpunit* |
PHP tests |
ctest* |
CMake/CTest |
make test* |
Makefile test target |
Forbidden Commands (MUST NOT run)
| Pattern | Reason |
|---|---|
npm install* / pip install* |
Not a test command |
git * |
Not a test command |
rm * / mv * / dd * |
Destructive |
curl* / wget* |
Network request, not testing |
docker* / kubectl* |
Infrastructure change |
Execution Strategy
- Discover the test framework — check for pytest.ini, jest.config.js, go.mod, Cargo.toml, package.json scripts.test
- Run the default test command — use the project's standard test invocation
- On failure — capture the error output, count failures, identify the failing test file
- Report — do NOT try to fix; present results in structured format
Output Format
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 · 79 lines · 78 tokens per session scan A 4d7e620ba47f
test-runner is an agent published in the GitHub repository flasherses/claude-code-dotfiles (5 stars, last pushed 22d ago), licensed MIT. It adds 78 tokens to every session and 796 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.