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 commands/random6913/claude-code-superkit/new-migrationgit clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitWrote 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/random6913/claude-code-superkit/new-migration)<a href="https://agentmods.dev/commands/random6913/claude-code-superkit/new-migration"><img src="https://agentmods.dev/badge/commands/random6913/claude-code-superkit/new-migration.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 | $0.00022 | $0.02439 |
| Opus 5 | $0.00011 | $0.01220 |
| Sonnet 5 | $0.00004 | $0.00488 |
| Haiku 4.5 | $0.00002 | $0.00244 |
Grade A, and why
new-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.
How it starts
The opening of the file, as written. The whole thing — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
New Migration
Role
Scaffold a database migration that matches the project's existing migration tool, directory, numbering scheme, and SQL dialect.
Migration description: $ARGUMENTS
Hard Rules
- NEVER invent a migrations directory, numbering scheme, or naming pattern — copy every convention from existing migrations, or ask the user (Step 2).
- No migration system detected, OR the migrations directory is empty → Step 2: report and ask. Create zero files on that branch.
- Match the project's SQL dialect (Step 3). NEVER emit PostgreSQL-only types (
TIMESTAMPTZ,BIGSERIAL,JSONB) into a MySQL or SQLite project. - SQL-file tools always get BOTH files:
.up.sqland.down.sql. Down is the exact reverse of up. - Use
IF NOT EXISTS/IF EXISTSguards where the dialect supports them; never a destructive operation (DROP TABLE,DROP COLUMN) withoutIF EXISTS. - Report only after verifying the created files exist on disk (
lsor Read).
Step 1 — Detect Migration System
Check each marker with Glob. A row matches only if the directory contains at least one existing migration file:
| Marker | Tool | Directory | Naming Pattern |
|---|---|---|---|
backend/migrations/*.sql with numbered names |
golang-migrate | backend/migrations/ |
000NNN_desc.{up,down}.sql |
migrations/*.sql with numbered names |
golang-migrate | migrations/ |
000NNN_desc.{up,down}.sql |
db/migrations/*.sql |
golang-migrate / dbmate | db/migrations/ |
NNNNNN_desc.{up,down}.sql |
db/migrate/*.rb |
Rails | db/migrate/ |
YYYYMMDDHHMMSS_desc.rb |
alembic/versions/*.py |
Alembic | alembic/versions/ |
rev_desc.py |
prisma/migrations/ |
Prisma | prisma/migrations/ |
YYYYMMDDHHMMSS_desc/ |
drizzle/ + drizzle.config.ts |
Drizzle | drizzle/ |
NNNN_desc.sql |
Branches — exactly one applies:
- Exactly one row matches → Step 3.
- Two or more rows match → list the candidate directories, ask the user which one to use, wait for the answer.
- No row matches, or a directory exists but holds no migration files → Step 2.
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.
- yesterday First seen · 183 lines · 22 tokens per session scan A 5124527e036a
new-migration is a command published in the GitHub repository RaNDoM6913/claude-code-superkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 2,439 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-09-03.
Other commands, from other repositories
cleanup
Detect and remove orphaned code, unused components, dead routes, and stale database artifacts.
add-migration
Create a new Alembic database migration for the backend.
learn-workspace-intent
Run Contorium BYOK workspace intent learning when API keys are configured.
setup-mcp-claude-code
Build and register the Contorium MCP server for Claude Code or Cursor Agent.
dmb-resume
Resume DMB context for this session.
dmb-status
Show DMB status for this project.