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 ultra-orchestratorgit 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/ultra-orchestrator)<a href="https://agentmods.dev/skills/keithhegit/ultra-orchestration/ultra-orchestrator"><img src="https://agentmods.dev/badge/skills/keithhegit/ultra-orchestration/ultra-orchestrator/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/keithhegit/ultra-orchestration/ultra-orchestrator"><img src="https://agentmods.dev/badge/skills/keithhegit/ultra-orchestration/ultra-orchestrator.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.00090 | $0.01555 |
| Opus 5 | $0.00045 | $0.00777 |
| Sonnet 5 | $0.00018 | $0.00311 |
| Haiku 4.5 | $0.00009 | $0.00155 |
Grade A, and why
ultra-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 9d 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ultra Orchestrator
Use this skill as the default public entry point for Ultra Orchestration.
The user should only need to invoke $ultra-orchestrator <task description>.
This is the mainline successor to the vNext protocol. The old stable workflow
is preserved as ultra-orchestrator-legacy.
Startup Contract
Recommended invocation:
$ultra-orchestrator <task description>
OpenSpec invocation:
$ultra-orchestrator OpenSpec change <change-id or path>: <task description>
Compatibility invocation:
$ultra-vnext-core <task description>
If the client exposes slash aliases, /ultra-orchestrator can be used the same
way.
Run Mode Decision
Classify the run before planning or execution:
LIGHTreview-only, QA-only, explanation-only, or user-explicit lightweight workSTANDARDuser-explicit fast orchestration with bounded risk and no full control planeSTRICTdevelopment work where OpenSpec is unavailable but ledger and JSON contracts are still requiredSTRICT_OPENSPECdefault for development work, bug fixes, multi-file implementation, pilots, full orchestration tests, OpenSpec work, slice DAG work, and control-plane validation
Development tasks must prefer STRICT_OPENSPEC. If that mode is impossible,
explain why and downgrade explicitly. Markdown-only artifacts are not enough
for STRICT or STRICT_OPENSPEC.
Router Duties
When invoked:
- classify the task and choose
run_mode - create or require OpenSpec change scaffolding when
STRICT_OPENSPECapplies - initialize the run ledger for
STRICTandSTRICT_OPENSPEC - route through the minimal required sibling skills
- validate machine-checkable artifacts before delivery
- produce delivery artifacts or a clear blocker
Do not ask the user to manually name every subskill.
Routing Table
| Task signal | Default mode | Route |
|---|---|---|
| development, feature, bugfix, multi-file implementation, pilot, full orchestration test | STRICT_OPENSPEC |
OpenSpec bootstrap or bridge -> planning -> risk -> dispatch -> review -> QA -> delivery |
existing OpenSpec change path, openspec/changes, proposal/design/tasks, archive workflow |
STRICT_OPENSPEC |
bridge -> planning -> risk -> dispatch -> review -> QA -> delivery |
| development task where OpenSpec cannot be used | STRICT |
planning -> risk -> dispatch -> review -> QA -> delivery |
| review-only request | LIGHT |
review -> delivery |
| QA-only request | LIGHT |
QA -> delivery |
| high-risk command, publishing, destructive write, credentials, external mutation | current mode plus risk gate | risk before execution |
What ships with it
12 files 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.
- agents/openai.yaml 337 B
- references/contracts.md 2.8 KB
- references/design-tenets.md 772 B
- references/examples.md 436 B
- references/review-lenses.md 707 B
- references/routing.md 1.9 KB
- references/source-synthesis.md 1.3 KB
- references/state-machine.md 675 B
- references/workflow.md 1.5 KB
- scripts/new_run.py 2.8 KB runs code
- scripts/validate_contracts.py 2.6 KB runs code
- scripts/validate_run.py 1.9 KB runs code
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.
- 9d ago First seen · 209 lines · 90 tokens per session scan A c46aa36ffa83
ultra-orchestrator is a skill published in the GitHub repository keithhegit/ultra-orchestration (6 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 90 tokens to every session and 1,555 once invoked, about $0.0005 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-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-audit-milestone
Audit milestone completion against original intent before archiving.
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…