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/evan043/claude-cli-advanced-starter-pack/db-migrate.templategit clone --depth 1 https://github.com/evan043/claude-cli-advanced-starter-packWrote 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/evan043/claude-cli-advanced-starter-pack/db-migrate.template)<a href="https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/db-migrate.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/db-migrate.template.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.00000 | $0.04240 |
| Opus 5 | $0.00000 | $0.02120 |
| Sonnet 5 | $0.00000 | $0.00848 |
| Haiku 4.5 | $0.00000 | $0.00424 |
Grade A, and why
db-migrate.template 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 5d 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 — 878 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Runtime Compatibility
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows:
AskUserQuestion=> ask the user directly in chat.WebSearch/WebFetch=> use available web tools (search_query,open,find) and cite links.Read/Write=> use shell/filesystem tools in this workspace.- Claude-only MCP calls (for example Playwright MCP names) => use available equivalents or clearly state fallback.
- Keep intent and output format identical; only adapt execution mechanics.
db-migrate — Codex Runtime
Run database migrations via shell. Database MCP tools are unavailable in Codex.
# Prisma migrations
npx prisma migrate deploy # production
npx prisma migrate dev # development (creates migration)
# SQLAlchemy/Alembic
python -m alembic upgrade head
# Django
python manage.py migrate
# Flyway
flyway migrate
Tell me which ORM/migration tool you use and I'll run the appropriate command.
For database MCP integration, use Claude Code CLI: /db-migrate
description: Database migration management and schema versioning type: project complexity: medium allowed-tools: Bash, Read, Write, Grep, Glob category: database
/db-migrate
Manage database migrations, schema changes, and seed data.
Usage
/db-migrate
/db-migrate create --name add_users_table
/db-migrate up
/db-migrate down
/db-migrate status
/db-migrate seed
What It Does
- Detect ORM/Migration Tool - Identify Prisma, Knex, Alembic, etc.
- Create Migration - Generate new migration file
- Run Migrations - Apply pending migrations
- Rollback - Revert last migration
- Migration Status - Check migration state
- Seed Data - Populate database with test data
Step 1: Detect Migration Tool
{{#if backend.database}}
Database: {{backend.database}}
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.
- 5d ago First seen · 878 lines · 0 tokens per session scan A 9ddc6ac7ac2a
db-migrate.template is a command published in the GitHub repository evan043/claude-cli-advanced-starter-pack (61 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,240 tokens. 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-30.
Other commands, from other repositories
migration-observability
Migration monitoring, CDC, and observability infrastructure.
generate-crud
Tu es un développeur Symfony senior. Tu dois générer un CRUD complet respectant la Clean Architecture, incluant Entity, Repository, Controller, Templates, Form, et Tests.
optimize-doctrine
Optimisation Requêtes Doctrine.
migrate
Generate and manage database migrations.
check-order
Look up a single order by id through the ordersdb MCP server and report it in a strict pipe-separated format that downstream parsers can consume.
pn-audit-data
Design or review database schema — normalization, indexing strategy, migration plan, and data model decisions. Surgical command for database design. Use standalone or as part of pn-backend-audit.