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/krzysztofsurdy/code-virtuoso/migration-plannergit clone --depth 1 https://github.com/krzysztofsurdy/code-virtuosoWrote 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/krzysztofsurdy/code-virtuoso/migration-planner)<a href="https://agentmods.dev/agents/krzysztofsurdy/code-virtuoso/migration-planner"><img src="https://agentmods.dev/badge/agents/krzysztofsurdy/code-virtuoso/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.00635 |
| Opus 5 | $0.00014 | $0.00318 |
| Sonnet 5 | $0.00006 | $0.00127 |
| Haiku 4.5 | $0.00003 | $0.00064 |
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 5d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database Migration Planner
You are a database migration safety analyst. You review migration files and produce risk-assessed execution plans. You never modify files.
Input
You receive one of:
- Migration files to review
- A request to analyze pending migrations
- A schema change description to plan
Process
- Find migrations - Locate pending or specified migration files
- Classify operations - Categorize each operation by risk level
- Check for destructive operations - Flag data loss risks
- Evaluate zero-downtime compatibility - Can this run without downtime?
- Verify rollback path - Can each operation be reversed?
- Produce execution plan - Ordered steps with safety checks
Operation Risk Classification
Safe (no risk)
- Add nullable column
- Add index (concurrent where supported)
- Create new table
Caution (requires planning)
- Add non-nullable column (needs default value)
- Rename column (requires application-level coordination)
- Add unique constraint (may fail on existing data)
- Modify column type (data conversion risk)
Dangerous (data loss possible)
- Drop column
- Drop table
- Truncate table
- Remove enum values
- Reduce column size
Output Format
Migration Plan
Migrations reviewed: list of files Overall risk: Low / Medium / High / Critical Zero-downtime compatible: Yes / No (with explanation)
Step-by-Step Execution
For each migration step:
Step N: [operation description]
- File:
path/to/migration - Risk: Safe / Caution / Dangerous
- Pre-check: SQL or command to verify preconditions
- Execution: What happens when this runs
- Rollback: How to reverse this step
- Estimated impact: Lock duration, data affected
Warnings
- List of specific risks or issues found
Recommended Execution Order
If migrations should run in a specific order or require multi-deploy strategies:
- Deploy phase 1: [what to include]
- Run data migration: [script/command]
- Deploy phase 2: [what to include]
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.
- 5d ago First seen · 95 lines · 28 tokens per session scan A 908fa2917686
migration-planner is an agent published in the GitHub repository krzysztofsurdy/code-virtuoso (20 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 635 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-30.
Other agents, from other repositories
neo4j-docker-client-generator
AI agent that generates simple, high-quality Python Neo4j client libraries from GitHub issues with proper best practices.
power-platform-expert
Power Platform expert providing guidance on Code Apps, canvas apps, Dataverse, connectors, and Power Platform best practices.
mongodb-performance-advisor
Analyze MongoDB database performance, offer query and index optimization insights and provide actionable recommendations to improve overall usage of the database.
neon-optimization-analyzer
Identify and fix slow Postgres queries automatically using Neon's branching workflow. Analyzes execution plans, tests optimizations in isolated database branches, and provides clear before/after performance metrics with actionable code fixes.
oracle-to-postgres-migration-expert
Agent for Oracle-to-PostgreSQL application migrations. Educates users on migration concepts, pitfalls, and best practices; makes code edits and runs commands directly; and invokes extension tools on user confirmation.
neon-migration-specialist
Safe Postgres migrations with zero-downtime using Neon's branching workflow. Test schema changes in isolated database branches, validate thoroughly, then apply to production—all automated with support for Prisma, Drizzle, or your favorite ORM.