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 rules/danielvm-git/bigpowers/plan-releasegit clone --depth 1 https://github.com/danielvm-git/bigpowersWrote 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/rules/danielvm-git/bigpowers/plan-release)<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/plan-release"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/plan-release.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.00069 | $0.01674 |
| Opus 5 | $0.00034 | $0.00837 |
| Sonnet 5 | $0.00014 | $0.00335 |
| Haiku 4.5 | $0.00007 | $0.00167 |
Grade A, and why
plan-release 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 yesterday.
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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Release
HARD GATE — Do NOT run this skill unless
elaborate-spechas produced a clear spec or the user has already defined the feature in detail. If the problem is still fuzzy, runelaborate-specfirst. HARD GATE —specs/product/SCOPE_LATEST.yaml(or legacyspecs/product/SCOPE_LATEST.yaml) must exist. If missing, runscope-workfirst.
Synthesize the conversation context into specs/release-plan.yaml (index) and shard detail under specs/epics/. No new interview — only clarify if something is genuinely ambiguous.
Outputs
| File | Content |
|---|---|
specs/release-plan.yaml |
release.version, semver bump hint, WSJF-ordered epic list with id, capsule_dir, wsjf, bcps — no story status |
specs/epics/eNN-<slug>/epic.yaml |
Epic manifest: id, title, wsjf, total_bcps, status, stories[] list |
specs/epics/eNN-<slug>/eNNsYY-<slug>.md |
Story spec in countable-story-format.md with 20 sections and Gherkin acceptance criteria |
specs/epics/eNN-<slug>/eNNsYY-tasks.yaml |
Decoupled task checklist with verify: commands per task |
specs/execution-status.yaml |
Flat key-value store for story status (eNNsYY: todo) |
Epic Capsule Structure
All epics use capsule directories (no flat/folder distinction):
specs/epics/e01-auth-system/
├── epic.yaml # Epic manifest
├── adr/ # Epic-local ADRs (created lazily)
├── e01s01-login.md # Story spec (countable-story-format)
├── e01s01-tasks.yaml # Decoupled task checklist
├── e01s02-jwt.md # Story spec
└── e01s02-tasks.yaml # Decoupled task checklist
Rationale: Capsule dirs achieve change isolation (C9), enable archive pruning (C2/C6), and enforce SRP by decoupling spec .md from execution -tasks.yaml (C1).
Process
1. Draft epics and stories
From the conversation context, define:
- Epics —
e01,e02, … (stable IDs; WSJF order inrelease-plan.yamlonly) - Stories —
e01s01,e01s02, … with Gherkin acceptance criteria
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.
- yesterday First seen · 145 lines · 69 tokens per session scan A 32023e8e6fa6
plan-release is a cursor rule published in the GitHub repository danielvm-git/bigpowers (163 stars, last pushed 3d ago), licensed MIT. It adds 69 tokens to every session and 1,674 once invoked, about $0.0003 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.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
app-router-patterns
Next.js 14+ App Router patterns — Server Components, Client Components, Route Handlers, Server Actions, and metadata API.
00-project-rules
ContextOS core project rules and role orchestration.
context-os
ContextOS rules for context-os.
database
Database architecture, schema design, Prisma, Drizzle ORM, indexing strategies, migrations, and N+1 query resolution.
vue
Rules for Vue (2 and 3) single-file components.