ide-monitor

ide-monitor is a skill for Claude Code from Oolab-labs/patchwork-os. It costs 30 tokens per session (643 once invoked), scanned A, a copy of ide-monitor, MIT.

A guide for repeatedly checking an IDE, the program developers use to edit code, through bridge tools. It can inspect diagnostics, test results, or terminal output, including during scheduled checks with /loop.

In plain words
What is it for?
Use it for one-time or recurring checks of workspace diagnostics, tests, or a development server's terminal output; it requires the Claude IDE Bridge.
Why use it?
It helps catch new editor errors, test failures, or terminal problems while development continues.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

Part of the claude-ide-bridge plugin — 4 skills, 1 agent, 16 hooks shipped together

Good fit Use it for one-time or recurring checks of workspace diagnostics, tests, or a development server's terminal output; it requires the Claude IDE Bridge.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/oolab-labs/patchwork-os/ide-monitor
Install

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.

Any agent
npx skills add Oolab-labs/patchwork-os --skill ide-monitor
Clone the repo
git clone --depth 1 https://github.com/Oolab-labs/patchwork-os

Made for: Claude Code.

Or install claude-ide-bridge, the plugin that ships this one along with the rest of its 4 skills, 1 agent, 16 hooks.

Wrote 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.

agentmods badge for ide-monitor

README.md
[![agentmods](https://agentmods.dev/badge/skills/oolab-labs/patchwork-os/ide-monitor/github.svg)](https://agentmods.dev/skills/oolab-labs/patchwork-os/ide-monitor)
Your own site
<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.

agentmods 80×15 button for ide-monitor

Your own site · 80×15
<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>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 643 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 10d ago against content hash 9ebd7ca46f74, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

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.

Origin

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.

claude-ide-bridge-plugin/skills/ide-monitor/SKILL.md · 75 lines

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

  1. Check if the getToolCapabilities MCP 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 getDiagnostics and runTests which have no CLI equivalent.

      To use this skill:

      1. Start the bridge: npm run start-all (in claude-ide-bridge/)
      2. Ensure the Claude IDE Bridge extension is installed in your IDE
      3. Use the claude --ide session (not remote-control)"
    • Available: call it. If extensionConnected is false: show the same message. If true: 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)

  1. Use getDiagnostics to get all current errors and warnings
  2. Compare with the previous check (if this is a recurring loop):
    • Report new errors since last check
    • Report resolved errors since last check
  3. If there are critical errors, summarize them prominently
  4. If everything is clean, report "No issues found"

Mode: tests [filter]

  1. Use runTests with the optional filter from the argument
  2. Report:
    • Total pass/fail counts
    • Any new failures (tests that were passing before)
    • Test duration for performance tracking
  3. If tests fail, suggest running /claude-ide-bridge:ide-debug to investigate

Mode: terminal <name>

  1. Use getTerminalOutput with the terminal name from the argument
  2. Check for:
    • Error patterns in recent output (stack traces, "Error:", "FATAL")
    • Whether the process is still running (use listTerminals)
  3. If the terminal has died, report it and suggest restarting
  4. If errors are found, summarize the most recent ones

Read the full file on GitHub · 75 lines

Changes

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.

  1. 10d ago First seen · 75 lines · 30 tokens per session scan A 9ebd7ca46f74

Subscribe to this mod's changes

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.