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 daman8271/the-perfect-orchestrator --skill skillgit clone --depth 1 https://github.com/daman8271/the-perfect-orchestratorWrote 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/daman8271/the-perfect-orchestrator/skill)<a href="https://agentmods.dev/skills/daman8271/the-perfect-orchestrator/skill"><img src="https://agentmods.dev/badge/skills/daman8271/the-perfect-orchestrator/skill/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/daman8271/the-perfect-orchestrator/skill"><img src="https://agentmods.dev/badge/skills/daman8271/the-perfect-orchestrator/skill.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.00133 | $0.01644 |
| Opus 5.5 | $0.00053 | $0.00658 |
| Sonnet 5.5 | $0.00027 | $0.00329 |
| Haiku 4.5 | $0.00013 | $0.00164 |
Grade B, and why
orch scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- **PERMISSIONS (the #1 blocker):** the permission classifier may *deny* autonomous spawns/sends. If `orch`/`tmux` calls get blocked, the user must add allow-rules to `~/.claude/settings.local.json`: `Bash(orch:*)` and ` This is a copy
95% identical to orch — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Perfect Orchestrator — lead playbook
You are the LEAD. This harness lets you spawn N autonomous Claude Code workers
(each its own tmux pane), brief each one, watch them, correct them, verify their
results, and drive them to completion — all from this one session. The CLI is orch
(run orch --help for usage; state lives under $ORCH_HOME, default ~/.orch).
The harness commands
| command | what it does |
|---|---|
orch spawn <session> <N> [workdir] |
Create tmux session orch-<session> with N worker panes + a shared workspace at $ORCH_HOME/runs/<session>/shared/ (contains bus.md; panes.txt lives one level up). Workers are numbered 1..N. Workdir defaults to the current directory. |
orch send <session> <#> --file <path> |
Dispatch a task: tells worker # "Read and follow <path> then begin, work autonomously." |
orch send <session> <#> <one-line msg> |
Send a short single-line nudge (NO newlines — newline submits). |
orch read <session> <#> [lines] |
Capture a worker's pane (to see what it's doing). |
orch status [session] |
Overview of all live fleets, or one fleet's panes + done-flags + bus tail. |
orch kill <session> |
Tear down a fleet when done. |
Workers launch with an isolated config (no hooks → no notification spam on every
turn, a generous allowlist → no permission prompts, shared live credentials,
ORCH_WORKER=1). When a worker's claude exits, its pane ends.
The workflow (do it in this order)
- PLAN — split the job into N independent sub-tasks (one per worker). Pick N deliberately (see Limits).
- SPAWN —
orch spawn <name> <N> [workdir]. Give workers a few seconds to boot (a pane showing a ready prompt = booted). - BRIEF — write each worker's brief to
$ORCH_HOME/runs/<name>/shared/agent-<i>.task.md. A good brief is self-contained: the goal, hard constraints (what NOT to touch), exactly what to produce, where to write its result + a done-flag totouch, and how to use the bus. - DISPATCH —
orch send <name> <i> --file .../agent-<i>.task.mdfor each booted worker. - COORDINATE via the bus — tell workers to post findings to
shared/bus.md(lines prefixed[Wn]) and to read it. When one discovers something (a bug class, a shared fix needed), the others act on it. The bus is the fleet's shared memory. - MONITOR (your core job) — periodically
orch readeach pane + readbus.md. Catch wrong-roads early and correct them with a nudge. Watch for: off-task drift, dead-ends, forbidden actions, or stalls. Re-check on a cadence (~80–600s) so you stay free between passes; a tighter cadence = closer watch. - COLLECT — each worker
touches a done-flag (e.g.shared/agent-<i>.done) + writesagent-<i>.result.md. Poll the flags (background loop ororch status) so you know when all are done. - VERIFY + TEAR DOWN — read the results, verify them adversarially (don't trust blindly — have a DIFFERENT worker try to refute each finding), then
orch kill <name>. Report a consolidated sign-off BEFORE killing sessions.
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 · 60 lines · 0 tokens per session scan B 4ef5b54aeeb4
orch is a skill published in the GitHub repository daman8271/the-perfect-orchestrator (1 stars, last pushed 4mo ago), licensed MIT. It adds 133 tokens to every session and 1,644 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). It is 95% identical to orch, differing in 2 lines, and is treated as a copy.
orch compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| orchdaman8271/the-perfect-orchestrator | Skill | 1 | 4mo ago | MIT | B | 133 | Claude Code, Codex |
| subagent-driven-developmentNousResearch/hermes-agent | Skill | 263k | today | MIT | A | 17 | Claude Code, Codex |
| mcporterNousResearch/hermes-agent | Skill | 263k | today | MIT | A | 16 | Claude Code, Codex |
| research-engineerdavila7/claude-code-templates | Skill | 34k | today | MIT | A | 43 | Claude Code, Codex |
| article-writingaffaan-m/ECC | Skill | 303k | 5d ago | MIT | A | 57 | Claude Code, Codex |
| safe-refactorJuliusBrussee/caveman | Skill | 120k | today | Apache-2.0 | A | 29 | Claude Code, Codex |
| artifact-template-minimal-letterheadasgeirtj/system_prompts_leaks | Skill | 71k | today | CC0-1.0 | A | 54 | Claude Code, Codex |