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 dremonkey/agents-and-skills --skill orchestrate-initiative-planninggit clone --depth 1 https://github.com/dremonkey/agents-and-skillsWrote 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/dremonkey/agents-and-skills/orchestrate-initiative-planning)<a href="https://agentmods.dev/skills/dremonkey/agents-and-skills/orchestrate-initiative-planning"><img src="https://agentmods.dev/badge/skills/dremonkey/agents-and-skills/orchestrate-initiative-planning/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/dremonkey/agents-and-skills/orchestrate-initiative-planning"><img src="https://agentmods.dev/badge/skills/dremonkey/agents-and-skills/orchestrate-initiative-planning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00081 | $0.02316 |
| Opus 5 | $0.00041 | $0.01158 |
| Sonnet 5 | $0.00016 | $0.00463 |
| Haiku 4.5 | $0.00008 | $0.00232 |
Grade A, and why
orchestrate-initiative-planning 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 11d 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrate Initiative Planning
Purpose
Use this skill when the user wants one agent to coordinate the full planning pipeline:
- Product definition
- Technical architecture
- Execution planning
This skill is an orchestrator. It should launch sub-agents, manage handoffs, answer sub-agent questions when possible, and stop before implementation.
Workspace Isolation
All work MUST happen in a git worktree.
Before doing anything else — before reading source docs, before launching sub-agents — enter a worktree:
- Use
EnterWorktreewith a name derived from the initiative (e.g.,plan-<INITIATIVE>). - All subsequent file creation and sub-agent work happens inside the worktree.
- Do not write any planning artifacts to the main working tree.
If EnterWorktree fails (e.g., already in a worktree), halt and ask the user how to proceed.
Artifact Contract
The orchestrated workflow should produce:
- Product artifacts in
tasks/<EPIC_NAME>/VISION.md(large initiatives only)PRD.<TOPIC>.md
- Top-level
VISION.mdupdate — high-level entry capturing the initiative's intent (large initiatives only) - Architecture docs in
docs/architecture/— organized by system or topic, not by initiative - Execution artifacts in
tasks/<EPIC_NAME>/EPIC.md- task files
Core Rule
Do not implement product code in this workflow.
plan-eng-tasks is planning-only — it produces task files but does not implement them. When execution is needed after planning, use exec-eng-tasks to dispatch sub-agents for implementation.
In this orchestrated workflow, plan-eng-tasks produces:
- updated
EPIC.md - task files
- any required architecture doc clarifications
It does not dispatch implementation sub-agents or write code. If the user wants to proceed to execution after the planning PR is merged, invoke exec-eng-tasks separately.
Stage Workflow
Stage 1: CEO Product Review
Launch a sub-agent that applies plan-requirement-doc.
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.
- 11d ago First seen · 253 lines · 81 tokens per session scan A f5fdf7084569
orchestrate-initiative-planning is a skill published in the GitHub repository dremonkey/agents-and-skills (2 stars, last pushed 27d ago), licensed MIT. It adds 81 tokens to every session and 2,316 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…