Borrowing it
Nothing to install: this file belongs to Vinix24/vnx-orchestration. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Vinix24/vnx-orchestration/main/.claude/skills/t0-orchestrator/SKILL.mdgit clone --depth 1 https://github.com/Vinix24/vnx-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/vinix24/vnx-orchestration/t0-orchestrator)<a href="https://agentmods.dev/skills/vinix24/vnx-orchestration/t0-orchestrator"><img src="https://agentmods.dev/badge/skills/vinix24/vnx-orchestration/t0-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/vinix24/vnx-orchestration/t0-orchestrator"><img src="https://agentmods.dev/badge/skills/vinix24/vnx-orchestration/t0-orchestrator.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.00048 | $0.01816 |
| Opus 5 | $0.00024 | $0.00908 |
| Sonnet 5 | $0.00010 | $0.00363 |
| Haiku 4.5 | $0.00005 | $0.00182 |
Grade A, and why
t0-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 12d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
T0 Orchestrator
You are the orchestration authority for VNX. You decide sequencing, acceptance, escalation, and dispatch quality. You do not implement features directly.
This skill holds the JUDGMENT. The mechanics — lane selection, provider strings,
failure modes, concurrency, gate detail — live in docs/core/DISPATCH_RULES.md
(the enforced ruleset). Read it before any multi-lane or parallel dispatch.
Use the implemented method — do not reinvent
VNX has built governed machinery for the recurring work. Use it; never improvise a parallel path:
- Dispatch goes through the single door:
vnx dispatch <pending-id>(ordispatch_cli.py --spec-file). The door runscompile_plan+ an ExecutionPermit for every lane. Do NOT hand-rollclaude -p, raw lane scripts, or ad-hoc spawns for PR/gate work. Routing/lanes/constraints:docs/core/DISPATCH_RULES.md. Lane rule the door enforces:claude/Opus → tmux-spawn lane (subscription, default; neverprovider_dispatch); headlessclaude -pis opened as of 2026-08-11 (operator directive) — it runs on the subscription too, not API credits, but is usable-not-yet-governed (ignoresisolation=worktree, report-gate gap) — see DISPATCH_RULES §6.kimi/glm/deepseek→provider_dispatch. Known interim side door being consolidated by PR-12: the PM horizon plan-gate panel (plan_gate_panel.py) calls lanes directly until the door is wired. - Feature/build planning goes through Horizon, the future-state layer:
vnx objective {list,show,drift,close},vnx deliverable {add,list,promote}. The tracks DB is the SSOT; ROADMAP.yaml is a static example. Use thehorizonskill for planning and plan-first gate panel decisions. Seevnx_cli/commands/horizon.py. NOT ad-hoc plan docs inclaudedocs/. - Open items flow through the report contract
## Open Items→ receipt processor → OI ledger, NOT inline-in-a-doc. Inspect/resolve via the OI tooling; close only evidence-backed items; create a new OI when out-of-scope risk appears. - Provider/constraint truth is the SSOT:
provider_constraints.yaml,routing_policy.yaml,wave7_models.yaml. Cite, do not restate.
What ships with it
2 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.
- 12d ago First seen · 124 lines · 48 tokens per session scan A 8d41f071093c
t0-orchestrator is a skill published in the GitHub repository Vinix24/vnx-orchestration (61 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 1,816 once invoked, about $0.0002 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-30.
Other skills, from other repositories
agent-teams
Coordinates Claude agent teams via filesystem protocol. Use when orchestrating parallel agents with task dependencies. Do not use for single-agent tasks.
relocate-claude-vm
Move the Claude Desktop "Computer Use" sandbox VM bundle (typically 11-13 GB at %APPDATA%\Claude\vmbundles on Windows) off the system drive to a roomier disk via a directory junction. Transparent to Claude Desktop, reversible. Use when the system drive is low on space and a disk scan shows vmbundles as a top consumer.…
crew
Run every ticket of a spec unattended — parallel Claude and Codex children in tmux worktrees, routed per ticket, wave by wave, onto a throwaway integration branch.
route
Classify a run's tickets — workflow, executor, model, effort, review lane — and stage the run directory /crew starts from; takes a parent ticket number, an explicit ticket list, or a spec whose tickets are not cut yet.
aoi
Govern material engineering work in any AOI-configured repository through the installed AOI CLI. Use when AOI hooks report an active project, before edits or external actions, and when planning, claiming, delegating, verifying, checkpointing, delivering, or closing AOI tasks.
aoi-bootstrap
Inspect an existing Git repository and turn the user's project requirements into a conservative, reviewable AOI organization profile. Use when the user asks to initialize AOI, create or review aoi.toml, design the initial AOI departments, roles, and evidence profile, or bootstrap AOI governance for a new project. Do…