epic-orchestrator

epic-orchestrator is an agent for Claude Code from evan043/claude-cli-advanced-starter-pack. It costs 45 tokens per session (3,099 once invoked), scanned A, original, MIT.

A coordinator for large development efforts made up of several roadmaps. An epic is a large body of related work, and a roadmap divides it into major workstreams.

In plain words
What is it for?
It helps break down epics, create roadmap records, coordinate roadmap agents, enforce progress gates such as passing tests, and synchronize overall progress with GitHub issues.
Why use it?
It organizes complex work into smaller roadmaps, tracks their progress, and checks that each stage is ready before moving forward.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md).

Good fit It helps break down epics, create roadmap records, coordinate roadmap agents, enforce…

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/evan043/claude-cli-advanced-starter-pack/epic-orchestrator.template
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.

Clone the repo
git clone --depth 1 https://github.com/evan043/claude-cli-advanced-starter-pack

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 epic-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/agents/evan043/claude-cli-advanced-starter-pack/epic-orchestrator.template.svg)](https://agentmods.dev/agents/evan043/claude-cli-advanced-starter-pack/epic-orchestrator.template)
Your own site
<a href="https://agentmods.dev/agents/evan043/claude-cli-advanced-starter-pack/epic-orchestrator.template"><img src="https://agentmods.dev/badge/agents/evan043/claude-cli-advanced-starter-pack/epic-orchestrator.template.svg" alt="Measured on agentmods" height="20"></a>
Per session 45 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,099 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.00045 $0.03099
Opus 5 $0.00023 $0.01550
Sonnet 5 $0.00009 $0.00620
Haiku 4.5 $0.00005 $0.00310

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

Security

Grade A, and why

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

templates/agents/epic-orchestrator.template.md · 440 lines

How it starts

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

Epic Orchestrator (L0)

You are the L0 Epic Orchestrator responsible for managing large-scale epics composed of multiple roadmaps. Your role is the highest level of coordination in the CCASP agent hierarchy.

Hierarchy Overview

L0 Epic Orchestrator (YOU)
├── L1 Roadmap Orchestrator (spawns per roadmap)
    ├── L1 Phase Orchestrator (spawns per phase)
        ├── L2 Specialist Agents (domain-specific)
            └── L3 Worker Agents (atomic tasks)

Core Responsibilities

  1. Analyze epic scope and determine optimal roadmap breakdown
  2. Create EPIC.json with roadmap placeholders
  3. Spawn Roadmap Orchestrators sequentially for each roadmap
  4. Gate progress - ensure tests pass before advancing
  5. Sync to GitHub - update epic issue with aggregate progress
  6. Report completion with aggregate metrics

Epic Structure

EPIC.json Schema

Location: .claude/epics/{slug}/EPIC.json

{
  "epic_id": "epic-{uuid}",
  "slug": "feature-name",
  "title": "Feature Name",
  "description": "Epic description",
  "business_objective": "Why this epic exists",

  "roadmaps": [
    {
      "roadmap_id": "rm-{uuid}",
      "roadmap_index": 0,
      "title": "Roadmap 1: Foundation",
      "description": "Build core infrastructure",
      "status": "not_started",
      "completion_percentage": 0,
      "path": ".claude/epics/{slug}/roadmaps/roadmap-1.json",
      "phase_count": 0,
      "depends_on": []
    }
  ],

  "roadmap_count": 3,
  "current_roadmap_index": 0,
  "completion_percentage": 0,
  "status": "in_progress",

  "github_epic_number": 123,

  "gating": {
    "require_tests": true,
    "require_docs": false,
    "allow_manual_override": true
  },

  "testing_requirements": {
    "unit_tests": true,
    "integration_tests": false,
    "min_coverage": 0
  },

  "token_budget": {
    "total": 500000,
    "used": 0,
    "per_roadmap": 100000,
    "compaction_threshold": 0.8
  }
}

Orchestration Protocol

Phase 1: Initialization and Scope Analysis

Read the full file on GitHub · 440 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. 7d ago First seen · 440 lines · 45 tokens per session scan A cb06e1f4d06c

Subscribe to this mod's changes

epic-orchestrator is an agent published in the GitHub repository evan043/claude-cli-advanced-starter-pack (61 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 3,099 once invoked, about $0.0002 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

rca-debugger

Root-cause analyzer for complex multi-system failures — the third stage of the debugging escalation chain (build-error-resolver → systematic-debugger → rca-debugger → escalation-fixer). Escalation from systematic-debugger when the bisect is inconclusive, there is a CI-vs-local discrepancy, the bug is flaky, or the…

sangrokjung/claude-forge · 118 tokens

cavecrew-reviewer

Diff/branch/file reviewer. One line per finding, severity-tagged, no praise, no scope creep. Output format path:line: : . . Use for "review this PR", "review my diff", "audit this file". Skips formatting nits unless they change meaning.

stevesolun/ctx · 75 tokens

systematic-debugger

Specialist for bugs that reproduce but whose root cause is unknown. Enforces a strict reproduce → bisect → hypothesize → verify protocol; never guesses a fix without a failing test first. Use proactively when a bug reproduces but the cause is unclear — "why does this happen", "works locally but not in CI"…

sangrokjung/claude-forge · 170 tokens

observability-engineer

OpenTelemetry, Prometheus, Grafana, distributed tracing, SLO design, and alerting specialist. Use when implementing observability, designing monitoring systems, or troubleshooting production issues. Trigger phrases: observability, monitoring, tracing, Prometheus, Grafana, OpenTelemetry, SLO, SLI, alerting, metrics…

travisjneuman/.claude · 82 tokens

go-expert

Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.

travisjneuman/.claude · 69 tokens

mobile-release-manager

App store submissions, mobile CI/CD, ASO, code signing, and beta distribution specialist. Use when preparing app releases, setting up mobile CI/CD, or managing app store presence. Trigger phrases: app store, Play Store, TestFlight, release, code signing, provisioning profile, Fastlane, ASO, beta, OTA update, version…

travisjneuman/.claude · 77 tokens