What is agent-orchestration?

A skill for coordinating multiple coding agents in iTerm2, including registering agents, creating teams, assigning tasks, and tracking workflow events.

Registering agents, creating teams, delegating tasks, executing plans, sending notifications, and checking agent status or locks.

It organizes shared work between agents so tasks, teams, messages, and status can be managed centrally.

agent-orchestration — Skill for Claude Code and Codex by research-deve

Install

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.

Any agent

npx skills add research-developer/iterm-mcp-claude-agency --skill agent-orchestration

Clone the repo

git clone --depth 1 https://github.com/research-developer/iterm-mcp-claude-agency

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/research-developer/iterm-mcp-claude-agency/agent-orchestration/github.svg)](https://agentmods.dev/skills/research-developer/iterm-mcp-claude-agency/agent-orchestration)

Your own site

<a href="https://agentmods.dev/skills/research-developer/iterm-mcp-claude-agency/agent-orchestration"><img src="https://agentmods.dev/badge/skills/research-developer/iterm-mcp-claude-agency/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/research-developer/iterm-mcp-claude-agency/agent-orchestration"><img src="https://agentmods.dev/badge/skills/research-developer/iterm-mcp-claude-agency/agent-orchestration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 964 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00056	$0.00964
Opus 5	$0.00028	$0.00482
Sonnet 5	$0.00011	$0.00193
Haiku 4.5	$0.00006	$0.00096

Measured 12d ago against content hash 8153d31e73f3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

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 12d 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.

skills/agent-orchestration/SKILL.md · 81 lines

How it starts

The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.

iTerm Agent Orchestration

The SP2 surface exposes a handful of method-semantic tools. Each takes an op parameter that accepts either an HTTP method (GET/POST/DELETE) or a friendly verb alias (list/create/remove/send/invoke). For a live schema on any tool, call it with op="OPTIONS".

Agents (`agents`)

agents(op="list") — list agents (optionally filter by team)
agents(op="GET", target="status") — compact status summary for all agents
agents(op="create", agent_name="alice", session_id="sid", teams=["backend"]) — register
agents(op="delete", agent_name="alice") — remove
agents(op="GET", target="notifications", agent="alice", limit=20) — read notifications
agents(op="send", target="notifications", agent="alice", level="info", summary="build done") — notify an agent
agents(op="GET", target="locks", agent="alice") — list locks held by an agent
agents(op="GET", target="hooks", hooks_op="get_stats") — hooks state / stats
agents(op="update", target="hooks", hooks_op="update_config", enabled=true) — tune hooks

Teams (`teams`)

teams(op="list") — list teams with member counts
teams(op="create", team_name="backend", description="Backend squad") — create
teams(op="create", target="agents", team_name="backend", agent_name="alice") — assign
teams(op="delete", target="agents", team_name="backend", agent_name="alice") — remove member
teams(op="delete", team_name="backend") — delete team

Managers (`managers`)

managers(op="list") — list managers
managers(op="GET", manager_name="m1") — get manager info
managers(op="create", manager_name="m1", workers=["w1","w2"], delegation_strategy="round_robin") — create manager
managers(op="create", target="workers", manager_name="m1", worker_name="w3", worker_role="builder") — add worker
managers(op="delete", target="workers", manager_name="m1", worker_name="w3") — remove worker
managers(op="delete", manager_name="m1") — remove manager

Delegation (`delegate`)

Read the full file on GitHub · 81 lines

Changes

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.

12d ago First seen · 81 lines · 56 tokens per session scan A 8153d31e73f3

Subscribe to this mod's changes

agent-orchestration is a skill published in the GitHub repository research-developer/iterm-mcp-claude-agency (4 stars, last pushed 2mo ago), licensed MIT. It adds 56 tokens to every session and 964 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.

Building agents

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens