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 keithhegit/ultra-orchestration --skill decision-complete-plannergit clone --depth 1 https://github.com/keithhegit/ultra-orchestrationWrote 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/keithhegit/ultra-orchestration/decision-complete-planner)<a href="https://agentmods.dev/skills/keithhegit/ultra-orchestration/decision-complete-planner"><img src="https://agentmods.dev/badge/skills/keithhegit/ultra-orchestration/decision-complete-planner.svg" alt="Measured on agentmods" 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.00054 | $0.00345 |
| Opus 5 | $0.00027 | $0.00172 |
| Sonnet 5 | $0.00011 | $0.00069 |
| Haiku 4.5 | $0.00005 | $0.00034 |
Grade A, and why
decision-complete-planner 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 7d 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.
What it actually says
Decision Complete Planner
Produce a plan another agent can execute without filling in key decisions.
In mainline STRICT or STRICT_OPENSPEC runs, planning must produce
JSON-ready artifacts. Markdown summaries may explain the plan, but they do not
replace the machine-checkable TaskManifest and WorkPackage objects.
Produce
- Short summary
- Ordered implementation phases
- JSON
TaskManifestentries - JSON
WorkPackageentries - Parallel vs serial execution boundaries
- Acceptance checks per package
- Retry budget assumptions for each non-trivial work package
- Current OpenSpec change and slice status when
STRICT_OPENSPECapplies
Use canonical field names from ../ultra-orchestrator/references/contracts.md.
Rules
- Prefer behavior-level decomposition over file-by-file decomposition.
- Mark shared write scope explicitly.
- Treat shared write scope as a write-lock conflict, not a soft warning.
- Keep non-goals visible.
- If a design choice is still unresolved, surface it instead of hiding it in prose.
- For development tasks, prefer one bounded OpenSpec change and one current slice before dispatch.
- Do not send work to dispatch if artifact validation cannot be planned.
Hand off
Send the plan to $spec-review for completeness, then to $dispatch-and-track.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 41 lines · 54 tokens per session scan A aa4005673692
decision-complete-planner is a skill published in the GitHub repository keithhegit/ultra-orchestration (6 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 54 tokens to every session and 345 once invoked, about $0.0003 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
gsd-plan-review-convergence
Cross-AI plan convergence - replan until review concerns are resolved.
gsd-audit-milestone
Audit milestone completion against original intent before archiving.
gsd-ns-manage
Route to the appropriate management skill based on the user's intent. gsd-config (settings + advanced + integrations + profile) and gsd-workspace (new + list + remove) are post-#2790 consolidated entries.
gsd-validate-phase
Retroactively audit and fill Nyquist validation gaps for a completed phase.
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…
spec-kitty-spdd-reasons
Drive REASONS Canvas authoring and review for Spec Kitty missions that opted in to Structured-Prompt-Driven Development (SPDD) via charter selection. Triggers: "use SPDD", "use REASONS", "generate a REASONS canvas", "apply structured prompt driven development", "make this mission SPDD". Does NOT handle: enforcing SPDD…