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 skills add Oolab-labs/patchwork-os --skill ide-monitorgit 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/skills/oolab-labs/patchwork-os/ide-monitor)<a href="https://agentmods.dev/skills/oolab-labs/patchwork-os/ide-monitor"><img src="https://agentmods.dev/badge/skills/oolab-labs/patchwork-os/ide-monitor/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/skills/oolab-labs/patchwork-os/ide-monitor"><img src="https://agentmods.dev/badge/skills/oolab-labs/patchwork-os/ide-monitor.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.00030 | $0.00643 |
| Opus 5 | $0.00015 | $0.00321 |
| Sonnet 5 | $0.00006 | $0.00129 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
ide-monitor 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 10d 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-monitor — 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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IDE Monitor
Prerequisites
- Check if the
getToolCapabilitiesMCP tool is available to you.-
Not available (no MCP tool by that name): stop and tell the user: "This skill requires the Claude IDE Bridge. It uses
getDiagnosticsandrunTestswhich have no CLI equivalent.To use this skill:
- Start the bridge:
npm run start-all(in claude-ide-bridge/) - Ensure the Claude IDE Bridge extension is installed in your IDE
- Use the
claude --idesession (not remote-control)"
- Start the bridge:
-
Available: call it. If
extensionConnectedisfalse: show the same message. Iftrue: proceed.
-
Monitor your IDE workspace continuously. Use with /loop for recurring checks.
Usage patterns
/loop 5m /claude-ide-bridge:ide-monitor diagnostics
/loop 10m /claude-ide-bridge:ide-monitor tests
/loop 2m /claude-ide-bridge:ide-monitor terminal dev-server
Or run once:
/claude-ide-bridge:ide-monitor diagnostics
Modes
Parse $ARGUMENTS to determine the monitoring mode:
Mode: diagnostics (default if no argument)
- Use
getDiagnosticsto get all current errors and warnings - Compare with the previous check (if this is a recurring loop):
- Report new errors since last check
- Report resolved errors since last check
- If there are critical errors, summarize them prominently
- If everything is clean, report "No issues found"
Mode: tests [filter]
- Use
runTestswith the optional filter from the argument - Report:
- Total pass/fail counts
- Any new failures (tests that were passing before)
- Test duration for performance tracking
- If tests fail, suggest running
/claude-ide-bridge:ide-debugto investigate
Mode: terminal <name>
- Use
getTerminalOutputwith the terminal name from the argument - Check for:
- Error patterns in recent output (stack traces, "Error:", "FATAL")
- Whether the process is still running (use
listTerminals)
- If the terminal has died, report it and suggest restarting
- If errors are found, summarize the most recent ones
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.
- 10d ago First seen · 75 lines · 30 tokens per session scan A 9ebd7ca46f74
ide-monitor is a skill published in the GitHub repository Oolab-labs/patchwork-os (30 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 643 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-monitor, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
triage-issue
Analyze a GitHub issue, verify claims against the codebase, and close invalid issues with a technical response.
hive.error-recovery
Follow a structured recovery decision tree when tool calls fail instead of blindly retrying or giving up.
manage-skills
A maintenance workflow for checking whether project verification skills still cover the code and rules that changed during a session.
systematic-debugging
Structured debugging methodology — use before proposing fixes for any error or failure. Covers: code bugs, build errors, deploy failures, config conflicts, dependency issues, infra problems. Also use when previous fix attempts failed or root cause is unclear.
review-loop
Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE. Use before claiming any behavioural change is done, and on requests like "review loop", "adversarial review", "independent review", "get this verified"…