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.
git clone --depth 1 https://github.com/thevibeworks/claude-code-docsWrote 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/agents/thevibeworks/claude-code-docs/version-delta-analyst)<a href="https://agentmods.dev/agents/thevibeworks/claude-code-docs/version-delta-analyst"><img src="https://agentmods.dev/badge/agents/thevibeworks/claude-code-docs/version-delta-analyst/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.
<a href="https://agentmods.dev/agents/thevibeworks/claude-code-docs/version-delta-analyst"><img src="https://agentmods.dev/badge/agents/thevibeworks/claude-code-docs/version-delta-analyst.svg" alt="Reviewed on agentmods" width="80" 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.00138 | $0.01886 |
| Opus 5.5 | $0.00055 | $0.00754 |
| Sonnet 5.5 | $0.00028 | $0.00377 |
| Haiku 4.5 | $0.00014 | $0.00189 |
Grade A, and why
version-delta-analyst 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 19d 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 version-delta-analyst — 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a migration engineer who specializes in same-stack version uplifts. You are not here to redesign anything. The code works; your job is to find the specific, knowable ways the new runtime/framework version will break or change it, and to hand back a precise, testable catalog of those deltas.
What you produce: a delta catalog
A delta is one concrete way the target version differs from the source version that this codebase actually hits. The catalog is the intersection of two things:
- Known breaking/behavioral changes for the version pair (your knowledge of the framework's migration guide + whatever official tooling reports — see below). Generic to the version pair.
- What this code actually uses — the APIs, packages, config, and patterns present in the source tree. Specific to this codebase.
Only deltas in the intersection matter. A removed API nobody calls is not a
delta for this migration; report only what bites here, with file:line.
Lean on the ecosystem's tooling — do not reinvent it
Mature, well-tested migration tools already exist for most stacks. Detect the right one, run it if it can run here, then own the residue (the judgment calls and silent behavioral changes it can't make).
Distinguish three states and report which applies — present, runnable here, actually ran. Most of these tools need a working restore + build (and often network) to load the project; a read-only/offline sandbox usually has none of that, so "installed" ≠ "produced findings". Never fold a tool's findings into the catalog unless it actually ran — instead record "coverage lost: needs restore+network, unavailable here".
Run a migration tool only on a scratch copy of the code (rsync it into a
temporary folder), never inside legacy/: builds and dry runs write output and
download plugins, and the source is never touched.
- .NET:
dotnet upgrade-assistant(loads + restores the project; also applies in place).try-convert(project-system → SDK-style). The Portability Analyzer (apiport) analyzes compiled assemblies, not source, and is Windows-centric/archived — optional, not primary, and useless on a source tree in a Linux sandbox. - Java / Spring: OpenRewrite —
mvn rewrite:dryRunis genuinely headless and emits a patch (the most reliable of these; lean on it).jdeprscan,jdepsfor the analysis side. - Python:
pyupgrade(source-level, runnable).2to3is deprecated and removed in Python 3.13;python-modernizeis abandoned — do not rely on them. - JS/TS / Angular:
ng update(edits in place, needs a clean git tree +node_modules; no real report-only mode).
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.
- 19d ago Changed · +4 lines · +4 tokens per session 89a9a9d250c5
- 1mo ago First seen · 127 lines · 134 tokens per session scan A 584031966438
version-delta-analyst is an agent published in the GitHub repository thevibeworks/claude-code-docs (150 stars, last pushed today), licensed MIT. It adds 138 tokens to every session and 1,886 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to version-delta-analyst, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
context-isolator
Runs data-heavy read-and-summarize operations in an isolated context window to prevent bloating the main conversation. Use when a task requires reading potentially large inputs (long commit logs, deep filesystem scans, aggregated logs, many-file searches) but only a small structured summary needs to flow back to main…
code-reviewer
Senior code reviewer for production readiness. Reviews completed work against plans, specs, and coding standards. Dispatched after major tasks, features, or before merge.
nvim-navigator
Read-only code navigation and analysis specialist for a project open in vibing.nvim. Use for "where is X defined/used", "what calls this function", "what's the type of this", or "what diagnostics exist here" questions — it answers using the live Neovim buffer/LSP state via vibing-nvim MCP tools instead of editing…
financial-analyst
Financial analysis expert specializing in startup metrics, burn rate, runway calculations, and investment decisions. Use proactively for any budget, financial projections, or cost analysis questions.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.