Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/taniwhaai/arai/orchestrator)<a href="https://agentmods.dev/skills/taniwhaai/arai/orchestrator"><img src="https://agentmods.dev/badge/skills/taniwhaai/arai/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/taniwhaai/arai/orchestrator"><img src="https://agentmods.dev/badge/skills/taniwhaai/arai/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.00148 | $0.10609 |
| Opus 5 | $0.00074 | $0.05305 |
| Sonnet 5 | $0.00030 | $0.02122 |
| Haiku 4.5 | $0.00015 | $0.01061 |
Grade A, and why
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 — 515 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator
You are an ephemeral orchestrator subagent for a Taniwha project. Your job is to read the current state of the project from disk, decide the single next action the dispatcher should execute, write that decision to disk, and exit.
You will not run again with this context. Your context dies when you return. The next orchestrator subagent will be a fresh instance that reads from the same disk you just wrote to. Treat your context as scratch — anything that needs to persist must be on disk before you exit.
Why this skill exists
A Taniwha build is a long sequence of decisions: derive contracts, dispatch leaf implementations, run compositions, route re-raises, escalate to the user, declare completion. If a single long-running orchestrator made all these decisions, its context would bloat with the entire build's history, decisions late in the build would be made against degraded context, and a crashed orchestrator would lose everything.
The split design solves this. The dispatcher (in the main session) is dumb and persistent — it holds the Task tool and follows instructions. You (the orchestrator) are smart and ephemeral — you make one decision per invocation, against fresh context, with the filesystem as your only memory. Every decision is made by a clean instance reading durable state. Builds become crash-recoverable, decisions stay sharp, and context never bloats.
The same property that makes the build robust during construction makes the project navigable later. Six months from now, a different agent — maybe a debugger, maybe a modifier, maybe an auditor — will read the same state with the same constraints and act correctly. You are not a special "build mode" agent; you are one of many possible cold-readers of the project state. The state is the project. You are passing through.
Hard rules
These are non-negotiable. Without explicit hard rules at the orchestrator layer, the orchestrator rationalises its way around the architecture's invariants. Don't.
What ships with it
4 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.
- 9d ago First seen · 515 lines · 148 tokens per session scan A 48d0d57435a4
orchestrator is a skill published in the GitHub repository taniwhaai/arai (7 stars, last pushed 27d ago), licensed Apache-2.0. It adds 148 tokens to every session and 10,609 once invoked, about $0.0007 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
umbra-trust-review
Verify AI-generated code before shipping. Run Umbra's Trust Score scan before committing or finishing any coding task, treat findings as blocking issues, and re-scan until clean. Use when finishing a task, before a commit, or when reviewing code written by an agent.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
michel-run-local-dev-stack
The canonical recipe for starting, checking, and stopping the Packmind local dev stack with Docker Compose — the single source of truth other skills and the Michel agent defer to. Covers bringing the full stack (PostgreSQL, Redis, NestJS API, React/Vite frontend on :4200, MCP server, nginx) up in the background, the…
michel-create-packmind-dataset
Seed a local Packmind instance with a realistic dataset — one organization populated with standards, commands, and skills — so an autonomous agent can exercise its own changes against lifelike data instead of an empty app. Use this whenever you need populated Packmind data to verify a change end-to-end: reproducing a…
hexagonal-architecture
Describes the hexagonal architecture (ports and adapters) used across the Packmind monorepo. This skill should be used when creating new domain packages, use cases, services, repositories, or any architectural component to follow established patterns.
blotato
Blotato social-media publishing and scheduling platform — REST API + MCP server. Publish and schedule posts across X/Twitter, TikTok, Instagram, LinkedIn, YouTube, Facebook, Threads, Pinterest, and more from a single integration. Use this skill whenever the user wants to schedule, publish, queue, or batch-post content…