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/execute-plangit 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/execute-plan)<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/execute-plan"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/execute-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 | $0.00034 | $0.00582 |
| Opus 5 | $0.00017 | $0.00291 |
| Sonnet 5 | $0.00007 | $0.00116 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
execute-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 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.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execute Plan
Execute tasks from the active epic (specs/epics/eNN-slug/epic.yaml story tasks[]) one at a time, showing evidence after each step before proceeding.
HARD GATE — Do NOT proceed if on
mainormaster. Runkickoff-branchfirst.HARD GATE — Active epic must exist with runnable
verifyon each task. If missing, runplan-releasethenplan-workorbuild-epic.
Process
1. Read the plan
Read specs/state.yaml (active_epic, active_story) and the matching specs/epics/*/epic.yaml. Parse depends-on in task descriptions for execution waves.
CONTEXT ISOLATION — Spawn each skill with a fresh context window. Pass decisions only through
specs/state.yamlhandoff— never rely on prior chat history.
Confirm with the user: step count, skip/reorder, stop-after step.
2. Execute step by step
For each task in the active story:
a. Announce — task desc and verify command.
b. Execute — code or delegate-task / dispatch-agents for waves.
c. Run verify — must be green before advancing.
d. Log — non-obvious decisions in specs/state.yaml under decisions[] or handoff block.
e. Checkpoint — ask to proceed unless autonomous mode requested.
f. Story UAT — after last task, run manual verification script from story notes or verify-work.
On verify failure: fix and re-run; never advance on red.
Update specs/execution-status.yaml when a story/epic completes (bash scripts/sync-status-from-epics.sh or direct edit).
3. Blockers
Report blocker; ask skip/adapt/stop; update epic capsule if plan changes.
4. Final report
Suggest: verify-work → run-evals → audit-code → simulate-agents → commit-message → release-branch
Rules
- Loop until behavioral correctness is verified: if a verify command passes but the observed behavior is still wrong, return to step 1 and run the execution cycle again.
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 · 61 lines · 34 tokens per session scan A a8c02db43fe7
execute-plan is a cursor rule published in the GitHub repository danielvm-git/bigpowers (163 stars, last pushed 2d ago), licensed MIT. It adds 34 tokens to every session and 582 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.
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.