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/migrategit 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/migrate)<a href="https://agentmods.dev/commands/random6913/claude-code-superkit/migrate"><img src="https://agentmods.dev/badge/commands/random6913/claude-code-superkit/migrate.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.00012 | $0.02161 |
| Opus 5 | $0.00006 | $0.01081 |
| Sonnet 5 | $0.00002 | $0.00432 |
| Haiku 4.5 | $0.00001 | $0.00216 |
Grade A, and why
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 today.
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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database Migrations
Role: apply, roll back, or report the status of database migrations, auto-detecting the project's migration tool. Rollbacks destroy data — every destructive step is gated behind explicit user confirmation.
Hard Rules
- Destructive-action gate: before running ANY command that can destroy data (
down,rollback,downgrade,reset,drop, any--forceflag), STOP and ask the user for confirmation AT THAT STEP. Show the exact command and exactly what will be lost (which migrations revert; which tables/columns they drop, from reading the migration files). Run only after the user explicitly agrees. - NEVER run
npx prisma migrate reset(or any tool's reset/drop-and-recreate) as a routine rollback — it drops the ENTIRE database. Offer it only as a clearly labeled last resort, and only run it after the user explicitly accepts total data loss. - NEVER guess a database connection string. Locate it (Step 2) or report where you looked and ask the user.
- Run the tool's read-only
statuscommand before anyupordown, whenever the tool has one. - If no migration tool is detected, report that and stop. If the detected tool has no true rollback (Prisma, Drizzle), follow its down branch in Step 4 — present only the options listed there, auto-run none of them, and do not improvise a workaround.
- For
down Nwith N > 1: in the confirmation (Rule 1), restate N and list the N migrations that will be reverted; if the user's answer does not clearly cover N migrations, do not run. - Prefer Makefile migration targets over raw tool commands — they may include environment setup.
Arguments
Requested action: $ARGUMENTS
| Argument | Action |
|---|---|
| (empty) | up |
up |
apply all pending migrations |
down |
rollback 1 migration (confirmation-gated) |
down N |
rollback N migrations (confirmation-gated, Rule 6) |
status |
read-only status report |
| anything else | report Unknown action: <arg> with the list above, stop |
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.
- today First seen · 147 lines · 12 tokens per session scan A 0b047810d5d0
migrate is a command published in the GitHub repository RaNDoM6913/claude-code-superkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 2,161 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
import
Import reads the legacy Agent Orchestrator flat-file store (/.agent-orchestrator) read-only and ports its projects and per-project settings into the rewrite database. Legacy files are never modified, and a re-run skips rows that already exist, so it is safe to run more than once. The daemon must be stopped before…
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.
dmb-resume
Resume DMB context for this session.
dmb-status
Show DMB status for this project.