agentmods.dev

ide-diagnostics-board

A dashboard that collects workspace diagnostics, such as errors and warnings reported by development tools, and shows them in a sortable browser table.

In plain words
What is it for?
Use it to scan a workspace, filter errors or warnings, count affected files, and inspect the results visually.
Why use it?
It gives a single view of problems spread across files and groups them by severity and file.

Skill for Claude CodeCodex

30 3d ago A scan 37 tokens copy · 98% MIT
View the source file Oolab-labs/patchwork-os
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.

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

Made for: Claude Code, Codex.

Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,305 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 98% 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 $0.00037 $0.01305
Opus 5 $0.00018 $0.00652
Sonnet 5 $0.00007 $0.00261
Haiku 4.5 $0.00004 $0.00130

Measured 3d ago against content hash 36b708cb49a5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ide-diagnostics-board 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 3d 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

98% identical to ide-diagnostics-board — 2 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/skills/ide-diagnostics-board/SKILL.md · 97 lines

How it starts

The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Generate a visual diagnostics dashboard for the workspace and open it in the browser.

Prerequisites

  1. Check if the getToolCapabilities MCP tool is available to you.
    • Available: call it, check extensionConnected → use IDE Path below.
    • Not available (no MCP tool by that name): use CLI Path below.

Arguments

$ARGUMENTS sets the severity filter:

  • error — errors only
  • warning — warnings and errors
  • all (default) — all severities

IDE Path

Use this path when bridge MCP tools are available.

Phase 1 — Collect diagnostics

  1. Determine the severity filter from $ARGUMENTS (default: all).
  2. Call getDiagnostics with no URI filter (full workspace scan). Pass the severity param if supported.
  3. If no diagnostics found, report "No diagnostics found — workspace is clean." and stop.

Phase 2 — Summarize

  1. Group diagnostics by severity: errors / warnings / info / hints.
  2. Group by file: sort files by error count descending.
  3. Compute totals: total diagnostic count, count per severity, number of files affected.

Phase 3 — Generate and open HTML

  1. Construct the HTML document (see HTML Template section below).
  2. Call openInBrowser with the HTML string and filename diagnostics-<timestamp>.html.
  3. Report: "Opened diagnostics board — N errors, M warnings across K files. Saved to: "

CLI Path

Use this path when bridge MCP tools are NOT available (e.g., remote-control sessions).

Phase 1 — Detect and run linters

  1. Determine the severity filter from $ARGUMENTS (default: all).
  2. Detect which linters are available by checking for config files using Glob:
    • **/tsconfig.json (not in node_modules) → run via Bash: npx tsc --noEmit 2>&1
    • **/biome.json or **/biome.jsonc → run via Bash: npx biome check . --reporter=json 2>&1
    • **/.eslintrc* or **/eslint.config.* → run via Bash: npx eslint . --format json 2>&1
    • **/pyrightconfig.json or **/*.py → run via Bash: npx pyright --outputjson 2>&1
    • **/ruff.toml or **/pyproject.toml → run via Bash: ruff check . --output-format json 2>&1
    • **/Cargo.toml → run via Bash: cargo check --message-format json 2>&1
  3. If no linters detected, report "No linter configuration found in workspace." and stop.

Read the full file on GitHub · 97 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. 3d ago First seen · 97 lines · 37 tokens per session scan A 36b708cb49a5

Subscribe to this mod's changes

ide-diagnostics-board is a skill published in the GitHub repository Oolab-labs/patchwork-os (30 stars, last pushed 3d ago), licensed MIT. It adds 37 tokens to every session and 1,305 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to ide-diagnostics-board, differing in 2 lines, and is treated as a copy.

Debuggingai-agentanthropicapproval-queueautomationclaudeclaude-code
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens