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 jakesterns/agent-skills --skill migration-plannergit clone --depth 1 https://github.com/jakesterns/agent-skillsWrote 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/jakesterns/agent-skills/migration-planner)<a href="https://agentmods.dev/skills/jakesterns/agent-skills/migration-planner"><img src="https://agentmods.dev/badge/skills/jakesterns/agent-skills/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.1 | $0.00028 | $0.00338 |
| Opus 5 | $0.00014 | $0.00169 |
| Sonnet 5 | $0.00006 | $0.00068 |
| Haiku 4.5 | $0.00003 | $0.00034 |
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 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.
What it actually says
Migration Planner
Use this skill when a user wants to move from one version, framework, library, API, runtime, schema, or architecture pattern to another.
Inputs
- Current and target versions or architectures
- Affected services, packages, database objects, APIs, or user workflows
- Constraints such as downtime tolerance, compatibility requirements, release windows, and rollback needs
Steps
- Inventory the affected surface area: imports, configuration, APIs, data schemas, tests, generated code, documentation, and deployment paths.
- Identify breaking changes, compatibility gaps, deprecations, behavior changes, and transitive dependency impacts.
- Split the migration into phases that preserve working software after each phase.
- Define verification for each phase: unit tests, integration tests, smoke checks, data validation, metrics, and manual QA.
- Plan rollout and rollback: feature flags, dual writes, compatibility shims, canaries, backups, and cutover criteria.
- Call out high-risk unknowns and create small discovery tasks for them.
- Produce an implementation order that minimizes blast radius.
Output
Return:
- Migration summary and scope
- Phased plan with tasks, owners or modules, and validation
- Breaking changes and compatibility strategy
- Rollout and rollback plan
- Open questions and risk register
Guidelines
- Prefer reversible phases over large rewrites.
- Keep user-facing behavior stable unless the migration explicitly changes it.
- Separate discovery tasks from implementation tasks.
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 · 41 lines · 28 tokens per session scan A 58d2dd3bf919
migration-planner is a skill published in the GitHub repository jakesterns/agent-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 338 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…