Borrowing it
Nothing to install: this file belongs to mit-network/everything-claude-code. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mit-network/everything-claude-code/main/.claude/commands/database-migration.mdgit clone --depth 1 https://github.com/mit-network/everything-claude-codeWrote 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/commands/mit-network/everything-claude-code/database-migration)<a href="https://agentmods.dev/commands/mit-network/everything-claude-code/database-migration"><img src="https://agentmods.dev/badge/commands/mit-network/everything-claude-code/database-migration/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/mit-network/everything-claude-code/database-migration"><img src="https://agentmods.dev/badge/commands/mit-network/everything-claude-code/database-migration.svg" alt="Reviewed on agentmods" width="80" 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.00018 | $0.00195 |
| Opus 5.5 | $0.00007 | $0.00078 |
| Sonnet 5.5 | $0.00004 | $0.00039 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
database-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 1mo 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.
This is a copy
100% identical to database-migration — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
/database-migration
Use this workflow when working on database-migration in everything-claude-code.
Goal
Database schema changes with migration files
Common Files
**/schema.*migrations/*
Suggested Sequence
- Understand the current state and failure mode before editing.
- Make the smallest coherent change that satisfies the workflow goal.
- Run the most relevant verification for touched files.
- Summarize what changed and what still needs review.
Typical Commit Signals
- Create migration file
- Update schema definitions
- Generate/update types
Notes
- Treat this as a scaffold, not a hard-coded script.
- Update the command if the workflow evolves materially.
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.
- 1mo ago First seen · 36 lines · 18 tokens per session scan A d6dd0c4338f0
database-migration is a command published in the GitHub repository mit-network/everything-claude-code (88 stars, last pushed 6mo ago), licensed MIT. It adds 18 tokens to every session and 195 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to database-migration, differing in 6 lines, and is treated as a copy.
Other commands, from other repositories
init
Initialize configurations for Supabase local development.
database-setup
Use when a project needs to store data and has no database yet. Setting up Supabase, creating tables, writing queries, and connecting them to the frontend. Written for designers.
new-migration
Scaffold a new database migration file pair (up + down) with auto-detection of migration tool and numbering.
json.batch_get
Read multiple JSON values by document and path.
json.batch_delete
Delete multiple JSON documents or paths in one itemwise batch.
json.index.drop
Drop a JSON secondary index by name.