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 agents/mokeybytes/claude-baseline/migration-plannergit clone --depth 1 https://github.com/MokeyBytes/claude-baselineWhat 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.00037 | $0.00459 |
| Opus 5 | $0.00018 | $0.00230 |
| Sonnet 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 3d 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.
- 3d 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 5d ago), licensed MIT. It adds 37 tokens to every session and 459 once invoked, about $0.0002 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 agents, from other repositories
db-orchestrator
Routes DB engineering queries to appropriate micro agents based on domain classification and coordinates parallel dispatch for multi-domain queries.
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
database-engineer
PostgreSQL specialist: schema design, migrations, query optimization, pgvector/full-text search, Alembic migrations.
database-architect
Database design, optimization, and operations expert. Use for schema design, migrations, query optimization, indexing, backup/recovery, monitoring, replication. Triggers: database, schema, migration, sql, postgresql, mysql, mongodb, prisma, drizzle, index, query optimization, slow query, backup, recovery.
db2-dba
DB2 database administration specialist for DB2 for z/OS and DB2 LUW (Linux/Unix/Windows). Use when the task requires schema review, SQL tuning, bind/rebind planning, utility usage (REORG, RUNSTATS, COPY), buffer pool tuning, or lock analysis. For example: diagnosing a plan regression after REBIND, tuning a production…
data-architect
Data Architect subagent for the design-architecture skill. Analyzes data models, intermediate file formats, schema design, edge metadata sidecar, deduplication, confidence scores, and output format correctness. Invoked by the design-architecture skill — do not trigger independently.