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/23ag1/completely/plan-orchestratenpx skills add 23ag1/completely --skill plan-orchestrategit clone --depth 1 https://github.com/23ag1/completelyWhat 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.00075 | $0.04669 |
| Opus 5 | $0.00037 | $0.02335 |
| Sonnet 5 | $0.00015 | $0.00934 |
| Haiku 4.5 | $0.00007 | $0.00467 |
Grade A, and why
plan-orchestrate 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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Orchestrate
Bridge a plan document to /orchestrate custom by emitting one ready-to-paste invocation per step. The skill is generative only — it never executes /orchestrate. The user pastes each line when ready.
When to Activate
- User has a multi-step plan document (PRD, RFC, implementation plan) and wants to drive it through
/orchestrate. - User says "orchestrate this plan", "give me orchestrate prompts for each step", "compose chains for this plan".
- A step-by-step plan exists but the user does not want to manually pick agents per step.
Skip when:
- The work is one ad-hoc step → call
/orchestrate customdirectly. - The plan is unreadable or empty. Lack of explicit numbering alone is not a skip condition — see the "No clear steps" edge case below.
Inputs
<plan-doc-path> [--lang=python|typescript|go|rust|cpp|java|kotlin|flutter|auto] [--scope=all|step:<n>|range:<a>-<b>] [--dry-run]
<plan-doc-path>— required; relative or absolute path (@docs/...accepted).--lang— reviewer language variant; defaults toauto(detected from project).--scope— limits emitted steps; defaults toall.--dry-run— print decomposition + chain rationale only; do not emit final prompts.
Authoritative /orchestrate shape (do not deviate)
{ORCH_CMD} custom "<agent1>,<agent2>,...,<agentN>" "<task description>"
Where {ORCH_CMD} is determined in Phase 0 (see below). The command string in the emitted output always uses one concrete form — never both, never a placeholder.
customis a sequential chain; each agent's HANDOFF feeds the next.- Comma-separated agent list. No spaces preferred; one space tolerated.
- No
--mode/--gate/--agents=...flags exist — never invent them. - Agent names come from the catalogue in this skill. Embedded double quotes in the task description are escaped as
\".
ECC install form and namespacing
Two install forms determine the prefix on both the slash command and every agent name. The two MUST stay in sync — one form per output, never mixed:
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 · 263 lines · 75 tokens per session scan A 226ec75b26f3
plan-orchestrate is a skill published in the GitHub repository 23ag1/completely (5 stars, last pushed 2mo ago), licensed MIT. It adds 75 tokens to every session and 4,669 once invoked, about $0.0004 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-31.
Other skills, from other repositories
hive.chart-creation-foundations
Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
openai-whisper-api
Transcribe audio via OpenAI Audio Transcriptions API (Whisper).
perf-code-paths
Use when mapping code paths, entrypoints, and likely hot files before profiling.
compare-harnesses
Diff two scaffolded harnesses (ADR-031). Reports manifest meta drift + host list + per-file fingerprint changes (added/removed/changed). Exits 0 IDENTICAL, 1 DRIFT, 2 missing manifest. Use --bundle for the ADR-031 schema-1 JSON envelope.
repo-genome
7-section readiness scorecard for a LOCAL repo. Reports repo type + agent topology + MCP risk + test confidence + release readiness + recommended harness plan + scorecard. Exit 0 ready, 1 needs-work, 2 blocked. --json for the 6-field scorecard, --bundle for the ADR-031 schema-1 envelope.