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/VaiYav/speckit-product-forgeWrote 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/vaiyav/speckit-product-forge/migration-plan)<a href="https://agentmods.dev/commands/vaiyav/speckit-product-forge/migration-plan"><img src="https://agentmods.dev/badge/commands/vaiyav/speckit-product-forge/migration-plan.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.1 | $0.00126 | $0.01669 |
| Opus 5 | $0.00063 | $0.00834 |
| Sonnet 5 | $0.00025 | $0.00334 |
| Haiku 4.5 | $0.00013 | $0.00167 |
Grade A, and why
speckit.product-forge.migration-plan 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 8d 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Forge — Migration Plan (Phase 5.5)
You are the Migration Strategist for Product Forge.
Your job: turn data-model changes in plan.md into an explicit, reversible,
zero-downtime migration plan with real forward/backward scripts, so that
Phase 6 (Implement) never has to improvise migrations under time pressure.
This phase is opt-in and conditional — trigger only when plan.md declares schema changes.
User Input
$ARGUMENTS
Parse for:
- Feature slug (required).
--db=<kind>—mongodb|postgres|mysql. If omitted, detect from project config / plan.md hints.
Step 0: Prerequisites
plan.mdexists AND its Data Model section is non-empty.- Identify the DB kind:
- From
.product-forge/config.ymlproject_tech_stackif clear. - Otherwise from plan.md (Prisma schema ⇒ Postgres/MySQL; Mongoose schema ⇒ MongoDB; raw SQL ⇒ inspect).
- From
- Confirm with the user before proceeding.
If plan.md has no schema changes, exit with: "No data-model changes detected in plan.md — migration plan not needed."
Step 1: Schema Diff
Extract the before/after schema:
- Before: current schema from the codebase (read-only).
- After: schema described in plan.md Data Model section.
Produce a diff:
| Change | Field / collection | Type | Reversible? |
|---|---|---|---|
| ADD | User.push_token |
`string | null` |
| MODIFY | Subscription.status (enum active → trialing) |
enum | ⚠️ data-dependent |
| DROP | User.legacy_flag |
bool | ❌ destructive |
Flag any ❌ as HIGH RISK.
Step 2: Strategy Selection
Pick one strategy per change, defaulting toward safe:
| Strategy | When to use |
|---|---|
| Shadow column + dual-write | Renames, type widenings, non-nullable additions on non-empty tables. |
| Expand–migrate–contract | Any data backfill touching > 10k rows. |
| Blue-green | Changes to hot paths where a short flip window is acceptable. |
| Big-bang | Dev/staging only, or non-empty but small (< 1k rows), non-production-critical. |
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.
- 8d ago First seen · 220 lines · 126 tokens per session scan A 60823e2e7f03
speckit.product-forge.migration-plan is a command published in the GitHub repository VaiYav/speckit-product-forge (23 stars, last pushed 15d ago), licensed MIT. It adds 126 tokens to every session and 1,669 once invoked, about $0.0006 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-30.
Other commands, from other repositories
init
Initialize configurations for Supabase local development.
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.
ingest
Manually add knowledge to the Weaviate store.
json.batch_delete
Delete multiple JSON documents or paths in one itemwise batch.
json.batch_get
Read multiple JSON values by document and path.
json.index.drop
Drop a JSON secondary index by name.