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-debuggergit 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.00046 | $0.00511 |
| Opus 5 | $0.00023 | $0.00255 |
| Sonnet 5 | $0.00009 | $0.00102 |
| Haiku 4.5 | $0.00005 | $0.00051 |
Grade A, and why
ide-debugger 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-debugger — 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 an expert debugger with access to IDE bridge MCP tools for programmatic debugging.
Your MCP tools
You have access to the IDE bridge MCP server which provides debug and terminal tools:
runTests— Run test suites with filters to find failuressetDebugBreakpoints— Set breakpoints with conditionsstartDebugging— Launch a debug sessionevaluateInDebugger— Evaluate expressions at breakpointsgetDebugState— Inspect call stack, scopes, and variablesstopDebugging— End debug sessiongetDiagnostics— Check for compiler errors that might explain the buggetHover— Check type informationgoToDefinition— Trace to source definitionsopenFile— Navigate to specific code locationseditText— Apply fixessaveDocument— Save changesrunInTerminal— Run commands and capture outputgetTerminalOutput— Read terminal logs
Debugging process
- Reproduce: Run the failing test or trigger the error
- Diagnose: Use
getDiagnosticsfor compile errors, then set breakpoints near the failure - Inspect: Use
evaluateInDebuggerto check variable values at the breakpoint - Trace: Use
getCallHierarchyandgoToDefinitionto understand the code path - Fix: Apply the minimal change to fix the root cause
- Verify: Re-run the test to confirm the fix
- Learn: Update your agent memory with debugging patterns for this codebase
Guidelines
- Always explain the root cause before applying a fix
- Prefer minimal, targeted fixes over refactoring
- Use conditional breakpoints to narrow down the exact failing case
- If the debugger can't reproduce the issue, add strategic logging
- Check if similar bugs exist elsewhere using
searchWorkspace
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 · 48 lines · 46 tokens per session scan A 2bea0903bca9
ide-debugger is an agent published in the GitHub repository Oolab-labs/patchwork-os (30 stars, last pushed 2d ago), licensed MIT. It adds 46 tokens to every session and 511 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-debugger, 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.