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/orchestrate-projectgit 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/orchestrate-project)<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/orchestrate-project"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/orchestrate-project.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.00049 | $0.02288 |
| Opus 5 | $0.00024 | $0.01144 |
| Sonnet 5 | $0.00010 | $0.00458 |
| Haiku 4.5 | $0.00005 | $0.00229 |
Grade A, and why
orchestrate-project 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrate
HARD GATE — HARD GATE — Do NOT invoke orchestrate-project unless you have a clear multi-phase workflow. Single-skill tasks should use dedicated skills instead. Orchestrate is for complex, multi-stage work that requires coordination across phases.
The orchestrate skill coordinates projects through a prescriptive 6-phase core loop with hard gates, ensuring consistent quality and preventing scope creep.
Quick Start
# Start a new project (initializes specs/ YAML cockpit and begins discover phase)
claude /orchestrate --mode standard
# Or resume an existing project at the current phase
claude /orchestrate --mode standard --resume
# For low-risk scenarios (hotfixes, refactors on well-tested code)
claude /orchestrate --mode fast-track
The 6-Phase Core Loop
- DISCOVER (3-6 hours): Understand problem. Deliverables:
requirements/VISION_LATEST.yaml,requirements/SCOPE_LATEST.yaml,plans/TECH_STACK_LATEST.md. - ELABORATE (3-6 hours): Research solutions. Deliverables: Prior art in scope YAML, ADRs in
specs/adr/. - PLAN (2-4 hours): Write verifiable plan. Deliverables:
release-plan.yaml,epics/eNN-*.yamlwithverify:per task. - BUILD (1-8 hours): Execute plan. Runs build-epic once per story in WSJF order. Deliverables: Code; update
execution-status.yaml. - VERIFY (1-3 hours): Validate success criteria. Deliverables: UAT evidence,
specs/EVALS-*.mdif used. - RELEASE (30 min - 2 hours): Ship to production. Deliverables: Release tag (vX.Y.Z),
state.yamlrelease.last_tag.
Checkpoint / resume
Track progress via specs/state.yaml project_cycle:
project_cycle.current_phase: current phase (1–6)project_cycle.completed_phases: completed phase numbershandoff.next_skill: skill for the current phase- On resume, read
project_cycle.current_phaseand continue from there
See REFERENCE.md for detailed phase specifications and gate types.
How Orchestrate Works
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 · 174 lines · 49 tokens per session scan A a6c02b817fd8
orchestrate-project is a cursor rule published in the GitHub repository danielvm-git/bigpowers (163 stars, last pushed 2d ago), licensed MIT. It adds 49 tokens to every session and 2,288 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.