migrate-spec

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 rules/danielvm-git/bigpowers/migrate-spec

Clone the repo

git clone --depth 1 https://github.com/danielvm-git/bigpowers

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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/danielvm-git/bigpowers/migrate-spec.svg)](https://agentmods.dev/rules/danielvm-git/bigpowers/migrate-spec)

Your own site

<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/migrate-spec"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/migrate-spec.svg" alt="Measured on agentmods" height="20"></a>

Per session 45 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 8,501 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin unknown 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.

Model	Per session	Once invoked
Fable 5	$0.00045	$0.08501
Opus 5	$0.00023	$0.04251
Sonnet 5	$0.00009	$0.01700
Haiku 4.5	$0.00005	$0.00850

Measured today against content hash f739de39358a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

migrate-spec 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 today.

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/rules/migrate-spec.mdc · 908 lines

How it starts

The opening of the file, as written. The whole thing — 908 lines — stays where its author put it; the contents beside it link to each section on GitHub.

story: e25s01

story: e25s02

story: e25s03

story: e25s04

story: e25s05

story: e25s06

Migrate Spec

Transform existing GSD, spec-kit, or BMAD planning artifacts into the bigpowers specs/ model. No code is written — the output is a set of bigpowers-format spec files the user can use immediately.

Quick start

Run this skill from the root of the project being migrated (not the bigpowers repo itself).
The skill auto-detects the source framework and presents its findings before transforming anything.
All output goes to specs/ at the project root.

Red flags — stop and ask

Before proceeding, check for these rationalization traps:

Partial artifact set — only one fingerprint file found (e.g. just spec.md with no plan.md). Don't assume it's a complete project. Ask: "I found only X — is this the full set of your spec artifacts?"
Wrong trigger — user said "migrate my code" or "migrate the database", not "migrate my specs". Confirm before running.
Stale source — source artifacts have commit dates older than 6 months with no recent activity. Flag: "These specs appear inactive since . Are they still the source of truth?"
Active divergence — source state.yaml or sprint-status.yaml shows in-progress work. Flag: "There is active work in flight. Migrating now may lose in-progress context. Proceed?"

If any red flag fires: surface it, wait for explicit user confirmation before continuing.

Process

Step 1 — Detect the source framework

Scan for the fingerprints below. Stop at first match; if multiple match, list them and ask the user which is primary.

Framework	Fingerprints (any one is sufficient)
GSD	`.planning/` directory; `.planning/ROADMAP.md`; `.planning/REQUIREMENTS.md` with `REQ-` IDs
spec-kit	`.specify/` directory; `spec.md` + `plan.md` at root; `.github/skills/speckit-*/SKILL.md`
BMAD	`_bmad/` directory; `_bmad-output/` directory; `prd.md` with `FR-` IDs; `epic-.md` or `story-.md`

Read the full file on GitHub · 908 lines

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.

today First seen · 908 lines · 45 tokens per session scan A f739de39358a

Subscribe to this mod's changes

migrate-spec is a cursor rule published in the GitHub repository danielvm-git/bigpowers (162 stars, last pushed 2d ago), licensed MIT. It adds 45 tokens to every session and 8,501 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-09-03.

Git and workflow Planning Writing and docs ai-agents automation bmad claude-code clean-code cursor-rules