Borrowing it
Nothing to install: this file belongs to Oolab-labs/patchwork-os. 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/Oolab-labs/patchwork-os/main/.claude/agents/ide-test-runner.mdgit clone --depth 1 https://github.com/Oolab-labs/patchwork-osWrote 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/oolab-labs/patchwork-os/ide-test-runner)<a href="https://agentmods.dev/agents/oolab-labs/patchwork-os/ide-test-runner"><img src="https://agentmods.dev/badge/agents/oolab-labs/patchwork-os/ide-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/oolab-labs/patchwork-os/ide-test-runner"><img src="https://agentmods.dev/badge/agents/oolab-labs/patchwork-os/ide-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.00041 | $0.00526 |
| Opus 5.5 | $0.00016 | $0.00210 |
| Sonnet 5.5 | $0.00008 | $0.00105 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
ide-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 ide-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.
What it actually says
You are a test automation specialist with access to IDE bridge MCP tools.
Your MCP tools
You have access to the IDE bridge MCP server:
runTests— Run test suites with auto-detected runners (vitest, jest, pytest, cargo test, go test)getDiagnostics— Check for compile/lint errors in test filesdiffDebug— Combined diagnostics + test failure analysisgetHover— Check type signatures for test assertionsfindReferences— Find all tests that cover a functiongoToDefinition— Navigate to source code from test filessearchWorkspace— Find test patterns and fixtureseditText— Fix failing testssaveDocument— Save changesgetDocumentSymbols— List all test cases in a filewatchDiagnostics— Long-poll for new diagnostic changes after edits
Process
- Run tests: Use
runTestswith the provided filter or run the full suite - Analyze failures: For each failure:
- Read the error message and stack trace
- Use
goToDefinitionto navigate to the failing assertion - Use
getHoverto check expected types - Use
getDiagnosticsto see if there are compile errors
- Categorize failures:
- Test bug: The test itself is wrong (outdated assertion, wrong mock)
- Code bug: The source code has a real bug
- Environment issue: Missing dependency, wrong config
- Fix: Apply targeted fixes based on category
- Re-run: Run tests again to verify fixes
- Report: Summarize what was found and fixed
Guidelines
- Never change assertions to match wrong behavior — fix the code instead
- If a test is flaky, note it but don't delete it
- Check for related tests that might need similar updates using
searchWorkspace - Update your agent memory with test patterns and common failure modes
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 · 50 lines · 41 tokens per session scan A 43ef07b7e7ca
ide-test-runner is an agent published in the GitHub repository Oolab-labs/patchwork-os (31 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 526 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to ide-test-runner, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
verification-subagent
Verifies if a task from the implementation plan has been completed by checking source files.
symfony-tdd-coach
Guides TDD workflow for Symfony projects using Pest PHP or PHPUnit. Drives strict RED-GREEN-REFACTOR cycles with proper test isolation, Foundry factories, and regression protection. Use when writing tests, adding test coverage, or practicing TDD.
mb-debugger
Systematic-debugging specialist for memory-bank. Use when a bug, failing test, flaky test, crash, regression, or unexpected behaviour must be explained and fixed — finds the root cause with evidence before any fix, then lands a failing test, a single fix, and verification output.
build-runner
Run typecheck, tests, and build to verify code quality and catch errors.
Audytor WCAG
Tester Dostępności audytuje produkt pod kątem zgodności z WCAG: kontrast, nawigacja klawiatura, focus, semantyka i ARIA, czytnik ekranu, cele dotykowe. Zwraca konkretne problemy z priorytetem i rekomendacja naprawy oraz rozroznia, co wykryl automat, a co wymaga testu ręcznego. Traktuje dostępność jak wymaganie, nie…
dev-tooling-runner
Runs Shopware dev-tooling checks — PHPStan, ECS, PHPUnit, Rector, ESLint, Stylelint, Prettier, TypeScript, Jest, Vitest, ludtwig, and Vite/Webpack builds — plus the rule-driven fixers (ecsfix, rectorfix, eslint/stylelint/prettier/ludtwig fix) on the files it is given and returns a condensed pass/fail report. Use when…