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/fschifone/claude-setup-wizard/new-migrationgit clone --depth 1 https://github.com/fschifone/claude-setup-wizardWrote 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/fschifone/claude-setup-wizard/new-migration)<a href="https://agentmods.dev/commands/fschifone/claude-setup-wizard/new-migration"><img src="https://agentmods.dev/badge/commands/fschifone/claude-setup-wizard/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.00014 | $0.00313 |
| Opus 5 | $0.00007 | $0.00156 |
| Sonnet 5 | $0.00003 | $0.00063 |
| Haiku 4.5 | $0.00001 | $0.00031 |
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 4d 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.
What it actually says
New migration
Create a new Alembic migration, review the auto-generated diff, and flag any risky operations before the user commits.
When to use
Run /new-migration "add orders.fulfilled_at column" whenever a schema change
is needed. The argument becomes the migration's description.
Steps
- Verify the working tree is clean (warn but don't block if not).
- Run
uv run alembic revision --autogenerate -m "$ARGUMENTS". - Read the generated file under
backend/alembic/versions/. - Scan for risky operations:
DROP TABLE/DROP COLUMN→ flag as destructive.ALTER COLUMN ... NOT NULLwithout a default → flag as blocking on existing data.- Missing
downgrade()body → flag.
- Report findings. Do NOT auto-apply the migration.
Guardrails
- Never run
alembic upgrade headautomatically — user decides when. - Never delete a migration file; if rollback is needed, tell the user to remove it manually.
- If the diff is empty, delete the empty revision file and inform the user that no schema changes were detected.
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.
- 4d ago First seen · 34 lines · 14 tokens per session scan A e341200af6b2
new-migration is a command published in the GitHub repository fschifone/claude-setup-wizard (2 stars, last pushed 4mo ago), licensed MIT. It adds 14 tokens to every session and 313 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 commands, from other repositories
review-renovate
Review and merge renovate PRs with automerge configuration updates.
monitor-ci
Monitors pull request CI checks until they are resolved (pass or fail).
plan-regression-tests
Plan regression tests for existing code with it.skip statements.
volume-admin-set-status
Changes the operational status of a named volume.
notebook-query
Query the notebook knowledge base (SQLite) built by /agy:notebook — precise, grounded, cited. Ask in natural language ("sum the amounts by category", "which docs mention 'Acme Corp'", "build a project timeline") or pass raw SQL. Read-only. Use this when you need exact aggregates/lookups across a document corpus…
database-setup
Use when a project needs to store data and has no database yet. Setting up Supabase, creating tables, writing queries, and connecting them to the frontend. Written for designers.