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 codebygarv/Ai-skills --skill migration-plannergit clone --depth 1 https://github.com/codebygarv/Ai-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/codebygarv/ai-skills/migration-planner)<a href="https://agentmods.dev/skills/codebygarv/ai-skills/migration-planner"><img src="https://agentmods.dev/badge/skills/codebygarv/ai-skills/migration-planner/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/skills/codebygarv/ai-skills/migration-planner"><img src="https://agentmods.dev/badge/skills/codebygarv/ai-skills/migration-planner.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.00046 | $0.00592 |
| Opus 5.5 | $0.00018 | $0.00237 |
| Sonnet 5.5 | $0.00009 | $0.00118 |
| Haiku 4.5 | $0.00005 | $0.00059 |
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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Plan a migration from an existing system to a new one in incremental, individually-reversible steps — so the migration can be paused, verified, or rolled back at any point, rather than being a single high-risk cutover.
When to Use
- Migrating a framework, database, service, or platform that's already running in production.
- Replacing a component where a big-bang cutover would be too risky to attempt.
- The user asks how to "migrate," "move off," or "replace" something existing.
Differs from Project Planner: that plans building something new; this plans replacing something that already exists and must keep working throughout.
What to Analyze / Do
- Establish what must never break — the invariants that have to hold during every intermediate state (data integrity, uptime, API compatibility for existing consumers).
- Find the seam — the interface/boundary where old and new can coexist behind a common abstraction. Migrations without a seam turn into big-bang cutovers by default.
- Sequence into reversible steps — each step should be independently deployable and independently revertable. Name the rollback action for each step, not just the forward action.
- Plan dual-running/verification — where both systems run simultaneously and outputs are compared (shadow reads, dual writes, percentage-based traffic shifting) to build confidence before committing.
- Identify the point of no return — the step after which rollback stops being cheap (e.g. once old data is deleted, or once writes stop going to the old system). Call this out explicitly and put maximum verification before it.
- Plan the cleanup — migrations that never delete the old path leave permanent dual-maintenance cost; include the removal step explicitly.
Output Format
- Invariants — what must hold throughout.
- Migration steps — numbered, each with: what changes, how it's verified, and how it's rolled back.
- Point of no return — which step, and what must be confirmed before crossing it.
- Cleanup — the steps that remove the old path once the new one is proven.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 39 lines · 46 tokens per session scan A 023ed8c6ecf5
migration-planner is a skill published in the GitHub repository codebygarv/Ai-skills (27 stars, last pushed 2mo ago), licensed MIT. It adds 46 tokens to every session and 592 once invoked, about $0.0002 per session on Opus 5.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
bun-api
Bun runtime API reference for TypeScript scripts. Covers Bun.serve() HTTP/HTTP/2 server with routes and WebSockets, fetch() transport options, proxies and Bun.FetchSession connection pools, Bun.ModuleGraph multi-instance apps, Bun.file(), Bun.write(), Bun.$() shell, Bun.spawn(), Bun.Glob, Bun.env, bun:sqlite…
bun-cli
Bun CLI reference for package management, script running, type checking, testing, bundling, and compilation. Covers bun install/add/remove/update, bun run, bun check and --check, bun test, bun build, bunx, bun patch, bun audit fix, bun dedupe, bun prune, bun why, bun pm, bun repl, bunfig.toml, bun.lock, workspace…
git-pr
PR and MR workflows for GitHub (gh) and GitLab (glab). Creation, review comment handling, thread resolution, review state queries, merging, cost-aware bot review rounds (GitHub: Copilot, CodeRabbit), and Copilot code review configuration (rulesets, custom instructions, billing). Use when creating PRs/MRs, addressing…
deps-upgrade
Validate JavaScript/TypeScript dependency upgrades after an interactive or manual update. Establish the real delta from git, detect peer/engine/type conflicts, extract breaking changes, migrations and adoptable features from release notes, assess held-back or seemingly unused packages, and run verification gates.…
git-project
GitHub Projects (v2) setup and management via gh CLI + GraphQL: organize a repo's issues into epics with native sub-issues, drive a board Status flow (Todo -> In Progress -> Done), set Project Priority, classify with native issue Types (Task/Bug/Feature) instead of labels, scope work with milestones (incl. resolving…
git-ci
CI/CD status queries for GitHub Actions (gh) and GitLab CI (glab). Check pipeline status, failing jobs, workflow runs, job logs, and merge readiness. Use when checking CI status, debugging build failures, viewing job logs, watching pipeline progress, or configuring gh/glab CI read-only allowlists. Not for PR workflows…