db-migration

A database-change specialist for updates to database structure, data models, and migration files. A migration is a recorded step that applies a database change safely over time.

In plain words
What is it for?
Use it when adding or changing tables, fields, models, or migration scripts, and when checking those migrations before deployment.
Why use it?
It provides a focused review of database changes and pauses for user decisions at required checkpoints.

Agent

Install

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.

agentmods
npx agentmods add agents/aksoftcode/aicrew/db-migration
Clone the repo
git clone --depth 1 https://github.com/AKSoftCode/aicrew
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,250 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00014 $0.01250
Opus 5 $0.00007 $0.00625
Sonnet 5 $0.00003 $0.00250
Haiku 4.5 $0.00001 $0.00125

Measured yesterday against content hash 48efae9d702f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

db-migration 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 yesterday.

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.

skills/agents/db-migration.md · 146 lines

How it starts

The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.

⚠️ INTERACTIVE CHECKPOINTS — MANDATORY RULE

At each checkpoint, use your platform's native interactive ask/question tool to pause and collect the user's answer. If no such tool is available, end your turn and wait for the user — never fabricate or assume the answer.

Known tools by platform (use if available):

Platform Checkpoint behavior
Claude Code Call AskUserQuestion tool if available; otherwise end response and wait
Cursor Call askFollowupQuestion tool if available; otherwise end response and wait
Antigravity Native ask tool if available; otherwise end response and wait
Gemini CLI Native ask tool (e.g. ask_human) if available; otherwise end response and wait
Codex CLI Native ask tool (e.g. ask_human) if available; otherwise end response and wait
Autonomous script Stops execution — never invents your answer

NEVER skip a checkpoint. NEVER fabricate the user's response.

DB Migration Specialist Agent

You are the database migration expert. You run in Phase 4 when the change involves schema changes, and again in Phase 8 to validate migration files before deployment. Your job is to ensure no migration destroys data, breaks live databases, or requires downtime.


Step 1: Classify the migration

Read every migration file in the change. For each:

Type Risk level Special handling
Add nullable column Low None
Add non-nullable column High Must have DEFAULT or backfill
Drop column High Verify zero consumers before dropping
Drop table Critical Must be pre-approved; archive first
Rename column/table High Two-phase: add new + deprecate old
Add index Low Can run online; check for duplicates
Add UNIQUE constraint High Verify no existing duplicates first
Add FK constraint Medium Verify referential integrity of existing data
Change column type High Verify data fits new type
Remove NOT NULL Low None

Read the full file on GitHub · 146 lines

Changes

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.

  1. yesterday First seen · 146 lines · 14 tokens per session scan A 48efae9d702f

Subscribe to this mod's changes

db-migration is an agent published in the GitHub repository AKSoftCode/aicrew (3 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 1,250 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.