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 skills/oolab-labs/patchwork-os/ide-reviewnpx skills add Oolab-labs/patchwork-os --skill ide-reviewgit 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.00044 | $0.00828 |
| Opus 5 | $0.00022 | $0.00414 |
| Sonnet 5 | $0.00009 | $0.00166 |
| Haiku 4.5 | $0.00004 | $0.00083 |
Grade A, and why
ide-review 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.
This is a copy
100% identical to ide-review — 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IDE PR Review Workflow
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 with a connected VS Code extension. It uses LSP tools (hover, references, call hierarchy, diagnostics) and GitHub tools for deep PR analysis.
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)
Alternative: use
gh pr diff <number>for a basic diff review." - Start the bridge:
-
Available: call it. If
extensionConnectedisfalse: show the same message. Iftrue: proceed.
-
Review a pull request using the IDE bridge's full code intelligence stack. Goes beyond diff reading by using LSP to understand the impact of changes.
Workflow
Phase 1: Gather PR context
- Use
githubViewPRto get PR details (title, description, author, base branch):$ARGUMENTS - Use
githubGetPRDiffto get the full diff - Use
githubListRunsto check CI status on the PR branch
Phase 2: Deep code analysis
For each changed file in the diff:
- Use
openFileto open the file at the first changed line - Use
getDiagnosticsto check for any errors or warnings in modified files - For each modified function or class:
- Use
getHoverto verify type signatures are correct - Use
findReferencesto check if callers are affected by the change - Use
getCallHierarchy(incoming) to understand who depends on modified code - Use
goToDefinitionon any new types or imports to verify they exist
- Use
- For renamed symbols:
- Use
searchWorkspaceto check for any missed references (string literals, comments, config files that LSP doesn't cover)
- Use
- For deleted code:
- Use
findReferenceson deleted exports to verify nothing still imports them
- Use
Phase 3: Run quality checks
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.
- 3d ago First seen · 82 lines · 44 tokens per session scan A 0a1a6b79ffc8
ide-review is a skill published in the GitHub repository Oolab-labs/patchwork-os (30 stars, last pushed 3d ago), licensed MIT. It adds 44 tokens to every session and 828 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-review, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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.
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.
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.
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…