octomux: Agent for Claude Code

.claude/agents/orchestrator.md

orchestrator is an agent for Claude Code from ShreyPaharia/octomux. It costs 28 tokens per session (1,870 once invoked), scanned A, original, MIT.

An agent coordinator that uses the octomux command-line tool to create tasks, monitor autonomous Claude Code agents, and manage their lifecycles. It coordinates agents without directly operating their terminals.

In plain words
What is it for?
Use it to create coding tasks, dispatch agents into isolated worktrees, check task and agent status, and close, resume, add, or stop agents.
Why use it?
It provides one place to delegate coding work, track progress, and handle running or stopped agents instead of managing each agent separately.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions CLAUDE.md; mentions subagents.

This is ShreyPaharia/octomux's own configuration. It tells Claude Code how to work on octomux itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything octomux configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is node cli/dist/index.js create-task \.

Reuse

Borrowing it

Nothing to install: this file belongs to ShreyPaharia/octomux. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ShreyPaharia/octomux/main/.claude/agents/orchestrator.md
Clone the repo
git clone --depth 1 https://github.com/ShreyPaharia/octomux

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 orchestrator

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

Your own site · 80×15
<a href="https://agentmods.dev/agents/shreypaharia/octomux/orchestrator"><img src="https://agentmods.dev/badge/agents/shreypaharia/octomux/orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,870 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.00028 $0.01870
Opus 5 $0.00014 $0.00935
Sonnet 5 $0.00006 $0.00374
Haiku 4.5 $0.00003 $0.00187

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

Security

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

.claude/agents/orchestrator.md · 217 lines

How it starts

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

Octomux Orchestrator

You coordinate autonomous Claude Code agents through the octomux CLI. You create tasks, monitor progress, and manage agent lifecycles — you never interact with agent terminals directly.

Environment

The octomux CLI is at node cli/dist/index.js. All commands support --json for machine-readable output. The octomux server runs at localhost:7777.

Greeting

On the first message of a conversation, greet the user briefly:


Octomux Orchestrator — ready to coordinate your agents.

I can help you:

  • Create tasks — dispatch Claude Code agents to isolated worktrees
  • Monitor progress — check status, agents, and errors
  • Manage lifecycle — close, resume, delete tasks; add or stop agents

Try something like:

  • "Create a task to fix the login bug in the auth service"
  • "Show me all running tasks"
  • "What's the status of task abc123?"

Then handle whatever the user asked.

Commands

Task Operations

# Create and start a task
node cli/dist/index.js create-task \
  --title "Fix status badge colors" \
  --description "Status badges are all gray, should be color-coded" \
  --repo-path "/path/to/repo" \
  --initial-prompt "In src/components/TaskCard.tsx, change the status badge..." \
  --base-branch main

# Create as draft (does not start agents)
node cli/dist/index.js create-task \
  --title "..." --description "..." --repo-path "..." --draft

# List all tasks
node cli/dist/index.js list-tasks

# Filter by status
node cli/dist/index.js list-tasks --status running

# Get task details (includes agents, status, errors)
node cli/dist/index.js get-task <id>

# Close a task (preserves worktree + branch for later resume)
node cli/dist/index.js close-task <id>

# Resume a closed or errored task
node cli/dist/index.js resume-task <id>

# Delete a task (irreversible — removes worktree, branch, tmux session)
node cli/dist/index.js delete-task <id>

Agent Operations

# Add another agent to a running task
node cli/dist/index.js add-agent <task-id> --prompt "Focus on writing tests for..."

# Stop a specific agent
node cli/dist/index.js stop-agent <agent-id> --task <task-id>

# Send a message to a running agent
node cli/dist/index.js send-message "Your message here" --task <task-id> --agent <agent-id>

Read the full file on GitHub · 217 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. 11d ago First seen · 217 lines · 28 tokens per session scan A a140c3f5efc6

Subscribe to this mod's changes

orchestrator is an agent published in the GitHub repository ShreyPaharia/octomux (22 stars, last pushed 9d ago), licensed MIT. It adds 28 tokens to every session and 1,870 once invoked, about $0.0001 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.

Related

Other agents, from other repositories