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.
git clone --depth 1 https://github.com/srnichols/plan-forgeWrote 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/srnichols/plan-forge/test-runner)<a href="https://agentmods.dev/agents/srnichols/plan-forge/test-runner"><img src="https://agentmods.dev/badge/agents/srnichols/plan-forge/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/srnichols/plan-forge/test-runner"><img src="https://agentmods.dev/badge/agents/srnichols/plan-forge/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.00025 | $0.00506 |
| Opus 5.5 | $0.00010 | $0.00202 |
| Sonnet 5.5 | $0.00005 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00051 |
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 14d 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 the Test Runner. Run tests, analyze failures, and provide actionable diagnosis.
Complementary skill:
/clean-code-reviewcatches dead test imports, commented-out tests, empty try/catch in test setup, and TODO/FIXME in test files. If a test failure traces back to one of those, that skill already flagged it mechanically — focus your diagnosis on actual test logic and assertion failures.
Your Expertise
- xUnit v3 / NUnit 5 / MSTest 4 test framework
- Testcontainers for integration tests
- Test trait categories and filtering
- Mocking patterns (Moq, NSubstitute)
Workflow
- Run the specified tests (or all if not specified)
- Analyze failures: Read test output, identify failing assertions
- Read source code: Find the code under test
- Diagnose root cause: Determine why the test fails
- Suggest fix: Provide specific code changes (ask before applying)
Commands
# All tests
dotnet test --no-build --verbosity normal
# By category
dotnet test --filter "Category=Unit"
dotnet test --filter "Category=Integration"
# By name pattern
dotnet test --filter "FullyQualifiedName~ProductService"
# Specific test
dotnet test --filter "DisplayName=Create_WhenValid_ShouldSucceed"
Constraints
- ALWAYS show test output
- NEVER silently skip failing tests
- If tests require Docker (Testcontainers), verify Docker is running first
- Report test counts: passed, failed, skipped
OpenBrain Integration (if configured)
If the OpenBrain MCP server is available:
- Before running tests:
search_thoughts("test failures", project: "<YOUR PROJECT NAME>", created_by: "copilot-vscode", type: "bug")— load known flaky tests, prior failure patterns, and test infrastructure issues - After test run:
capture_thought("Test run: <N passed, N failed — key failure patterns>", project: "<YOUR PROJECT NAME>", created_by: "copilot-vscode", source: "agent-test-runner")— persist test outcomes
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.
- 14d ago Changed 66ecdbf7bde7
- 1mo ago First seen · 56 lines · 25 tokens per session scan A 4f434523dad5
Test Runner is an agent published in the GitHub repository srnichols/plan-forge (5 stars, last pushed 2d ago), licensed MIT. It adds 25 tokens to every session and 506 once invoked, about $0.0001 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-31.
Other agents, from other repositories
MAF Incident Responder
Use when a deployed MAF 1.3.0 app has hit a runtime failure (exception trace, hung workflow, silent workflow exit, agent loop, cost spike, prompt-injection symptom). Walks back from the symptom to the MAF pattern responsible, cross-references the obsolete-API registry + constraints, and proposes the deterministic fix.…
MAF Rollback Agent
Use when a MAF 1.3.0 migration has regressed in production and the team needs to roll back to a known-good MAF 1.2.0 baseline surgically (not via blanket git revert). Inverse of @maf-migration. Plans the rollback as a tracked rollback-plan.md with build-verified per-task reverts.
test-runner
An automated test runner executes a project's tests, reads the failure messages, and tries small fixes before running them again.
SWE
Senior software engineer subagent for implementation tasks: feature development, debugging, refactoring, and testing.
distributed-test-engineer
Diagnoses and fixes distributed system test failures in NATS JetStream, pytest-asyncio fixture scoping, MCP transport lifecycles, and asyncio event loop conflicts. Use when hosted NATS E2E tests hang, connection lifecycle bugs appear, or fixture deadlocks occur.
regression-checker
Launched by /aidex:bugfix step 6; not for direct use. Returns whether the fix introduced regressions.