agentmods.dev

build-epic

build-epic is a cursor rule for Cursor from danielvm-git/bigpowers. It costs 50 tokens per session (1,902 once invoked), scanned A, original, MIT.

Eight-step epic build cycle — reads state.yaml, execution-status.yaml, and one epic capsule; updates status via bp-yaml-set or direct edit. Resume mode runs one step per invocation. Use instead of ad-hoc execute-plan for release work.

Cursor rule for Cursor

not rated 163 2d ago A scan 50 tokens MIT
View the source file danielvm-git/bigpowers
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/build-epic
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.

agentmods badge for build-epic

README.md
[![agentmods](https://agentmods.dev/badge/rules/danielvm-git/bigpowers/build-epic.svg)](https://agentmods.dev/rules/danielvm-git/bigpowers/build-epic)
Your own site
<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/build-epic"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/build-epic.svg" alt="Measured on agentmods" height="20"></a>
Per session 50 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,902 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.

ModelPer sessionOnce invoked
Fable 5 $0.00050 $0.01902
Opus 5 $0.00025 $0.00951
Sonnet 5 $0.00010 $0.00380
Haiku 4.5 $0.00005 $0.00190

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

Security

Grade A, and why

build-epic 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/build-epic.mdc · 105 lines

How it starts

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

story: e20s05

Build Epic

Scope: one story. Called by orchestrate-project Phase 4. Not a replacement for orchestrate-project.

Orchestrates the build flow for a single epic: survey → plan tasks → kickoff → TDD → verify → audit → commit → release.

HARD GATE — Set specs/state.yaml active_flow: build_epic and active_epic: eNN before starting.

HARD GATE — Not on main/master before step 3 (kickoff-branch).

Nine steps (epic_cycle in state.yaml)

Step Skill / action
0 security-review — threat-model epic scope → specs/security/epics/<id>/THREAT_MODEL.md
1 survey-context — confirm epic + story
2 plan-work — flesh out story tasks[] in specs/epics/eNN-slug/epic.yaml
3 kickoff-branch — feature branch + clean baseline
4 develop-tdd — red-green per task
5 verify-work — UAT + mechanical gates
6 audit-code — non-optional gate (pass/fail; fail → loop back to step 4)
7 commit-message — Conventional Commits draft
8 release-branch — PR or solo land (supports --squash-state)

Process

  1. Read specs/state.yaml, specs/execution-status.yaml, specs/release-plan.yaml, active specs/epics/eNN-slug/epic.yaml.
    • On story start (step 1): Write started_at ISO 8601 timestamp to execution-status.yaml under the story's key in the stories: section. The bp-timing.sh script already tracks skill-level timings — this is story-level.
  2. Step 0 — Threat Model: Run security-review against the epic's scope (read from the epic capsule). Output specs/security/epics/<epic-id>/THREAT_MODEL.md with surface area, vulnerability categories, risk level, and mitigation guidance.
  3. Assess Impact (Step 2): Before writing tasks, run assess-impact --lightweight on the proposed change. If the risk score exceeds 7, gate — require a grill-me session. Write the impact report to specs/IMPACT-<epic>-<story>.md. For net-new code with no existing dependents, skip.
  4. BCP Tracking (Step 2): After plan-work completes, read the bcps: count (Business Complexity Points story size) from the epic capsule and carry it into state.yaml as epic_cycle.story_bcps = N.
  5. BCP Plus (Step 2, optional): When the epic capsule carries a bcp_plus_breakdown (13-dimension sizing), also carry it into state.yaml as epic_cycle.bcp_plus. The breakdown maps each of the 13 dimensions to an integer count. NFR dimensions (11–13) that are N/A per the NFR Gate may be set to 0.
  6. If epic_cycle.step missing, set to 1.
  7. Run only the current step (resume mode) unless user asked for full auto-run.
  8. After step verify passes, increment epic_cycle.step in state.yaml (or bash scripts/bp-yaml-set.sh if available).
  9. On story complete, set execution-status.yaml story key to done; run bash scripts/sync-status-from-epics.sh.
    • On story complete (step 8): Write completed_at ISO 8601 timestamp to execution-status.yaml under the same story key. Format:

Read the full file on GitHub · 105 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.

  1. today First seen · 105 lines · 50 tokens per session scan A 88a8f06e42fb

Subscribe to this mod's changes

build-epic is a cursor rule published in the GitHub repository danielvm-git/bigpowers (163 stars, last pushed 2d ago), licensed MIT. It adds 50 tokens to every session and 1,902 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.

Git and workflowPlanningai-agentsautomationbmadclaude-codeclean-codecursor-rules
Related

Other cursor rules, from other repositories

ponytail

Ponytail, lazy senior dev mode. Always pick the simplest solution that works.

DietrichGebert/ponytail · 576 tokens

app-router-patterns

Next.js 14+ App Router patterns — Server Components, Client Components, Route Handlers, Server Actions, and metadata API.

tugkanboz/awesome-cursorrules · 0 tokens

context-os

ContextOS rules for context-os.

kok-o/koko-contextos-agents · 6 tokens

database

Database architecture, schema design, Prisma, Drizzle ORM, indexing strategies, migrations, and N+1 query resolution.

kok-o/koko-contextos-agents · 24 tokens

vue

Rules for Vue (2 and 3) single-file components.

inboxpraveen/Minimize-Cursor-Cost · 0 tokens

nextjs

ContextOS rules for nextjs.

kok-o/koko-contextos-agents · 0 tokens