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/data-wise/craft/plan-orchestratornpx skills add Data-Wise/craft --skill plan-orchestratorgit clone --depth 1 https://github.com/Data-Wise/craftWhat 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.00138 | $0.04338 |
| Opus 5 | $0.00069 | $0.02169 |
| Sonnet 5 | $0.00028 | $0.00868 |
| Haiku 4.5 | $0.00014 | $0.00434 |
Grade A, and why
plan-orchestrator 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 — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Orchestrator Skill
Produces concrete planning artifacts from specs and feature requests. Where project-planner advises on strategy ("how should we estimate?"), this skill emits files and structured backlogs ready to drive implementation: ORCHESTRATE-<topic>.md, feature task trees, sprint commitments, and visual roadmaps.
When to Use
Activate when the user wants a deliverable (file, backlog, milestone list), not just guidance:
- "Generate ORCHESTRATE from
docs/specs/SPEC-auth-*.md" - "Break this feature into tasks with estimates"
- "Plan next sprint, 80 hours capacity"
- "Generate a 6-month roadmap as mermaid"
- "Turn this brainstorm into a planning doc"
Do not use for: routing a single task to a command (use task-analyzer), saving session state (use session-state), or general "how do I plan?" advice (use project-planner).
Differentiation Map
| Need | Skill |
|---|---|
| "What command should I run for X?" | task-analyzer |
| "Save / resume my orchestrator session" | session-state |
| "Coach me on estimation / agile practices" | project-planner |
| "Generate the actual plan file" | plan-orchestrator (this) |
Four Planning Modes
This skill consolidates four commands. The user's phrasing selects the mode:
1. Spec → ORCHESTRATE (orchestrate:plan)
Trigger: spec file mentioned, or "implementation plan from SPEC".
Flow:
- Discover specs in
docs/specs/SPEC-*.md(andBRAINSTORM-*.mdlacking specs). - Parse selected spec: title, phases/increments, acceptance criteria, key files, cross-repo references.
- Detect cross-repo work (paths under
~/projects/<other>/); enforce same branch name across repos. - Confirm plan with user (ORCHESTRATE+worktree / ORCHESTRATE-only / modify / cancel).
- Generate
ORCHESTRATE-<topic>.mdwith sections: Objective, Phase Overview, Phase 1..N, Friction Prevention, Acceptance Criteria, Commit Strategy, Verification, Session Instructions. - Create worktree at
~/.git-worktrees/<project>/feature-<topic>fromdevif selected. - Update
.STATUSand.gitignore. - Branch on
output:orchestrate-worktree(default) ororchestrate-only→ instruct the user tocdinto the worktree and start a new session — do NOT begin implementation (STOP-new-session mode).orchestrate-dispatch→ skip the STOP instruction; instead run the confirm-before-dispatch gate (below), then dispatch a backgroundAgentcall from this same live session. See "orchestrate-dispatchmode" below for the full flow.
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 · 340 lines · 138 tokens per session scan A 5bd6f6c2d5b8
plan-orchestrator is a skill published in the GitHub repository Data-Wise/craft (4 stars, last pushed 16d ago), licensed MIT. It adds 138 tokens to every session and 4,338 once invoked, about $0.0007 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
dispatch
Use when a task file exists in .hyperflow/tasks/ and workers need dispatching. Fans out parallel workers under per-batch Reviewers, runs a final integration review, and commits per sub-task. Endpoint of the auto-chain — no auto-deploy. Trigger with /hyperflow:dispatch, "run the plan", "execute the task", "build it"…
agency-os
Notion-as-source-of-truth dispatch board for running your work like an AI agency. One Tasks database is the source of truth; tasks flow Suggestion through Discussion, To-Do, In Progress, and Done with subtasks, recurring cadences, dependencies, and template subtrees. Batch execution fans approved To-Do rows out to…
roadmap
Maintain and update the Atmos roadmap page (website/src/data/roadmap.js): milestone/initiative/quarter schema, progress-percentage math, the curated featured[] cap (max 6, never auto-modified), and the no-changelog-for-internal-refactors gate. Invoke when adding/updating milestones, initiatives, or quarters, or…
handoff
Use when managing a two-session handoff — inspecting, picking up, or reviewing a committed handoff package produced by a session=two scope run. The operator interface over the cross-environment handoff lifecycle (plan in one session, build in another, review back in the first). Trigger with /hyperflow:handoff, "list…
orchestrate
Pipeline orchestration: dispatch the highest-priority ready tasks/work units to agents, manage capacity, and coordinate the Todo to Done flow. Invoked as /agiflow:orchestrate. Uses listtasks, listactivetasksbyorg, listmembers, updatetask, getworkunitprogress.
meeting-minutes
Turn a meeting transcript, notes, or conversation into collision-safe, source-linked minutes in meetings/YYYY-MM-DD-slug.md. Use for project meeting records, attendance, discussion, stated information, decisions, action candidates, and open questions. Saving minutes never changes PROJECT.md, decisions/, or TASKS.md…