What is ide-api-deprecation-tracker?

A workspace scanner that finds deprecated programming interfaces, counts where they are used, and collects their recommended replacements. Deprecated means an interface is still available but should no longer be used.

Use it to produce a prioritized report of deprecated APIs, their callers, and migration guidance. It requires the Claude IDE Bridge to be connected.

It helps teams focus migration work on deprecated interfaces with the most callers, rather than searching manually or fixing low-impact uses first.

ide-api-deprecation-tracker — Skill for Claude Code by Oolab-labs

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.

Any agent

npx skills add Oolab-labs/claude-ide-bridge --skill ide-api-deprecation-tracker

Clone the repo

git clone --depth 1 https://github.com/Oolab-labs/claude-ide-bridge

Made for: Claude Code.

Or install claude-ide-bridge, the plugin that ships this one along with the rest of its 4 skills, 1 agent, 16 hooks, 1 MCP server.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/oolab-labs/claude-ide-bridge/ide-api-deprecation-tracker/github.svg)](https://agentmods.dev/skills/oolab-labs/claude-ide-bridge/ide-api-deprecation-tracker)

Your own site

<a href="https://agentmods.dev/skills/oolab-labs/claude-ide-bridge/ide-api-deprecation-tracker"><img src="https://agentmods.dev/badge/skills/oolab-labs/claude-ide-bridge/ide-api-deprecation-tracker/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/oolab-labs/claude-ide-bridge/ide-api-deprecation-tracker"><img src="https://agentmods.dev/badge/skills/oolab-labs/claude-ide-bridge/ide-api-deprecation-tracker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 842 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found 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.

Model	Per session	Once invoked
Fable 5.1	$0.00045	$0.00842
Opus 5	$0.00023	$0.00421
Sonnet 5	$0.00009	$0.00168
Haiku 4.5	$0.00005	$0.00084

Measured 9d ago against content hash 36aee42a213f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

ide-api-deprecation-tracker 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 9d 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

Copies of this mod

1 near-identical copy found in the catalogue:

ide-api-deprecation-tracker — 100% identical, 0 lines differ

claude-ide-bridge-plugin/skills/ide-api-deprecation-tracker/SKILL.md · 99 lines

How it starts

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

IDE API Deprecation Tracker

Prerequisites

Check if getToolCapabilities is available.
- Not available: tell the user this skill requires the Claude IDE Bridge, then stop.
- Available: call it. If extensionConnected is false: show the same message and stop. If true: proceed.

Goal

Produce a Markdown report of all deprecated APIs ranked by caller count, with migration paths extracted from JSDoc.

Workflow

Phase 1: Find deprecated symbols

Note the argument: $ARGUMENTS
- If a scope is given, pass it as the include glob to searchWorkspace
- Otherwise, search workspace-wide
Call searchWorkspace with pattern @deprecated to find all files containing deprecation annotations. This catches:
- /** @deprecated ... */ JSDoc comments
- @deprecated in TSDoc, Python docstrings, Go comments, etc.
For each match, call getHover at the annotated symbol's position to extract:
- The full deprecation message (migration guidance)
- The symbol name and type signature

Phase 2: Count callers

For each deprecated symbol found in Phase 1:
- Call searchWorkspaceSymbols to locate the symbol's definition precisely
- Call findReferences on the definition to count all call sites
- Record: symbol name, file, line, reference count, deprecation message

Phase 3: Extract migration paths

For symbols with a migration path mentioned in @deprecated (e.g., "use newFunction instead"):
- Extract the replacement symbol name from the hover text
- Call searchWorkspaceSymbols to verify the replacement exists

Phase 4: Report

## API Deprecation Report

Workspace: [project name]
Deprecated APIs found: N
Total call sites to migrate: M

### High Priority (>10 callers)

| API | File | Callers | Replacement | Deprecation message |
|-----|------|---------|-------------|---------------------|
| `oldFn()` | src/utils.ts:42 | 47 | `newFn()` ✓ | Use newFn() — supports async |
| ...

### Medium Priority (3–10 callers)

| API | File | Callers | Replacement | Deprecation message |
|-----|------|---------|-------------|---------------------|
| ...

### Low Priority (1–2 callers)

| API | File | Callers | Replacement |
|-----|------|---------|-------------|
| ...

### No Migration Path

These are deprecated with no documented replacement:
| API | File | Callers | Message |
|-----|------|---------|---------|
| ...

### Summary
- APIs to migrate: N
- Call sites to update: M
- APIs with clear migration path: K / N
- Suggestion: Start with high-priority APIs — they have the most callers and the clearest migration paths.

Read the full file on GitHub · 99 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.

9d ago First seen · 99 lines · 45 tokens per session scan A 36aee42a213f

Subscribe to this mod's changes

ide-api-deprecation-tracker is a skill published in the GitHub repository Oolab-labs/claude-ide-bridge (38 stars, last pushed 4mo ago), licensed MIT. It adds 45 tokens to every session and 842 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.

Claude Code Debugging ai claude developer-tools ide lsp

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…

blackwell-systems/agent-lsp · 126 tokens

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.

blackwell-systems/agent-lsp · 43 tokens

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.

blackwell-systems/agent-lsp · 57 tokens

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.

blackwell-systems/agent-lsp · 59 tokens

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.

blackwell-systems/agent-lsp · 0 tokens

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.

blackwell-systems/agent-lsp · 46 tokens