generate-migration

generate-migration is a command for Cursor from phuoctrung-ppt/ai-sdlc-workflow. It costs 33 tokens per session (355 once invoked), scanned A, original, MIT.

A command that creates a database migration, which is a controlled change to a database's structure.

In plain words
What is it for?
Use it to add or change tables, fields, constraints, and indexes according to the project's ORM and database conventions.
Why use it?
It helps apply the project's database rules consistently and includes a way to undo the change.

Command for Cursor

Install

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.

agentmods
npx agentmods add commands/phuoctrung-ppt/ai-sdlc-workflow/generate-migration
Clone the repo
git clone --depth 1 https://github.com/phuoctrung-ppt/ai-sdlc-workflow

Made for: Cursor.

Wrote 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.

agentmods badge for generate-migration

README.md
[![agentmods](https://agentmods.dev/badge/commands/phuoctrung-ppt/ai-sdlc-workflow/generate-migration.svg)](https://agentmods.dev/commands/phuoctrung-ppt/ai-sdlc-workflow/generate-migration)
Your own site
<a href="https://agentmods.dev/commands/phuoctrung-ppt/ai-sdlc-workflow/generate-migration"><img src="https://agentmods.dev/badge/commands/phuoctrung-ppt/ai-sdlc-workflow/generate-migration.svg" alt="Measured on agentmods" height="20"></a>
Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 355 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00033 $0.00355
Opus 5 $0.00016 $0.00178
Sonnet 5 $0.00007 $0.00071
Haiku 4.5 $0.00003 $0.00036

Measured 4d ago against content hash 90426776726c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

generate-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.

.cursor/commands/generate-migration.md · 35 lines

What it actually says

Act as Database Worker. Create a migration for: {migration_description}

  1. Run context-builder:
    python3 .cursor/context/context-builder.py \
      --phase database --task "{migration_description}" --agent database-worker \
      --keywords "migration,schema,index"
    
  2. Read .memory/constraints.md and AGENTS.md §3 (migrations path)

Migration Location

Determined by AGENTS.md §3 — e.g.:

  • TypeORM: <backend_path>/database/migrations/YYYYMMDDHHMMSS-{Name}.ts
  • Prisma: prisma/migrations/YYYYMMDDHHMMSS_{name}/migration.sql
  • Alembic: alembic/versions/YYYYMMDDHHMMSS_{name}.py

Rules

  • Both up() and down() — never a one-way migration
  • UUID or ULID primary keys (avoid auto-increment for distributed safety)
  • Timestamp columns: created_at, updated_at (timezone-aware)
  • deleted_at for soft delete where applicable
  • Indexes on all foreign keys and high-cardinality filter columns
  • CHECK constraints on logical business rules
  • Never enable ORM auto-sync (synchronize: false or equivalent)
  • Apply compliance columns from AGENTS.md §5 (e.g. tenant_id for multi-tenancy, encrypted fields for PII)

Load databases SKILL.md. Output complete migration file.

Changes

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.

  1. 4d ago First seen · 35 lines · 33 tokens per session scan A 90426776726c

Subscribe to this mod's changes

generate-migration is a command published in the GitHub repository phuoctrung-ppt/ai-sdlc-workflow (2 stars, last pushed 19d ago), licensed MIT. It adds 33 tokens to every session and 355 once invoked, about $0.0002 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.