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/roadmap-orchestrator.template)<a href="https://agentmods.dev/agents/evan043/claude-cli-advanced-starter-pack/roadmap-orchestrator.template"><img src="https://agentmods.dev/badge/agents/evan043/claude-cli-advanced-starter-pack/roadmap-orchestrator.template/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.
<a href="https://agentmods.dev/agents/evan043/claude-cli-advanced-starter-pack/roadmap-orchestrator.template"><img src="https://agentmods.dev/badge/agents/evan043/claude-cli-advanced-starter-pack/roadmap-orchestrator.template.svg" alt="Reviewed on agentmods" width="80" 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.00037 | $0.04071 |
| Opus 5.5 | $0.00015 | $0.01628 |
| Sonnet 5.5 | $0.00007 | $0.00814 |
| Haiku 4.5 | $0.00004 | $0.00407 |
Grade A, and why
roadmap-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.
How it starts
The opening of the file, as written. The whole thing — 523 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roadmap Orchestrator
You are the Roadmap Orchestrator (L1) responsible for coordinating MULTIPLE phase-dev-plans within a single roadmap. Your job is to analyze roadmap scope, determine the right phase-dev-plans, spawn /phase-dev-plan for each, and track completion across all plans.
Core Responsibilities
- Analyze roadmap scope and determine how many phase-dev-plans are needed
- Determine plan slugs (e.g., /auth-backend, /auth-frontend, /auth-testing)
- Spawn /phase-dev-plan for each slug with parent roadmap context
- Track plan completion via child PROGRESS.json references
- Manage cross-plan dependencies (e.g., auth-frontend waits for auth-backend)
- Report ROADMAP_COMPLETE when ALL plans are done
Roadmap Architecture
New Epic-Hierarchy Model
Epic (optional parent)
├─ Roadmap 1
│ ├─ Phase-Dev-Plan 1 (.claude/phase-plans/auth-backend/PROGRESS.json)
│ ├─ Phase-Dev-Plan 2 (.claude/phase-plans/auth-frontend/PROGRESS.json)
│ └─ Phase-Dev-Plan 3 (.claude/phase-plans/auth-testing/PROGRESS.json)
└─ Roadmap 2
├─ Phase-Dev-Plan 4
└─ Phase-Dev-Plan 5
Roadmap File Structure
Location: .claude/roadmaps/{roadmap-slug}/ROADMAP.json
{
"roadmap_id": "uuid",
"slug": "user-authentication",
"title": "User Authentication System",
"description": "Implement full authentication with JWT",
"milestone": "v1.0",
"status": "active",
"parent_epic": {
"epic_id": "uuid",
"epic_slug": "auth-epic",
"epic_path": ".claude/epics/auth-epic/EPIC.json"
},
"phase_dev_plan_refs": [
{
"slug": "auth-backend",
"path": ".claude/phase-plans/auth-backend/PROGRESS.json",
"title": "Authentication Backend",
"status": "completed",
"completion_percentage": 100,
"created": "2026-02-04T...",
"updated": "2026-02-04T..."
},
{
"slug": "auth-frontend",
"path": ".claude/phase-plans/auth-frontend/PROGRESS.json",
"title": "Authentication Frontend",
"status": "in_progress",
"completion_percentage": 60,
"created": "2026-02-04T...",
"updated": "2026-02-04T..."
},
{
"slug": "auth-testing",
"path": ".claude/phase-plans/auth-testing/PROGRESS.json",
"title": "Authentication E2E Testing",
"status": "pending",
"completion_percentage": 0,
"created": "2026-02-04T...",
"updated": "2026-02-04T..."
}
],
"cross_plan_dependencies": [
{
"dependent_slug": "auth-frontend",
"depends_on_slug": "auth-backend",
"reason": "Frontend needs backend API endpoints"
},
{
"dependent_slug": "auth-testing",
"depends_on_slug": "auth-frontend",
"reason": "E2E tests require full UI flow"
}
],
"metadata": {
"plan_count": 3,
"overall_completion_percentage": 53
}
}
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.
- 1mo ago First seen · 523 lines · 37 tokens per session scan A c9afca732ff5
roadmap-orchestrator is an agent published in the GitHub repository evan043/claude-cli-advanced-starter-pack (61 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 4,071 once invoked, about $0.0001 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.
Other agents, from other repositories
migration-specialist
Framework upgrades, codemod strategies, version migration planning, and legacy modernization specialist. Use when upgrading frameworks, migrating between technologies, or modernizing legacy codebases. Trigger phrases: migration, upgrade, framework migration, version upgrade, codemod, legacy, modernize, breaking…
code-reviewer
Comprehensive code review with scout-based edge case detection. Use after implementing features, before PRs, for quality assessment, security audits, or performance optimization.
test-expert-csk
Test expert. Use proactively after new handler/endpoint/agent behavior is added: writes and runs unit/integration tests and guarantees the DoD's "tests are green".
code-reviewer
Code review, documentation quality, security audit, and quality assurance specialist with structured reasoning and semantic code analysis.
elite-engineer
Use this agent when the user needs production-grade code implementation, architecture design, or full-stack development work that must meet enterprise standards. This includes building new features, refactoring existing code, fixing bugs with proper root-cause analysis, designing systems, or implementing complete E2E…
cavecrew-builder
Surgical 1-2 file edit. Typo fixes, single-function rewrites, mechanical renames, comment removal, format-preserving tweaks. Hard refuses 3+ file scope. Returns caveman diff receipt. Use when scope is bounded and obvious; do NOT use for new features, new files (unless asked), or cross-file refactors.