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 zircote-plugins/claude-team-orchestration --skill orchestratinggit clone --depth 1 https://github.com/zircote-plugins/claude-team-orchestrationWrote 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/zircote-plugins/claude-team-orchestration/orchestrating)<a href="https://agentmods.dev/skills/zircote-plugins/claude-team-orchestration/orchestrating"><img src="https://agentmods.dev/badge/skills/zircote-plugins/claude-team-orchestration/orchestrating.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.00077 | $0.02522 |
| Opus 5 | $0.00039 | $0.01261 |
| Sonnet 5 | $0.00015 | $0.00504 |
| Haiku 4.5 | $0.00008 | $0.00252 |
Grade A, and why
orchestrating 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 8d 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Swarm Orchestration
Master multi-agent orchestration using Claude Code's agent teams and task system.
Experimental: Agent teams are disabled by default. Enable with
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMSin your settings.json or environment.
Primitives
| Primitive | What It Is | File Location |
|---|---|---|
| Agent | A Claude instance that can use tools. You are an agent. Subagents are agents you spawn. | N/A (process) |
| Team | A named group of agents working together. One leader, multiple teammates. | ~/.claude/teams/{name}/config.json |
| Teammate | An agent that joined a team. Has a name, color, inbox. Spawned via Task with team_name + name. |
Listed in team config |
| Leader | The agent that created the team. Receives teammate messages, approves plans/shutdowns. | First member in config |
| Task | A work item with subject, description, status, owner, and dependencies. | ~/.claude/tasks/{team}/N.json |
| Inbox | JSON file where an agent receives messages from teammates. | ~/.claude/teams/{name}/inboxes/{agent}.json |
| Message | A JSON object sent between agents. Can be text or structured (shutdown_request, idle_notification, etc). | Stored in inbox files |
| Backend | How teammates run. Auto-detected: in-process (same Node.js, invisible), tmux (separate panes, visible), iterm2 (split panes in iTerm2). See Spawn Backends. |
Auto-detected based on environment |
| Mode | Permission mode for spawned agents. Set mode: "plan" to require plan approval before the agent acts. See Plan Approval pattern. |
Task parameter |
| Isolation | Set isolation: "worktree" to give an agent an isolated git worktree copy. Cleaned up if no changes; returns worktree path/branch if changes are made. Recommended for agents making code changes. |
Task parameter |
What ships with it
2 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.
- 8d ago First seen · 224 lines · 77 tokens per session scan A 3679ff8f4ddf
orchestrating is a skill published in the GitHub repository zircote-plugins/claude-team-orchestration (14 stars, last pushed today), licensed MIT. It adds 77 tokens to every session and 2,522 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-30.
Other skills, from other repositories
content-extraction
Extracts and organizes content ideas from long-form content into detailed platform-specific tables. Use when repurposing transcripts, articles, blog posts, or any long-form content into multiple pieces across platforms.
title-generator
Generates compelling, click-worthy titles from content across multiple styles and platforms. Use when naming blog posts, videos, newsletters, social posts, or any content that needs a great headline.
linkedin-post
Generates engaging LinkedIn posts from long-form content. Use when creating LinkedIn content, building thought leadership, or repurposing content for professional audiences.
substack-note
Generates Substack Notes from long-form content. Use when creating short-form content for Substack's social feed, building newsletter audience, or sharing quick insights.
twitter-thread
Generates engaging Twitter/X threads from long-form content. Use when creating Twitter content, building audience, or breaking down complex topics into tweet-sized insights.
key-takeaways
Summarizes key takeaways from long-form content into structured bullet lists and actionable insights. Use when creating show notes, content summaries, SEO descriptions, or quick reference guides.