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 agentmods add skills/jl-cmd/claude-dev-env/orchestratornpx skills add jl-cmd/claude-dev-env --skill orchestratorgit clone --depth 1 https://github.com/jl-cmd/claude-dev-envWrote 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/jl-cmd/claude-dev-env/orchestrator)<a href="https://agentmods.dev/skills/jl-cmd/claude-dev-env/orchestrator"><img src="https://agentmods.dev/badge/skills/jl-cmd/claude-dev-env/orchestrator.svg" alt="Measured on agentmods" 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 | $0.00081 | $0.04567 |
| Opus 5 | $0.00041 | $0.02284 |
| Sonnet 5 | $0.00016 | $0.00913 |
| Haiku 4.5 | $0.00008 | $0.00457 |
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 today.
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 — 359 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator Strategy
Principle
A frontier model plans and synthesizes while cheap workers do the token-heavy reading and doing — Anthropic's coordinator pattern, source: https://github.com/anthropics/claude-cookbooks/blob/main/managed_agents/CMA_plan_big_execute_small.ipynb ("Coordinator pattern: big models for planning, small models for execution"). On the cookbook's own measured run, a coordinator delegating to Sonnet-5 workers came out cheaper and faster than a solo frontier agent held to the same verification rigor, with 84-98% of the team's input tokens billed at the worker rate.
Under this skill the session is the orchestrator. It spawns and resumes
executor subagents — clean-coder and the like — and those executors do
every bit of the execution: the code edits, the build runs, the test
runs. The orchestrating session drives the plan, keeps the run artifacts
and the ledger current, and answers executor consults. Hard questions
this session cannot settle go to the human.
The moment it edits a file or runs a test itself, the pairing breaks —
its own tool use stays orchestration, run-artifact writes, and light
verification reads.
status_gate (deterministic — not optional)
Prose does not keep the loop alive. Re-arm and terminate are gated by
scripts/status_gate.py (and, on Claude, the PreToolUse hook
orchestrator_refresh_reschedule_gate). The gate is host-agnostic: a
single pending re-arm latch in the status file, not host product names.
python scripts/status_gate.py set --status active|done [--run-slug SLUG] [--status-file PATH]
python scripts/status_gate.py begin-firing [--run-slug SLUG] [--status-file PATH]
python scripts/status_gate.py should-reschedule [--run-slug SLUG] [--status-file PATH]
python scripts/status_gate.py claim-rearm [--run-slug SLUG] [--status-file PATH]
python scripts/status_gate.py release-rearm [--run-slug SLUG] [--status-file PATH]
| Exit / output | Meaning |
|---|---|
set → 0 |
Status written (active/done); done clears latch; re-asserting active preserves it |
begin-firing → 0 |
Active; clears rearm_pending (start of a refresh firing) |
begin-firing → 1 |
Stop — missing/invalid/done (fail closed) |
should-reschedule → 0 |
Active and rearm_pending is false (read-only) |
should-reschedule → 1 |
Stop — inactive, missing, invalid, or slot already pending |
claim-rearm → 0 |
Slot latched (rearm_pending true) after a successful create |
claim-rearm → 1 |
Slot already pending or inactive — cancel any just-created schedule |
release-rearm → 0 |
Cleared pending (recovery if a latch stuck after create) |
release-rearm → 1 |
Stop — missing/invalid/done; nothing to release |
What ships with it
13 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.
- .claude/CLAUDE.md 14 B
- AGENTS.md 1 B
- reference/.claude/CLAUDE.md 14 B
- reference/AGENTS.md 1 B
- reference/consult-the-orchestrator.md 2.4 KB
- reference/executor-consult-block.md 2.7 KB
- reference/host-detect.md 489 B
- scripts/status_gate_constants/__init__.py 60 B runs code
- scripts/status_gate_constants/config/__init__.py 48 B runs code
- scripts/status_gate_constants/config/constants.py 1.4 KB runs code
- scripts/status_gate.py 20 KB runs code
- scripts/test_status_gate.py 15 KB runs code
- test_orchestrator_skill_contract.py 2.1 KB runs code
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.
- today Changed · -9 lines · +3 tokens per session 50eedbfa4f33
- 4d ago First seen · 368 lines · 78 tokens per session scan A 8ec0b2f65f71
orchestrator is a skill published in the GitHub repository jl-cmd/claude-dev-env (5 stars, last pushed today), licensed MIT. It adds 81 tokens to every session and 4,567 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…