migration-check

migration-check is a command for Claude Code from latestaiagents/agent-skills. It costs 8 tokens per session (726 once invoked), scanned A, original, MIT.

A command that reviews pending database migrations for risks before they run. Database migrations change a database’s tables, columns, indexes, constraints, or data.

In plain words
What is it for?
Use it before running Laravel, Rails, Prisma, or Knex migrations, especially when they drop or modify columns, change constraints, or affect existing data.
Why use it?
It highlights changes that could delete data, fail, lock tables, or cause problems when applied to existing records.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the latestaiagents plugin — 47 skills, 10 commands, 7 plugins shipped together

Good fit Use it before running Laravel, Rails, Prisma, or Knex migrations, especially when…

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/latestaiagents/agent-skills/migration-check
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.

Clone the repo
git clone --depth 1 https://github.com/latestaiagents/agent-skills

Made for: Claude Code.

Or install latestaiagents, the plugin that ships this one along with the rest of its 47 skills, 10 commands, 7 plugins.

Wrote 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.

agentmods badge for migration-check

README.md
[![agentmods](https://agentmods.dev/badge/commands/latestaiagents/agent-skills/migration-check.svg)](https://agentmods.dev/commands/latestaiagents/agent-skills/migration-check)
Your own site
<a href="https://agentmods.dev/commands/latestaiagents/agent-skills/migration-check"><img src="https://agentmods.dev/badge/commands/latestaiagents/agent-skills/migration-check.svg" alt="Measured on agentmods" height="20"></a>
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 726 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00008 $0.00726
Opus 5 $0.00004 $0.00363
Sonnet 5 $0.00002 $0.00145
Haiku 4.5 $0.00001 $0.00073

Measured 6d ago against content hash 5cad45c1b9e1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

migration-check 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 6d 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.

commands/migration-check.md · 134 lines

How it starts

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

/migration-check

Analyze database migrations for risks before running them.

Step 1: Environment Check

# Verify environment
echo "Environment: $NODE_ENV"
echo "Database: $DATABASE_URL"

⚠️ If this is production, proceed with extra caution.

Step 2: Check Pending Migrations

# Laravel
php artisan migrate:status

# Rails
rails db:migrate:status

# Prisma
npx prisma migrate status

# Knex
npx knex migrate:status

Step 3: Analyze Each Migration

For each pending migration, I'll assess:

Check What I Look For
Destructive DDL DROP TABLE, DROP COLUMN, TRUNCATE
Data modifications DELETE, UPDATE affecting existing data
Constraint changes Adding NOT NULL to populated columns
Index changes Dropping indexes, adding unique constraints
Foreign keys CASCADE DELETE risks

Risk Classification

  • CRITICAL: Will delete/modify existing data
  • HIGH: May fail or lock tables
  • MEDIUM: Adds constraints, may need backfill
  • LOW: Safe additive changes (CREATE, ADD COLUMN nullable)

Step 4: Check Existing Data

Before migrations that DROP or modify:

-- Check row counts in affected tables
SELECT 'users' as table_name, COUNT(*) as rows FROM users
UNION ALL
SELECT 'orders', COUNT(*) FROM orders;

-- Check if column being dropped has data
SELECT COUNT(*) FROM users WHERE deprecated_column IS NOT NULL;

Step 5: Pre-Migration Backup

Required for CRITICAL/HIGH risk migrations:

# Full database backup
pg_dump -Fc database_name > backup_pre_migration_$(date +%Y%m%d_%H%M%S).dump

# Single table backup
pg_dump -t affected_table database_name > table_backup.sql

Step 6: Migration Decision

I'll present:

## Migration Risk Assessment

### Migration: 2024_01_15_drop_legacy_users
**Risk Level:** CRITICAL
**Action:** DROP TABLE legacy_users
**Data at Risk:** 1,247 records

**Recommendation:**
1. Create backup: `pg_dump -t legacy_users db > legacy_users_backup.sql`
2. Verify these records are not needed
3. Proceed only after confirmation

### Migration: 2024_01_16_add_email_index
**Risk Level:** LOW
**Action:** ADD INDEX on email column
**Data at Risk:** None

**Recommendation:** Safe to proceed

Read the full file on GitHub · 134 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. 6d ago First seen · 134 lines · 8 tokens per session scan A 5cad45c1b9e1

Subscribe to this mod's changes

migration-check is a command published in the GitHub repository latestaiagents/agent-skills (5 stars, last pushed 4mo ago), licensed MIT. It adds 8 tokens to every session and 726 once invoked, about $0.0000 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.