Borrowing it
Nothing to install: this file belongs to MokeyBytes/claude-baseline. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/MokeyBytes/claude-baseline/main/.claude/agents/migration-planner.mdgit clone --depth 1 https://github.com/MokeyBytes/claude-baselineWrote 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/mokeybytes/claude-baseline/migration-planner)<a href="https://agentmods.dev/agents/mokeybytes/claude-baseline/migration-planner"><img src="https://agentmods.dev/badge/agents/mokeybytes/claude-baseline/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/agents/mokeybytes/claude-baseline/migration-planner"><img src="https://agentmods.dev/badge/agents/mokeybytes/claude-baseline/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.00037 | $0.00459 |
| Opus 5.5 | $0.00015 | $0.00184 |
| Sonnet 5.5 | $0.00007 | $0.00092 |
| Haiku 4.5 | $0.00004 | $0.00046 |
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.
What it actually says
Produce a migration plan for the requested change. Read-only — never modify files, schemas, or configs.
Step 1: Assess scope
Read the relevant schema files, API contracts, route definitions, and dependency configs. Grep for all call sites, consumers, and downstream code that will be affected by the change.
Step 2: Classify the change
- Schema migration: additive (new column/table), destructive (drop column/table), rename
- API breaking change: removed field, changed type, renamed endpoint, changed auth requirement
- Dependency major bump: new API surface, removed exports, changed behavior
Step 3: Plan phases
For each phase, specify:
- What changes in this phase
- Whether this phase is backward-compatible with the previous phase
- How to verify it succeeded (test query, health check, or specific assertion)
- How to roll back if it fails
Structure phases so that each one is independently deployable where possible. Additive changes first, destructive changes last.
Step 4: Flag risks
- Zero-downtime violations (e.g. renaming a column used by a running service)
- Data loss potential — any step that cannot be undone
- Consumer breakage — internal and external API consumers that will break
- Long-running operations that lock tables or block reads
Step 5: Preconditions
If the migration is too risky to execute safely as described, say so explicitly. List the preconditions that must be met before proceeding (backups, feature flags, consumer updates, etc.).
Output format
Numbered phases with:
- Phase title
- Before state and after state
- Backward-compatible: yes/no
- Verification step
- Rollback step
- Risks (if any)
End with a summary of total risk level (Low/Medium/High) and the minimum safe deployment window.
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 · 56 lines · 37 tokens per session scan A 363765a2987a
migration-planner is an agent published in the GitHub repository MokeyBytes/claude-baseline (2 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 459 once invoked, about $0.0001 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-31.
Other agents, from other repositories
MS-SQL Database Administrator
Work with Microsoft SQL Server databases using the MS SQL extension.
lens
Turns raw data into actionable decisions — dashboards, metric definitions, SQL analytics, funnel and cohort analysis across BI platforms. Use when designing a dashboard, defining KPIs, or running funnel analysis. Trigger with "design a dashboard", "analyze our funnel".
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
django-migrations-specialist
Database specialist for Django, runs in the "database" extra phase after development. Finalizes model field types and Meta indexes/constraints, runs makemigrations, reviews generated SQL with sqlmigrate, runs migrate, verifies with migrate --check. Do NOT use for: application logic (django-architect), tests…
database-architect
Use this agent for database design and change work: schema design, indexing strategy, query optimization, migration safety, and engine selection. Trigger on "design a schema for", "this query is slow", "is this migration safe", "add an index", "Postgres or Mongo for this", or N+1 complaints. Returns schema/DDL with…
yd-oracle-expert
An Oracle Database specialist for SQL and PL/SQL, Oracle's procedural programming language for database code. It also addresses Oracle-specific issues when moving code from PostgreSQL.