db-migrate

A database migration command for creating and managing recorded changes to a database's structure or data. Migrations let teams apply the same database changes in a controlled order.

In plain words
What is it for?
For generating migrations, applying pending changes, undoing the latest change, and checking which migrations have run with tools such as Prisma, Alembic, or raw SQL.
Why use it?
It helps reduce accidental data loss and keeps the database aligned with changes in the application's models or schema.

Command

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 commands/alphaaiservice/cortex/db-migrate
Clone the repo
git clone --depth 1 https://github.com/alphaaiservice/cortex
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 372 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.00025 $0.00372
Opus 5 $0.00013 $0.00186
Sonnet 5 $0.00005 $0.00074
Haiku 4.5 $0.00003 $0.00037

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

Security

Grade A, and why

db-migrate 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.

commands/db-migrate.md · 56 lines

What it actually says

Database Migration Helper

Action: $ARGUMENTS

Detect Database Setup

  1. Identify ORM/migration tool:

    • Prisma, Drizzle, TypeORM, Sequelize (Node.js)
    • Alembic, Django migrations (Python)
    • GORM, golang-migrate (Go)
    • Raw SQL migrations
  2. Identify database type from connection strings / config

Actions

generate — Generate a new migration

  1. Analyze model/schema changes vs current database state
  2. Generate migration file with:
    • Descriptive name based on changes
    • UP migration (apply changes)
    • DOWN migration (rollback changes)
    • Data migration if needed (not just schema)
  3. Review the generated migration for safety:
    • No data loss operations without explicit confirmation
    • Proper index creation for new columns
    • Foreign key constraints
    • Default values for new NOT NULL columns

run — Apply pending migrations

  1. Show pending migrations
  2. Ask for confirmation
  3. Apply migrations
  4. Verify database state

rollback — Rollback last migration

  1. Show what will be rolled back
  2. Ask for confirmation
  3. Execute rollback
  4. Verify database state

status — Show migration status

  1. List all migrations (applied and pending)
  2. Show current database schema version
  3. Flag any drift between models and database

Safety Rules

  • NEVER drop tables or columns without explicit user confirmation
  • ALWAYS generate DOWN migrations
  • ALWAYS backup recommendation before destructive operations
  • Validate migration in a test/dry-run mode if possible
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 · 56 lines · 25 tokens per session scan A e5bd1be02e68

Subscribe to this mod's changes

db-migrate is a command published in the GitHub repository alphaaiservice/cortex (1 stars, last pushed 25d ago), licensed MIT. It adds 25 tokens to every session and 372 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.