agentmods.dev

ide-explore

A codebase exploration tool that uses an IDE’s language features to map project structure, follow calls between functions, and find where code starts running.

In plain words
What is it for?
Use it when joining a new project or investigating a module, entry point, call chain, or dependency relationship.
Why use it?
It helps when unfamiliar code is difficult to understand by showing how files, modules, and functions connect. It requires the Claude IDE Bridge and a connected VS Code extension.

Skill for Claude CodeCodex

30 3d ago A scan 48 tokens copy · 100% 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-explore
Any agent
npx skills add Oolab-labs/patchwork-os --skill ide-explore
Clone the repo
git clone --depth 1 https://github.com/Oolab-labs/patchwork-os

Made for: Claude Code, Codex.

Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 917 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00048 $0.00917
Opus 5 $0.00024 $0.00458
Sonnet 5 $0.00010 $0.00183
Haiku 4.5 $0.00005 $0.00092

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

Security

Grade A, and why

ide-explore 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

100% identical to ide-explore — 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/skills/ide-explore/SKILL.md · 110 lines

How it starts

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

IDE Codebase Explorer

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 with a connected VS Code extension. It uses LSP tools (type hierarchy, call hierarchy, references, hover, inlay hints) that 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.

Explore and explain a codebase using the IDE bridge's full LSP capabilities. Produces a structured architectural overview.

Workflow

Phase 1: Overview

  1. Use getProjectInfo to understand the project type, languages, and frameworks
  2. Use getFileTree with depth 3 to see the directory structure
  3. Use getToolCapabilities to see what language tooling is available
  4. Identify the focus area from the argument: $ARGUMENTS
    • If a specific file: explore that file and its connections
    • If a module/directory: explore the module's public API and internal structure
    • If a question: search for relevant code to answer it

Phase 2: Entry points and architecture

  1. Use searchWorkspace to find entry points (main, index, app.listen, export default, etc.)
  2. Use getDocumentSymbols on key files to list classes, functions, and exports
  3. For the focus area, use getTypeHierarchy on major classes to understand inheritance
  4. Use getCallHierarchy (outgoing) on entry points to trace the startup flow

Phase 3: Dependency mapping

  1. For the focus area's main exports:
    • Use findReferences to see who depends on them
    • Use goToDefinition on imports to trace dependencies
    • Use getHover on key functions to read their type signatures
  2. Use searchWorkspaceSymbols to find related types and interfaces
  3. Build a dependency map: what depends on what

Read the full file on GitHub · 110 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 · 110 lines · 48 tokens per session scan A 7829e520d5ae

Subscribe to this mod's changes

ide-explore is a skill published in the GitHub repository Oolab-labs/patchwork-os (30 stars, last pushed 3d ago), licensed MIT. It adds 48 tokens to every session and 917 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-explore, differing in 0 lines, and is treated as a copy.

ai-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