orchestrator

orchestrator is an agent for Claude Code from andyzengmath/quantum-loop. It costs 64 tokens per session (13,896 once invoked), scanned A, original, MIT.

An execution manager for the quantum-loop development workflow. It reads the project plan, runs implementation stories in dependency order, and sends completed work through review before committing it.

In plain words
What is it for?
Use it to execute a planned software project, coordinate sequential or parallel coding agents, run review checks, and commit stories that pass.
Why use it?
It removes the need to manually track which tasks are ready, retry failed work, manage parallel branches, and decide which changes have passed review.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents; mentions Claude Code.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is breaches=$(bash lib/surface-budget.sh gate "$BASE_SHA" "$HEAD_SHA" "$BUDGET").

Part of the quantum-loop plugin — 10 skills, 9 agents shipped together

Good fit Use it to execute a planned software project, coordinate sequential or parallel coding agents, run review checks, and commit stories that pass.

Compare 6 agents from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/andyzengmath/quantum-loop
agentmods
npx agentmods add agents/andyzengmath/quantum-loop/orchestrator

Made for: Claude Code.

Or install quantum-loop, the plugin that ships this one along with the rest of its 10 skills, 9 agents.

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/andyzengmath/quantum-loop/orchestrator/github.svg)](https://agentmods.dev/agents/andyzengmath/quantum-loop/orchestrator)
Your own site
<a href="https://agentmods.dev/agents/andyzengmath/quantum-loop/orchestrator"><img src="https://agentmods.dev/badge/agents/andyzengmath/quantum-loop/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/andyzengmath/quantum-loop/orchestrator"><img src="https://agentmods.dev/badge/agents/andyzengmath/quantum-loop/orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 64 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 13,896 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.00064 $0.13896
Opus 5.5 $0.00026 $0.05558
Sonnet 5.5 $0.00013 $0.02779
Haiku 4.5 $0.00006 $0.01390

Measured 1mo ago against content hash 8d5c34e4c033, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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.

agents/orchestrator.md · 1,027 lines

How it starts

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

Quantum-Loop: Orchestrator Agent

You manage the full execution lifecycle for quantum-loop. You read quantum.json, query the dependency DAG, implement stories (sequential) or dispatch implementer subagents (parallel), run review gates, handle retries, and commit passing stories.

Step 1: Initialize

  1. Read quantum.json in the current directory
  2. Read codebasePatterns array for project conventions from previous iterations
  3. Read the PRD at the path in prdPath for requirement context
  4. Check progress array for recent learnings
  5. Clean up stale quantum.json.tmp if present
  6. Verify you are on the correct branch (branchName):
    git branch --show-current
    # If wrong branch: git checkout <branchName> 2>/dev/null || git checkout -b <branchName> main
    
  7. Count stories by status and report summary to user

Step 1.0.4 / 1.0.5 / 1.1: Liveness wrapping, routing snapshot, PRD hash-check

See agents/orchestrator-modules/init-and-routing.md for the full procedure (parent-side poll_orchestrator_commits wrapping, per-role routing snapshot via resolve_routing + read_routing_snapshot + write_routing_snapshot, PRD hash-check via verify_prd_sha, and the init-guard/resilience/reground/tracecoder/dead-code/intent-graph/skeleton/trajectory/hyclone module sourcing block with *_AVAILABLE flags).

Step 1B: Detect Stale Stories

After initialization and before querying the DAG, check for stories stuck in in_progress:

  1. Read staleThresholdMinutes from quantum.json (default: 20). This can be overridden by the CLI flag --stale-timeout.
  2. For each story where status === "in_progress" and startedAt is set:
    • Calculate elapsed = now - startedAt (in minutes)
    • If elapsed > staleThresholdMinutes:
      • Set status = "failed"
      • Clear startedAt = null
      • Increment retries.attempts
      • Add failure log entry: {"phase": "stale_detection", "timestamp": "<ISO 8601>", "error": "Story was in_progress for <elapsed> minutes (threshold: <threshold>)"}
      • If retries.attempts >= retries.maxAttempts: set status = "blocked"
      • Log: [STALE] US-XXX - reset to failed after <elapsed> minutes
  3. Stories without startedAt that are in_progress are suspicious but not provably stale — log a warning but do not reset them.

Read the full file on GitHub · 1,027 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. 1mo ago First seen · 1,027 lines · 64 tokens per session scan A 8d5c34e4c033

Subscribe to this mod's changes

orchestrator is an agent published in the GitHub repository andyzengmath/quantum-loop (24 stars, last pushed 3mo ago), licensed MIT. It adds 64 tokens to every session and 13,896 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-30.

Related

Other agents, from other repositories

conductor

Conducts workflow runs: writes a Workflow-shaped script for a phase of work, starts it with wfstart, waits with wfwait, reads the result and decides the next step. Reads the tree and uses git and gh through the shell; leaves implementation, review and research to the workers its scripts dispatch. Session profile…

developer239/michals-opencode-cookbook · 88 tokens

producer

The Producer manages all production concerns: sprint planning, milestone tracking, risk management, scope negotiation, and cross-department coordination. This is the primary coordination agent. Use this agent when work needs to be planned, tracked, prioritized, or when multiple departments need to synchronize.

IdoCohen560/claude-unity-game-studio · 56 tokens

planner

Drafts the execution Plan (plan.md) AND emits task records for a SpecManager feature, grounded in the approved Architecture and the existing codebase. Plans MUST be organised into phases with Fibonacci-scored tasks ≤3.

joanseg/specmanager · 46 tokens

plan-creation-eng-lead

Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.

QBall-Inc/the-bulwark · 48 tokens

evolve-dependency-map

Dependency mapping and critical path analysis agent for the Evolve Loop (Evaluate archetype). Analyzes project dependencies, identifies the critical path, and highlights blocking items.

mickeyyaya/evolve-loop · 39 tokens

pm-advisor

You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".

VandanaAjayDubey111/great-pm · 123 tokens