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/dcosson/h2/plan-orchestratenpx skills add dcosson/h2 --skill plan-orchestrategit clone --depth 1 https://github.com/dcosson/h2What 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.00043 | $0.05489 |
| Opus 5 | $0.00022 | $0.02745 |
| Sonnet 5 | $0.00009 | $0.01098 |
| Haiku 4.5 | $0.00004 | $0.00549 |
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 — 377 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Orchestrate
Orchestrate the full planning lifecycle for a project. This skill is a structured decision framework for the concierge/scheduler agent — it defines what to do at each phase, what judgments to make, and when to proceed. It is NOT a fully automated script; the orchestrating agent uses judgment throughout.
The individual steps (review, incorporate, summarize) are already separate skills. This skill is the connective tissue that ties them together into a repeatable, consistent process that can proceed with minimal user prompting.
Inputs
$0: Path to starting material (shaping doc, architecture doc, feature exploration doc, or requirements doc)
Phase 0: Input Assessment
Read whatever starting material exists. Determine the current state:
- Is there a shaping doc? If requirements are vague or the solution approach is undefined, run the
shapingskill first. - Is there an architecture doc? If
docs/plans/00-architecture.mdexists, skip to Phase 2 or 3. - Is there a plan index? If
docs/plans/00-plan-index.mdexists with sub-plans listed, skip to Phase 2. - Are plan docs already written? If plan docs exist, skip to Phase 3 (review cycles).
Decision: Skip to the appropriate phase based on what exists. Communicate the assessment to the user via h2 send.
Phase 1: Architecture
Assign an agent to run plan-architect with the input doc. This produces:
docs/plans/00-architecture.mddocs/plans/00-plan-index.md(if the project needs multiple sub-plans)
After the architecture doc is written:
- Create a planning epic bead:
bd create "Planning: {project-name}" --type epic - Create a task bead for each plan doc listed in the plan index
- Set dependencies between beads matching the dependency order in the plan index
Phase 2: Plan Writing
Assign plan-draft beads to available agents. Rules:
- Respect dependency order from the plan index (batch 1 first, then batch 2, etc.)
- Within a batch, parallelize across agents
- Each agent drafts one plan doc + its companion test harness doc
- A bead is done when both docs are committed
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 · 377 lines · 43 tokens per session scan A c3c199caf928
plan-orchestrate is a skill published in the GitHub repository dcosson/h2 (159 stars, last pushed 6d ago), licensed MIT. It adds 43 tokens to every session and 5,489 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-08-30.
Other skills, from other repositories
mcporter
List, auth, and call MCP servers/tools from the terminal.
📝 任务完成后归档
重要提醒: 每次完成复杂调试或开发任务后，主动执行此流程！ 将学到的经验归档为 skill，供以后参考。不要等用户提醒。.
oracle
Best practices for using the oracle CLI (prompt + file bundling, engines, sessions, and file attachment patterns).
agent-mode
Unified tool for managing agent LLM modes (add, remove, update, list, switch).
agento11y-prod-setup
Sets up production evaluation and guardrails for a DEPLOYED AI agent in Grafana Agent Observability, grounded in the agent's own code and its real ingested traffic. The judgment layer on top of the agento11y skill: it reads the agent's source (system prompt, tools, entrypoint) AND samples its live traffic via gcx…
mcp-scripting
Write mcpScript JavaScript for discovering, inspecting, and calling MCP tools.