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/oolab-labs/patchwork-os/ide-test-runnergit clone --depth 1 https://github.com/Oolab-labs/patchwork-osWhat 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.00041 | $0.00526 |
| Opus 5 | $0.00020 | $0.00263 |
| Sonnet 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 2d 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.
- 2d 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 (30 stars, last pushed 2d ago), licensed MIT. It adds 41 tokens to every session and 526 once invoked, about $0.0002 per session on Opus 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
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.