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 skills add dcosson/h2 --skill plan-orchestrategit clone --depth 1 https://github.com/dcosson/h2Wrote 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/skills/dcosson/h2/plan-orchestrate)<a href="https://agentmods.dev/skills/dcosson/h2/plan-orchestrate"><img src="https://agentmods.dev/badge/skills/dcosson/h2/plan-orchestrate/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/dcosson/h2/plan-orchestrate"><img src="https://agentmods.dev/badge/skills/dcosson/h2/plan-orchestrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00043 | $0.05489 |
| Opus 5.5 | $0.00017 | $0.02196 |
| Sonnet 5.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 1mo 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.
- 1mo ago First seen · 377 lines · 43 tokens per session scan A c3c199caf928
plan-orchestrate is a skill published in the GitHub repository dcosson/h2 (163 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 5,489 once invoked, about $0.0002 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…