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 KirschBluteX/agent-orchestration-gateway --skill orchestrategit clone --depth 1 https://github.com/KirschBluteX/agent-orchestration-gatewayWrote 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/kirschblutex/agent-orchestration-gateway/orchestrate)<a href="https://agentmods.dev/skills/kirschblutex/agent-orchestration-gateway/orchestrate"><img src="https://agentmods.dev/badge/skills/kirschblutex/agent-orchestration-gateway/orchestrate/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/kirschblutex/agent-orchestration-gateway/orchestrate"><img src="https://agentmods.dev/badge/skills/kirschblutex/agent-orchestration-gateway/orchestrate.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.00057 | $0.00220 |
| Opus 5 | $0.00028 | $0.00110 |
| Sonnet 5 | $0.00011 | $0.00044 |
| Haiku 4.5 | $0.00006 | $0.00022 |
Grade A, and why
orchestrate 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.
What it actually says
Orchestrate
Load exactly one role reference:
- For the user-facing Primary that defines and supervises an initiative, read references/supervisor.md.
- For a task whose prompt identifies it as an AOG module task, read references/module.md.
Do not load both references or invent a third role. Validate an approved structural plan by sending its JSON to standard input of:
python -B <SKILL_ROOT>/scripts/validate_plan.py
The validator is stateless. AOG stores no lifecycle, lease, receipt, recovery, routing, or workspace files; Codex owns task, worktree, Goal, and wait state.
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 · 27 lines · 57 tokens per session scan A 17eac41bdfdf
orchestrate is a skill published in the GitHub repository KirschBluteX/agent-orchestration-gateway (7 stars, last pushed 23d ago), licensed MIT. It adds 57 tokens to every session and 220 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
orcast
Use when orchestrating multiple agents in Orca: fan out parallel workers, pipeline work across stages, adversarially verify findings, run judge panels or loop-until-dry sweeps, or delegate a task and get the result back. You write a Plan definition in real JavaScript — a worker-workflow graph of worker, action, and…
simply-pm
Use when you are spawned as the PM of a simply harness project and your brief references a .simply/LEDGER.md work ledger or this skill. Grants fleet authority, routing doctrine, safe worker lifecycle, and the signal protocol back to the auditor.
improve
Use ONLY when the user explicitly asks to optimize a measurable quantity of an existing system (performance, size, score, latency) and a trustworthy metric exists or can be justified. Most work does not need this; the standard criteria loop covers it.
sonol-multi-agent
Sonol multi-agent orchestration skill. Use when a user wants one request decomposed into single-agent or multi-agent execution, with local-AI creative draft generation, hosted normalization/binding, adapter-backed sub-agent controls, runtime reporting, dashboard monitoring, plan/run persistence, and final result…
sonol-agent-runtime
Sonol runtime helper skill for sub-agents participating in Sonol multi-agent orchestration. Use when a sub-agent must report progress, artifacts, completion, or session status into the shared dashboard and SQLite-backed run history.
code-review-excellence
This skill should be used when the user asks to review a diff or pull request, write review comments, audit code quality, establish review standards, or improve how a team performs code review.