A monitor for an integrated development environment (IDE), the application where developers edit and run code, using a connected bridge to inspect workspace status.

It is for recurring or one-time monitoring of IDE diagnostics, test results, and terminal output, including development-server output.

It helps spot new errors, warnings, failed tests, or terminal problems during repeated checks.

ide-monitor — Skill for Claude Code by Oolab-labs

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/claude-ide-bridge --skill ide-monitor

Clone the repo

git clone --depth 1 https://github.com/Oolab-labs/claude-ide-bridge

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, 1 MCP server.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/oolab-labs/claude-ide-bridge/ide-monitor/github.svg)](https://agentmods.dev/skills/oolab-labs/claude-ide-bridge/ide-monitor)

Your own site

<a href="https://agentmods.dev/skills/oolab-labs/claude-ide-bridge/ide-monitor"><img src="https://agentmods.dev/badge/skills/oolab-labs/claude-ide-bridge/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/oolab-labs/claude-ide-bridge/ide-monitor"><img src="https://agentmods.dev/badge/skills/oolab-labs/claude-ide-bridge/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 original No closer match found 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.

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

Measured 12d ago against content hash 9ebd7ca46f74, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, 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 12d 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

Copies of this mod

1 near-identical copy found in the catalogue:

ide-monitor — 100% identical, 0 lines differ

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

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)

Use getDiagnostics to 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 runTests with 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-debug to investigate

Mode: `terminal <name>`

Use getTerminalOutput with 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

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.

12d 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/claude-ide-bridge (38 stars, last pushed 4mo ago), 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Claude Code Debugging ai claude developer-tools ide lsp

lsp-inspect

Full code quality audit for a file, package, or directory. Supports batch mode (directory walk with --top ranking), comparison mode (--diff for branch-only issues), severity calibration by blast radius, fix suggestions, and confidence tiers. Applies a check taxonomy (dead symbols, silent failures, error wrapping…

blackwell-systems/agent-lsp · 126 tokens

lsp-dead-code

Enumerate exported symbols in a file and surface those with zero references across the workspace. Use when auditing for dead code, cleaning up APIs, or checking which exports are safe to remove.

blackwell-systems/agent-lsp · 43 tokens

lsp-refactor

End-to-end safe refactor workflow — blast-radius analysis, speculative preview, apply to disk, verify build, run affected tests. Inlines lsp-impact + lsp-safe-edit + lsp-verify + lsp-test-correlation into one coordinated sequence.

blackwell-systems/agent-lsp · 57 tokens

lsp-safe-edit

Wrap any code edit with before/after diagnostic comparison. Speculatively previews the change first (previewedit), then applies to disk only if the error delta is acceptable. If post-edit errors appear, surfaces code actions for quick fixes. Handles single and multi-file edits.

blackwell-systems/agent-lsp · 59 tokens

lsp-understand

Deep-dive exploration of unfamiliar code — given a symbol or file, builds a complete Code Map showing type info, implementations, call hierarchy (2-level depth limit), all references, and source. Broader than lsp-explore: accepts files, synthesizes multi-symbol relationships, and produces a navigable dependency map.

blackwell-systems/agent-lsp · 0 tokens

lsp-edit-export

Safe workflow for editing exported symbols or public APIs. Use when changing a function signature, modifying a public type, or altering any symbol used outside its own package — finds all callers first so nothing breaks silently.

blackwell-systems/agent-lsp · 46 tokens