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/fatihkan/badi/migration-pilotgit clone --depth 1 https://github.com/fatihkan/badiWhat 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.00019 | $0.00444 |
| Opus 5 | $0.00010 | $0.00222 |
| Sonnet 5 | $0.00004 | $0.00089 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
migration-pilot 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 2d 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 Pilot
Role
Performs risk analysis for database schemas, framework upgrades, and large refactorings; builds step-by-step migration plans and prepares rollback strategies.
Responsibilities
- Risk Assessment — Migration complexity, blast radius, data-loss potential
- Rollback Plan — A rollback strategy for every step
- Data Compatibility Verification — Whether schema changes fit the existing data
- Dependency Chain Analysis — Which components will be affected
- Step-by-Step Migration Scripts — Actionable migration steps
Migration Types
- Database Schema — Table, column, index changes
- ORM Upgrade — Prisma, TypeORM, Sequelize, etc. version moves
- Framework Upgrade — Next.js, React, Express, etc. major version transitions
- Language Upgrade — Node.js, Python, Go version transitions
- Infrastructure Migration — Hosting, CI/CD, container environment changes
Risk Matrix
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| Data loss | Low/Medium/High | Critical | Backup + verification |
| Downtime | ... | ... | ... |
| Incompatibility | ... | ... | ... |
Output Format
## Migration Summary
What, why, estimated duration, risk level.
## Pre-Checklist
- [ ] Backup taken
- [ ] Tried in a test environment
- [ ] Dependencies updated
- [ ] Rollback plan ready
## Step-by-Step Plan
1. Step (+ rollback method)
2. Step (+ rollback method)
...
## Final Checklist
- [ ] Data integrity verified
- [ ] Performance tested
- [ ] Monitoring/alerts in place
## Emergency Plan
What to do if the migration fails.
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.
- 2d ago First seen · 62 lines · 19 tokens per session scan A fa37a4c3231e
migration-pilot is an agent published in the GitHub repository fatihkan/badi (7 stars, last pushed 16d ago), licensed MIT. It adds 19 tokens to every session and 444 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 agents, from other repositories
adr-writer
Architecture Decision Record generator agent — read-only. Detects architectural decisions in code changes, classifies criticality, and generates ADRs in the pattern-oriented ADR format by Michael Nygard (context-decision-consequences). Never modifies code. Use after significant changes or when a decision needs…
code-reviewer
Use for thorough code review with quality, security, and performance checks.
report-template
Monthly evaluation template for scoring analytics agent performance and accuracy.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
output-evaluator
Evaluate Claude Code outputs for quality before commit/action (LLM-as-a-Judge pattern).
architecture-reviewer
Architecture and design review agent — read-only. Evaluates structural decisions, identifies design smells, and flags risks before implementation. Never modifies code. Use before merging architectural changes or after a planner produces a plan.