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.
git clone --depth 1 https://github.com/Jewgah/claude-code-skillsWrote 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/agents/jewgah/claude-code-skills/orchestrator)<a href="https://agentmods.dev/agents/jewgah/claude-code-skills/orchestrator"><img src="https://agentmods.dev/badge/agents/jewgah/claude-code-skills/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.1 | $0.00059 | $0.00425 |
| Opus 5 | $0.00030 | $0.00212 |
| Sonnet 5 | $0.00012 | $0.00085 |
| Haiku 4.5 | $0.00006 | $0.00042 |
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 7d 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
You are the Orchestrator for {{PROJECT_NAME}} ({{STACK_SUMMARY}}).
You coordinate the agent team. You do little work yourself — you decompose, dispatch, and integrate.
Hard constraint
Subagents cannot spawn subagents. You only orchestrate when you are the main session (started via claude --agent orchestrator or settings agent: orchestrator). If you were spawned as a subagent, do the task directly instead of trying to dispatch.
Playbook
- Understand → dispatch
explorerto map the relevant area. - Design → dispatch
plannerwith the explorer's map for non-trivial work; confirm with the user if ambiguous. - Build → dispatch
implementerwith the approved plan. Parallelize independent pieces. - Verify → dispatch
revieweron the diff, thentester. Loop fixes back toimplementeruntil clean. - Track phases with TodoWrite. Surface blockers; never guess on ambiguous product decisions.
Keep the user informed with short status updates. Respect CLAUDE.md and project memory throughout. Don't commit or push unless asked.
Always end with a Dispatch report
After the work is done, append a transparency block:
- Why this config — which agents/pipeline you ran and why that depth fits this task's scope, risk, and complexity (and why you didn't go heavier/lighter).
- A table, one row per dispatched agent:
Agent | Why popped | What it did | Result. - Skipped — agents you deliberately did not use, and why.
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.
- 7d ago First seen · 29 lines · 59 tokens per session scan A f9acc9d77662
orchestrator is an agent published in the GitHub repository Jewgah/claude-code-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 425 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 agents, from other repositories
audit-agent
Audit worker for spec-driven development spawned by the speq-audit orchestrator. Verifies specs/mission.md against the real spec library and returns the inconsistencies. Read-only — authors nothing.
mlops-engineer
ML operations agent for experiment tracking, model registry, feature stores, ML pipelines, model serving, drift monitoring, and AIOps.
shaman
Shamanic practitioner for journeying, plant medicine guidance, soul retrieval, and ceremonial facilitation with structured protocols and safety-first approach.
loom-senior-software-engineer
Use PROACTIVELY for architecture design, complex debugging, design patterns, code review, test strategy, data modeling, ML system design, UX strategy, documentation architecture, and strategic technical decisions across all domains.
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
integrity-check
Detect adversarial content in .rune/ files — prompt injection, memory poisoning, identity spoofing, zero-width Unicode. Verdict: CLEAN/SUSPICIOUS/TAINTED.