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 skills/random6913/claude-code-superkit/migratenpx skills add RaNDoM6913/claude-code-superkit --skill migrategit clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitWhat 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.00015 | $0.00783 |
| Opus 5 | $0.00008 | $0.00392 |
| Sonnet 5 | $0.00003 | $0.00157 |
| Haiku 4.5 | $0.00002 | $0.00078 |
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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database Migrations
Apply or rollback database migrations with auto-detection of the migration tool.
Target
Parse the user's request to determine the action. Accepted formats: up, down, down N, status.
Step 1 — Detect Migration Tool
Scan the project for migration tool markers:
| Marker | Tool | Apply Command | Rollback Command |
|---|---|---|---|
Makefile with migrate-up |
Make | make migrate-up |
make migrate-down |
Makefile with migrate |
Make | make migrate |
make migrate-rollback |
golang-migrate or numbered .sql pairs |
golang-migrate | migrate -path <dir> -database $DB up |
migrate ... down 1 |
dbmate in deps or PATH |
dbmate | dbmate up |
dbmate down |
alembic.ini or alembic/ |
Alembic | alembic upgrade head |
alembic downgrade -1 |
prisma/ + package.json |
Prisma | npx prisma migrate deploy |
npx prisma migrate reset |
db/migrate/ + Rakefile |
Rails | rails db:migrate |
rails db:rollback |
drizzle.config.ts |
Drizzle | npx drizzle-kit push |
(manual) |
knexfile.js / knexfile.ts |
Knex | npx knex migrate:latest |
npx knex migrate:rollback |
If a Makefile target exists for migrations, prefer it — it may include environment setup.
Step 2 — Execute Command
Based on the user's request:
up (default if no argument)
Apply all pending migrations:
<detected_apply_command>
down
Rollback the last migration:
<detected_rollback_command>
down N (e.g., "down 3")
Rollback N migrations:
- golang-migrate:
migrate ... down N - Alembic:
alembic downgrade -N - Rails:
rails db:rollback STEP=N - Knex:
npx knex migrate:rollback --all(then migrate to target, or rollback N times in loop)
status
Show migration status:
- golang-migrate:
migrate ... version - Alembic:
alembic current+alembic history - Prisma:
npx prisma migrate status - Rails:
rails db:migrate:status - dbmate:
dbmate status
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 · 84 lines · 15 tokens per session scan A 98ec9973a6b5
migrate is a skill published in the GitHub repository RaNDoM6913/claude-code-superkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 783 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-08-31.
Other skills, from other repositories
apm-review-panel
Use this skill to run a multi-persona expert advisory review on a labelled pull request in microsoft/apm. The panel fans out to five mandatory specialists plus a test-coverage specialist (active on every PR that touches src/) plus three conditional specialists (auth, doc-writer, performance-expert), all running in…
apm-issue-autopilot
Use this skill to drive any open microsoft/apm issue (bug, feature, docs, refactor, perf) from raw intake to a mergeable PR with triage as the central, paramount gate. Run the apm-triage-panel rubric per issue first, then present ONE consolidated triage review for the whole batch and escalate to the maintainer BY…
apm-spec-guardian
Use this skill to run a four-panel adversarial advisory review on any pull request that touches the OpenAPM specification artifact (docs/src/content/docs/specs/openapm-.md), its inline / sidecar JSON Schemas (docs/src/content/docs/specs/schemas/.schema.json), or the conformance fixture seed…
apm-triage-panel
Use this skill to triage one microsoft/apm issue selected by the daily sweep, the status/needs-triage fast path, or manual dispatch. Emit one synthesized comment with a decision, label set, exact milestone, and suggested next action.
batch-bug-shepherd
Use this skill to drive a batch of suspected bugs in microsoft/apm from raw issue list to mergeable PR queue. Fan out one triage subagent per issue (LEGIT / UNCLEAR / FIXED-AT-HEAD), gate every legit bug against PRINCIPLES.md via an apm-ceo strategic-alignment pass, cross-reference legit issues against open PRs, then…
cli-logging-ux
Use this skill when editing or creating CLI output, logging, warnings, error messages, progress indicators, or diagnostic summaries in the APM codebase. Activate whenever code touches console helpers (richsuccess, richwarning, richerror, richinfo, richecho), DiagnosticCollector, STATUSSYMBOLS, CommandLogger, or any…