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-vnext-coregit 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-vnext-core)<a href="https://agentmods.dev/skills/keithhegit/ultra-orchestration/ultra-vnext-core"><img src="https://agentmods.dev/badge/skills/keithhegit/ultra-orchestration/ultra-vnext-core/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-vnext-core"><img src="https://agentmods.dev/badge/skills/keithhegit/ultra-orchestration/ultra-vnext-core.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.00951 |
| Opus 5.5 | $0.00032 | $0.00380 |
| Sonnet 5.5 | $0.00016 | $0.00190 |
| Haiku 4.5 | $0.00008 | $0.00095 |
Grade A, and why
ultra-vnext-core 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 2mo 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ultra VNext Core
Use this skill as a compatibility alias for the mainline $ultra-orchestrator
protocol. The user should not need to list every subskill.
Prefer the same behavior as the new main entry point:
$ultra-orchestrator <task description>
$ultra-vnext-core <task description> remains valid for existing users and
pilot runs.
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.
Strict Control Plane
For STRICT and STRICT_OPENSPEC, the run must use:
scripts/new_run.pyto initialize a run directoryledger.jsonas the execution state record- JSON
TaskManifest - JSON
WorkPackage - JSON or structured
AgentResult scripts/validate_contracts.pyfor core artifact validation- explicit review and QA gates
- final
control_surface_used
If a required script or artifact cannot be used, stop with a blocker instead of silently downgrading to markdown-only orchestration.
What ships with it
8 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.
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.
- 2mo ago First seen · 128 lines · 81 tokens per session scan A eed6f7c20d17
ultra-vnext-core is a skill published in the GitHub repository keithhegit/ultra-orchestration (6 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 81 tokens to every session and 951 once invoked, about $0.0003 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-31.
Other skills, from other repositories
gsd-audit-milestone
Audit milestone completion against original intent before archiving.
gsd-ns-manage
Invoke this Pi skill with /skill:gsd-ns-manage.
gsd-validate-phase
Retroactively audit and fill Nyquist validation gaps for a completed phase.
dependency-upgrade
Plan, batch, and verify dependency upgrades safely. Triages outdated packages into risk tiers, upgrades in order (dev/minor/patch first, runtime majors last), verifies each batch, and produces an auditable commit sequence. Use when asked to "upgrade deps", "bump packages", "update nodemodules", "fix vulnerabilities"…
forensics
Post-mortem a failed GSD auto-mode run. Traces symptom to root cause via .gsd/ activity, journal, metrics, and lock artifacts, producing a filing-ready bug report with file:line refs and a fix suggestion. Use when asked to "forensics", "post-mortem", "why did auto-mode fail", "trace the stuck loop", "debug the crash"…
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"…