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 CassetteTapeCrackle/claude-starters --skill agent-orchestrationgit clone --depth 1 https://github.com/CassetteTapeCrackle/claude-startersWrote 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/cassettetapecrackle/claude-starters/agent-orchestration)<a href="https://agentmods.dev/skills/cassettetapecrackle/claude-starters/agent-orchestration"><img src="https://agentmods.dev/badge/skills/cassettetapecrackle/claude-starters/agent-orchestration/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/cassettetapecrackle/claude-starters/agent-orchestration"><img src="https://agentmods.dev/badge/skills/cassettetapecrackle/claude-starters/agent-orchestration.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.00059 | $0.00647 |
| Opus 5 | $0.00030 | $0.00324 |
| Sonnet 5 | $0.00012 | $0.00129 |
| Haiku 4.5 | $0.00006 | $0.00065 |
Grade A, and why
agent-orchestration 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 11d 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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent orchestration (the dispatcher policy)
You are the orchestrator. You choose between doing work yourself and delegating to a specialist agent. Optimize for fewer tokens and better output — most of the time that means doing it yourself or skipping.
Candidates come from two channels
- Reactive — the Stop hook surfaced a code-risk candidate (e.g.
unsafe-auditor,rt-safety-auditor,any-eliminator) because changed code matched a risk pattern. - Proactive — the phase of the current task maps to a specialist:
- ideate →
plugin-ideator/idea-brainstormer/competitor-analyst - spec/plan →
prd-writer/spec-critic - research an unknown →
deep-researcher - design UI →
ui-designer/ux-critic/plugin-ui-designer/design-system-author - debug →
debugger/regression-hunter - audit quality → the per-stack auditors +
starter-conformance-checker - ship →
technical-writer/release-copywriter/demo-script-writer/naming-agent
- ideate →
Only consider agents that actually exist for this project: the ones in .claude/agents/ (scoped) plus the global ones. Don't invent agents.
The decision — skip / inline / delegate
For each candidate, pick the cheapest option that gets the job done well:
- SKIP if the agent's concern isn't really implicated, or the change is trivial (docs, a rename, a one-line tweak). This is the most common answer. Don't dispatch to prove diligence.
- INLINE (do it yourself) if the surface is small and local (a few lines / one file) and you already have the context. Spinning a subagent would cost more than just doing it.
- DELEGATE only when it clearly pays: a broad scan (many files / a whole module), work that would pull a lot into your context (isolation is the payoff — the subagent's tokens stay out of your window), or a well-scoped specialist job whose prompt does better than you would ad hoc.
Rules
- Bias to skip/inline. When unsure and the surface is small, inline.
- One agent at a time; don't chain speculative delegations. Delegate, read the result, then decide the next step.
- Respect the project's own rules (its
CLAUDE.md) — e.g. don't let an agent touch DSP on a non-DSP task. - After you've handled a surfaced candidate, don't re-evaluate the same unchanged diff.
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.
- 11d ago First seen · 35 lines · 59 tokens per session scan A a0ab448ded31
agent-orchestration is a skill published in the GitHub repository CassetteTapeCrackle/claude-starters (1 stars, last pushed 22d ago), licensed MIT. It adds 59 tokens to every session and 647 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
open-problem
Use when the user points at a hard, unsolved, or open problem in any field — mathematics, physics, biology, ML, engineering — and wants a real attack on it. Runs a sustained multi-agent assault: establishes the state of play from primary sources, hunts for the two literatures nobody has combined, generates and kills…
grounding
Use before writing, reviewing, or debugging any code that uses a specific ML model (DINOv3, SAM 2, Whisper, Qwen3-Embedding, SigLIP 2…), whenever a model-provenance archive for it exists locally. Loads that archive's real source — checkpoint ids, API signatures, preprocessing constants, training recipe — so the code…
engineering-discipline
Behavioral guidelines to reduce common agent coding mistakes — thinking before coding, simplicity, surgical changes, goal-driven execution, and mandatory verification for data/BI work. Adapted from andrej-karpathy-skills (MIT), with a data/BI engineering layer added. Use this skill whenever writing, editing, or…
self-awareness
Behavioral calibration system that helps Claude catch its own failure patterns in real-time. Triggers on EVERY response to run self-checks for verbosity compensation, hallucination risk, missed frustration signals, sycophantic patterns, and constraint violations. Use this skill continuously—it modifies how Claude…
fable-method
Use when a task carries real uncertainty — multi-step builds, debugging where the first theory may be wrong, research or analysis with claims to verify, anything touching data/APIs/files not yet opened, or work that will be handed off. Also when work keeps failing or stalling, before declaring anything done, or when…
model-provenance
Use when the user names a specific ML model (e.g. DINOv3, SAM 2, Whisper, Qwen2-VL) and wants its real/official code, training recipe, or papers found, verified, or archived locally for grounded coding. Triggers include "find the real code for this model", "harvest DINOv3", "store the model's code and papers locally"…