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 skills add Oolab-labs/claude-ide-bridge --skill ide-dead-code-huntergit 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-dead-code-hunter)<a href="https://agentmods.dev/skills/oolab-labs/claude-ide-bridge/ide-dead-code-hunter"><img src="https://agentmods.dev/badge/skills/oolab-labs/claude-ide-bridge/ide-dead-code-hunter.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.00052 | $0.00806 |
| Opus 5 | $0.00026 | $0.00403 |
| Sonnet 5 | $0.00010 | $0.00161 |
| Haiku 4.5 | $0.00005 | $0.00081 |
Grade A, and why
ide-dead-code-hunter 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
1 near-identical copy found in the catalogue:
- ide-dead-code-hunter — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IDE Dead Code Hunter
Prerequisites
- Check if
getToolCapabilitiesis available.- Not available: tell the user this skill requires the Claude IDE Bridge with a connected VS Code extension, then stop.
- Available: call it. If
extensionConnectedis false: show the same message and stop. If true: proceed.
Goal
Find dead code — unused exports, functions with zero callers, unused imports — and produce a prioritized cleanup list with confidence badges.
Workflow
Phase 1: Scope
-
Note the argument:
$ARGUMENTS- If a specific file path: scope search to that file only
- If a directory: scope to that directory
- If empty: search the entire workspace
-
Use
getProjectInfoto understand the project type and entry points (to avoid flagging intentional public API exports as dead)
Phase 2: Detect unused symbols
-
Call
detectUnusedCodeon each in-scope file (or workspace-wide if no scope) -
For each reported unused symbol, call
findReferencesto cross-verify:- Zero references: confirmed dead — high confidence
- References only in the same file: likely dead (internal-only) — medium confidence
- References in other files: false positive from
detectUnusedCode— skip
-
Call
searchWorkspacewith pattern^exporton TypeScript/JS files to find exported symbols not caught bydetectUnusedCode, then runfindReferenceson each to check usage outside the file
Phase 3: Unused imports
- Use
getDocumentSymbolson each in-scope file to list import declarations - For any import whose symbol has zero
findReferencesresults in the current file body: flag as unused import
Phase 4: Build the report
Produce a Markdown table sorted by priority:
## Dead Code Report
Scoped to: [scope or "workspace-wide"]
Analyzed: N files
### High Confidence (zero external references)
| Symbol | File | Line | Type | Action |
|--------|------|------|------|--------|
| `functionName` | src/foo.ts | 42 | function | Delete |
| ...
### Medium Confidence (internal refs only)
| Symbol | File | Line | Type | Refs | Action |
|--------|------|------|------|------|--------|
| `helperFn` | src/bar.ts | 15 | function | 2 (same file) | Review |
| ...
### Unused Imports
| Import | File | Line | Action |
|--------|------|------|--------|
| `{ OldType }` | src/baz.ts | 3 | Remove |
| ...
### Summary
- High confidence dead code: N symbols
- Medium confidence: M symbols
- Unused imports: K declarations
- Estimated line reduction: ~X lines
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 · 92 lines · 52 tokens per session scan A 4fd75ef553bb
ide-dead-code-hunter is a skill published in the GitHub repository Oolab-labs/claude-ide-bridge (38 stars, last pushed 4mo ago), licensed MIT. It adds 52 tokens to every session and 806 once invoked, about $0.0003 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-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-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-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-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-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.