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 skills/danielvm-git/bigpowers/orchestrate-projectnpx skills add danielvm-git/bigpowers --skill orchestrate-projectgit clone --depth 1 https://github.com/danielvm-git/bigpowersWhat 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.00054 | $0.02294 |
| Opus 5 | $0.00027 | $0.01147 |
| Sonnet 5 | $0.00011 | $0.00459 |
| 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 2d ago.
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 — 175 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.
- 2d ago First seen · 175 lines · 54 tokens per session scan A 96b4f693eef6
orchestrate-project is a skill published in the GitHub repository danielvm-git/bigpowers (156 stars, last pushed 25d ago), licensed MIT. It adds 54 tokens to every session and 2,294 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-08-30.
Other skills, from other repositories
shared/tech-stack-detection
检测项目技术栈的通用方法，通过分析配置文件识别语言、框架、工具链.
devops/changelog-generation
自动生成 CHANGELOG，基于 git 提交历史和 pipeline 产物信息，遵循 Conventional Commits 和 Keep a Changelog 规范.
boss
可审计的 agent 团队：BMAD 全自动研发流水线编排器。编排 9 个专业 Agent（PM、架构师、UI Designer、Tech Lead、Scrum Master、Frontend、Backend、QA、DevOps）从需求到部署，每一步都有事件溯源 + 不可绕过门禁 + 确定性 eval——可验证测试真跑、门禁真过。支持单环节切片命令（/boss:plan /review /qa /ship）与无 CLI 纯 Markdown 降级。 Triggers: 'boss mode', '/boss', '全自动开发', '从需求到部署', '帮我做一个', 'build this', 'ship it', '全流程'…
debloat
Compress an artifact that has accreted into bloat — padding, over-qualification, fused sentences, walls of enumeration, adjacent restatement — down to its load-bearing density, meaning preserved. Use when prose is correct and current but has grown verbose or patched-over and you want it tight without a full rewrite.
bmad-dev-story
Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan".
bmad-validate-prd
Validate a PRD against standards. Use when the user says "validate this PRD" or "run PRD validation".