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 skills add RaNDoM6913/claude-code-superkit --skill 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/skills/random6913/claude-code-superkit/migrate)<a href="https://agentmods.dev/skills/random6913/claude-code-superkit/migrate"><img src="https://agentmods.dev/badge/skills/random6913/claude-code-superkit/migrate/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/skills/random6913/claude-code-superkit/migrate"><img src="https://agentmods.dev/badge/skills/random6913/claude-code-superkit/migrate.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.00022 | $0.00985 |
| Opus 5.5 | $0.00009 | $0.00394 |
| Sonnet 5.5 | $0.00004 | $0.00197 |
| Haiku 4.5 | $0.00002 | $0.00098 |
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 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database Migrations
Inspect or execute the project's configured migration workflow. Read applicable AGENTS.md instructions and discover the runtime's command tools before use.
Target and Authority
Parse the user's request as intent: up, down, down N, or status. With no action, prepare a status inspection; never default to applying changes. Before any connection, resolve the exact component, database/environment, migration directory and configuration using non-secret evidence. Do not print credentials, connection URLs, environment dumps or private records. If the target or authorized access is unclear, stop before contacting it and ask for the missing information.
Before mutation, verify existing user authority covers that target, direction, migration set and destructive effects. A known database URL is not permission to modify it. Present the concrete pending/rollback set and its data impact; retain an already authorized bounded action without repeatedly asking. For destructive or shared/production operations, verify the project's required backup/recovery and approval conditions. Missing authority or recovery evidence blocks execution, not local inspection. Do not start infrastructure or change connection configuration implicitly.
Step 1 — Detect Migration Tool
Inspect actual configuration, dependencies, installed version, command help and existing migrations. Markers only select candidates. Inspect wrapper/Make targets for side effects before preferring them. Use installed binaries or existing package-manager scripts; never install a missing tool implicitly.
| Tool | Apply path to verify | Rollback semantics to verify |
|---|---|---|
| golang-migrate | Configured migration path/database, up |
Explicit down N; bare down may revert all migrations |
| dbmate | Configured migrate or project wrapper; up may also create the database |
Installed rollback / down alias reverts the latest migration; confirm each selected step |
| Alembic | Configured upgrade revision, commonly head |
Explicit revision or relative count; account for multiple heads |
| Prisma | Installed version's migration deployment command | No generic down command; migrate reset is a destructive reset, not rollback |
| Rails | Configured db:migrate |
db:rollback STEP=N with the selected migration set |
| Drizzle | Configured generated-migration apply command | Project-specific rollback/recovery; push directly changes schema and is not an interchangeable migration apply |
| Knex | Configured migrate:latest |
migrate:rollback reverts a batch, not necessarily one migration; use verified single-migration down or exact project procedure |
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 Changed · -23 lines · +7 tokens per session 7742b91100c1
- 1mo ago First seen · 84 lines · 15 tokens per session scan A 98ec9973a6b5
migrate is a skill published in the GitHub repository RaNDoM6913/claude-code-superkit (3 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 985 once invoked, about $0.0001 per session on Opus 5.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.
Other skills, from other repositories
migration-preview
Use when reviewing or writing a database migration, schema change, or data backfill — anything that alters durable data shape.
Supabase Expert
Database and backend knowledge for business operators — table design, auth setup, row-level security, storage, and edge functions explained in plain English. Not a developer guide — domain expertise for building your backend on Supabase.
cqrs-implementation
Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.
nav-skill-creator
Analyze codebase patterns and create custom skills for repetitive workflows. Use when project needs automation or pattern enforcement. Auto-invoke when user says "create a skill for...", "automate this workflow", or "we keep doing X manually".
neo4j-aura-agent-skill
Manages Neo4j Aura Agents via the v2beta1 REST API — create, list, get, update, delete, and invoke Aura agents backed by an AuraDB instance. Use when configuring Aura Agent tools (CypherTemplate, SimilaritySearch, Text2Cypher), setting system prompts, deploying agents to REST or MCP endpoints, invoking agents with…
software-database-design
Designs database schemas, migrations, and data models for PostgreSQL, MySQL, MongoDB, and Redis. Use when planning tables, relationships, indexes, or ORM-backed schema changes.