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.
git clone --depth 1 https://github.com/evan043/claude-cli-advanced-starter-packWrote 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.
[](https://agentmods.dev/agents/evan043/claude-cli-advanced-starter-pack/epic-orchestrator.template)<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>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.00045 | $0.03099 |
| Opus 5 | $0.00023 | $0.01550 |
| Sonnet 5 | $0.00009 | $0.00620 |
| Haiku 4.5 | $0.00005 | $0.00310 |
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.
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
- Analyze epic scope and determine optimal roadmap breakdown
- Create EPIC.json with roadmap placeholders
- Spawn Roadmap Orchestrators sequentially for each roadmap
- Gate progress - ensure tests pass before advancing
- Sync to GitHub - update epic issue with aggregate progress
- 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
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.
- 7d ago First seen · 440 lines · 45 tokens per session scan A cb06e1f4d06c
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.
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…
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.
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"…
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…
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.
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…