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 agentmods add skills/jansenanalytics/claudex/migration-plannernpx skills add JansenAnalytics/claudex --skill migration-plannergit clone --depth 1 https://github.com/JansenAnalytics/claudexWrote 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/jansenanalytics/claudex/migration-planner)<a href="https://agentmods.dev/skills/jansenanalytics/claudex/migration-planner"><img src="https://agentmods.dev/badge/skills/jansenanalytics/claudex/migration-planner.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 | $0.00025 | $0.00430 |
| Opus 5 | $0.00013 | $0.00215 |
| Sonnet 5 | $0.00005 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
migration-planner 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 today.
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.
What it actually says
migration-planner
Plan and execute framework, language, or infrastructure migrations safely: version upgrades, framework swaps, API changes.
When to Use
- Upgrading Node.js or Python versions
- Migrating between frameworks (Express→Fastify, React→Next.js, etc.)
- Planning database migrations
- Modernizing legacy codebases
- Any breaking-change upgrade
How It Works
- Run
checklist-gen.shto generate a migration checklist for your scenario - Use
breaking-changes.shto scan for potential breaking changes - Use
rollback-plan.shto generate a rollback plan - Consult references for common patterns and anti-patterns
Scripts
| Script | Purpose |
|---|---|
checklist-gen.sh |
Generate a migration checklist for a specific migration type |
breaking-changes.sh |
Detect potential breaking changes between versions/frameworks |
rollback-plan.sh |
Generate a rollback plan template |
References
| File | Content |
|---|---|
common-migrations.md |
Common migration paths with tips |
anti-patterns.md |
Migration anti-patterns to avoid |
Example Usage
# Generate a migration checklist
bash scripts/checklist-gen.sh --from "node16" --to "node20" --type runtime
# Detect breaking changes in package.json
bash scripts/breaking-changes.sh --path /path/to/project --from "16.0.0" --to "20.0.0"
# Generate rollback plan
bash scripts/rollback-plan.sh --name "Node 20 upgrade" --steps "Update .nvmrc,Update CI config,Update Dockerfile" --output rollback.md
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.
- today First seen · 55 lines · 25 tokens per session scan A a0bc21e41c28
migration-planner is a skill published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 2mo ago), licensed MIT. It adds 25 tokens to every session and 430 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
deprecation-and-migration
Manages safe API deprecation and system migrations. Use when removing or changing existing APIs, migrating databases, upgrading dependencies, or migrating between architectural patterns without breaking existing consumers.
migration
Step-by-step guide to migrate a Cumulocity Web SDK application to a target version. Detects breaking changes with the ui-breaking-changes-cli, scaffolds a reference app at the target version with the new-app skill, compares key configuration files (app.ts, bootstrap.ts, angular.json, etc.), and finishes with a…
next-upgrade
Upgrade Next.js to the latest version following official migration guides and codemods.
Release Checklist
Check release readiness and record a release note. Use for release and rollback requests.
epistemic-graph-migrations
Upgrade and migrate a live epistemic-graph engine (the AI-native database): binary version flips, the one-time snapshot/.mp -> redb authoritative migration, config/env migrations (e.g. retired GRAPHBACKEND values), and on-disk data-format evolution (bi-temporal fields, persisted blobs). Use when raising the engine…
Breaking Change Detector
Compares two versions of a codebase or API and flags all breaking changes with migration hints.