agentmods.dev

orchestrate

orchestrate is a skill for Claude Code from tianhanz/ears. It costs 71 tokens per session (3,237 once invoked), scanned A, original, MIT.

A coordination tool for managing several Claude Code sessions working as separate workers on related tasks.

In plain words
What is it for?
Use it to split work into parallel tasks, assign tasks to worker sessions, read their status, and combine their results.
Why use it?
It helps one main session keep track of parallel work, decisions, progress, and failures across multiple worktrees, which are separate working copies of the same project.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions Claude Code.

not rated 6repo 6mo ago A scan 71 tokens original MIT

Good fit Use it to split work into parallel tasks, assign tasks to worker sessions, read their status, and combine their results.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tianhanz/ears/orchestrate
View source ↗ tianhanz/ears
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 tianhanz/ears --skill orchestrate
Clone the repo
git clone --depth 1 https://github.com/tianhanz/ears

Made for: Claude Code.

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.

agentmods badge for orchestrate

README.md
[![agentmods](https://agentmods.dev/badge/skills/tianhanz/ears/orchestrate/github.svg)](https://agentmods.dev/skills/tianhanz/ears/orchestrate)
Your own site
<a href="https://agentmods.dev/skills/tianhanz/ears/orchestrate"><img src="https://agentmods.dev/badge/skills/tianhanz/ears/orchestrate/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.

agentmods 80×15 button for orchestrate

Your own site · 80×15
<a href="https://agentmods.dev/skills/tianhanz/ears/orchestrate"><img src="https://agentmods.dev/badge/skills/tianhanz/ears/orchestrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,237 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00071 $0.03237
Opus 5.5 $0.00028 $0.01295
Sonnet 5.5 $0.00014 $0.00647
Haiku 4.5 $0.00007 $0.00324

Measured 2mo ago against content hash 6cc6b3ace5b8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

orchestrate 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 2mo 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/orchestrate/SKILL.md · 353 lines

How it starts

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

Orchestrate Skill

Coordinate multiple Claude Code sessions as an orchestrator. The orchestrator maintains strategic context and decision-making authority while spawning worker sessions to execute specific tasks in parallel.

Arguments: $ARGUMENTS

Concepts

  • Orchestrator: The main session (you) that maintains the big picture, makes decisions, and coordinates workers. Thinks like tianhanz — strategic, decisive, delegates execution but owns the judgment calls.

  • Worker: A spawned Claude Code session that executes a specific task. Workers write their progress and decisions to .claude/state/session-<id>.yaml. When done, they mark status=completed with structured results.

  • Session State: Structured YAML files in .claude/state/ that enable cross-session coordination. Each session writes its own state; the orchestrator reads all states. All writes are protected by file locking (fcntl) — safe for concurrent access.

  • Failure Taxonomy: Workers report outcomes using a 5-category system: success (task completed), blocked (waiting on external input/decision), env_failure (tooling/infra issue), timeout (exceeded time limit), inconclusive (unclear if done, needs human review).

Subcommands

/orchestrate plan

Plan the work breakdown and identify parallelizable tasks.

  1. Ask: "What's the overall goal? What are the major workstreams?"
  2. Identify tasks that can run in parallel (independent) vs sequential (dependent)
  3. For each parallelizable task, draft a worker prompt
  4. Output a dependency graph:
# Work plan with dependencies
tasks:
  - id: task-1
    description: "Review OTM radiation"
    dependencies: []        # Can start immediately
    estimated_complexity: low
    worker_type: review      # review | implement | test | research

  - id: task-2
    description: "Review SNB radiation"
    dependencies: []         # Can run in parallel with task-1
    estimated_complexity: medium
    worker_type: review

  - id: task-3
    description: "Fix issues found in review"
    dependencies: [task-1, task-2]  # Blocked until reviews complete
    estimated_complexity: high
    worker_type: implement

Read the full file on GitHub · 353 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.

  1. 2mo ago First seen · 353 lines · 71 tokens per session scan A 6cc6b3ace5b8

Subscribe to this mod's changes

orchestrate is a skill published in the GitHub repository tianhanz/ears (6 stars, last pushed 6mo ago), licensed MIT. It adds 71 tokens to every session and 3,237 once invoked, about $0.0003 per session on Opus 5.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 agentsMulti-Agentcoordinationparallel-executionsession-management
Related

orchestrate compared with skills from other repositories

orchestrate next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
orchestratetianhanz/earsSkill66mo agoMITA71Claude Code
agent-teamsathola/claude-night-marketSkill348todayMITA30Claude Code
orchestratevarun29ankuS/shodh-memorySkill3225d agoApache-2.0A67Claude Code
coding-agents-farmgriddynamics/rosettaSkill373todayApache-2.0B32Claude Code
building-multiagent-systems2389-research/building-multiagent-systemsSkill85d agoMITA0Claude Code
hive-mind-advancedruvnet/agentic-flowSkill838todaynoneA25Claude Code
sema-usageemergent-wisdom/semaSkill1427d agoMITA68Claude Code