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.
git clone --depth 1 https://github.com/travisjneuman/.claudeWrote 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/travisjneuman/.claude/migrate)<a href="https://agentmods.dev/commands/travisjneuman/.claude/migrate"><img src="https://agentmods.dev/badge/commands/travisjneuman/.claude/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/commands/travisjneuman/.claude/migrate"><img src="https://agentmods.dev/badge/commands/travisjneuman/.claude/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.00005 | $0.01582 |
| Opus 5 | $0.00003 | $0.00791 |
| Sonnet 5 | $0.00001 | $0.00316 |
| Haiku 4.5 | $0.00001 | $0.00158 |
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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database Migration Manager
Detects the project's ORM, generates migrations, validates them, and manages the migration lifecycle.
Execution Flow
Step 1: Detect ORM
# Prisma
[ -d "prisma" ] && [ -f "prisma/schema.prisma" ] && echo "PRISMA"
# Drizzle
[ -f "drizzle.config.ts" ] || [ -f "drizzle.config.js" ] && echo "DRIZZLE"
# TypeORM
grep -q "typeorm" package.json 2>/dev/null && echo "TYPEORM"
# Sequelize
grep -q "sequelize" package.json 2>/dev/null && echo "SEQUELIZE"
# Django
[ -f "manage.py" ] && grep -q "django" requirements.txt 2>/dev/null && echo "DJANGO"
# Alembic (SQLAlchemy)
[ -f "alembic.ini" ] && echo "ALEMBIC"
# Knex
grep -q "knex" package.json 2>/dev/null && echo "KNEX"
# Golang (golang-migrate / goose)
[ -d "migrations" ] && ls migrations/*.sql &>/dev/null && echo "GO_MIGRATE"
Step 2: Run Action
Action: {{action}}
Name: {{name}}
create - Generate a New Migration
Prisma:
npx prisma migrate dev --name {{name}} --create-only
Before running, read prisma/schema.prisma and validate:
- No destructive changes without explicit confirmation (dropping columns/tables)
- New required fields have defaults or are nullable
- Index names follow conventions
- Relations have proper onDelete behavior
Drizzle:
npx drizzle-kit generate:pg --name {{name}}
TypeORM:
npx typeorm migration:generate -n {{name}} -d src/data-source.ts
Django:
python manage.py makemigrations --name {{name}}
Alembic:
alembic revision --autogenerate -m "{{name}}"
Knex:
npx knex migrate:make {{name}}
After generation:
- Read the generated migration file
- Verify it matches intended changes
- Check for destructive operations
- Validate reversibility (down migration exists)
Migration Created
-----------------
File: prisma/migrations/20240115_add_user_roles/migration.sql
ORM: Prisma
Changes detected:
+ CREATE TABLE "Role" (id, name, createdAt)
+ ALTER TABLE "User" ADD COLUMN "roleId" (FK -> Role.id)
+ CREATE INDEX "User_roleId_idx" ON "User"("roleId")
Safety check:
[PASS] No destructive operations
[PASS] New columns are nullable or have defaults
[PASS] Foreign keys have ON DELETE behavior
[PASS] Indexes added for foreign keys
Ready to apply with: /migrate run
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.
- 6d ago First seen · 325 lines · 5 tokens per session scan A 2aa3696ed840
migrate is a command published in the GitHub repository travisjneuman/.claude (97 stars, last pushed 4d ago), licensed MIT. It adds 5 tokens to every session and 1,582 once invoked, about $0.0000 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
hades-export-traces
Export Charon trace data for analysis or sharing.
dev-supabase
Configure and use Supabase as a backend (Auth, Database, Storage, Realtime, Edge Functions).
dev-prisma
Command "dev-prisma" from christopherlouet/claude-base, covering agent dev-prisma (pointer), context, delegate to the vendor toolkit, prisma's preferred path (verify on their readme) and fallback — clone and copy.
api-gen
Generate REST API endpoints with routes, validation, error handling, and tests.
performance-audit
Find performance bottlenecks across the stack — queries, rendering, bundle size, memory.
debug
Systematic debugging — reproduce, isolate, fix, verify, and add regression test.