Borrowing it
Nothing to install: this file belongs to Oolab-labs/claude-ide-bridge. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Oolab-labs/claude-ide-bridge/main/.claude/skills/ide-explore/SKILL.mdgit clone --depth 1 https://github.com/Oolab-labs/claude-ide-bridgeWrote 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.
[](https://agentmods.dev/skills/oolab-labs/claude-ide-bridge/ide-explore)<a href="https://agentmods.dev/skills/oolab-labs/claude-ide-bridge/ide-explore"><img src="https://agentmods.dev/badge/skills/oolab-labs/claude-ide-bridge/ide-explore.svg" alt="Measured on agentmods" height="20"></a>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.00048 | $0.00917 |
| Opus 5 | $0.00024 | $0.00458 |
| Sonnet 5 | $0.00010 | $0.00183 |
| Haiku 4.5 | $0.00005 | $0.00092 |
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 7d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- ide-explore — 100% identical, 0 lines differ
- ide-explore — 100% identical, 0 lines differ
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
- 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 (type hierarchy, call hierarchy, references, hover, inlay hints) that have no CLI equivalent.
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)"
- Start the bridge:
-
Available: call it. If
extensionConnectedisfalse: show the same message. Iftrue: proceed.
-
Explore and explain a codebase using the IDE bridge's full LSP capabilities. Produces a structured architectural overview.
Workflow
Phase 1: Overview
- Use
getProjectInfoto understand the project type, languages, and frameworks - Use
getFileTreewith depth 3 to see the directory structure - Use
getToolCapabilitiesto see what language tooling is available - 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
- Use
searchWorkspaceto find entry points (main, index, app.listen, export default, etc.) - Use
getDocumentSymbolson key files to list classes, functions, and exports - For the focus area, use
getTypeHierarchyon major classes to understand inheritance - Use
getCallHierarchy(outgoing) on entry points to trace the startup flow
Phase 3: Dependency mapping
- For the focus area's main exports:
- Use
findReferencesto see who depends on them - Use
goToDefinitionon imports to trace dependencies - Use
getHoveron key functions to read their type signatures
- Use
- Use
searchWorkspaceSymbolsto find related types and interfaces - Build a dependency map: what depends on what
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.
- 7d ago First seen · 110 lines · 48 tokens per session scan A 7829e520d5ae
ide-explore is a skill published in the GitHub repository Oolab-labs/claude-ide-bridge (38 stars, last pushed 4mo 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
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…
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.
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.
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.
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.
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.