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.
git clone --depth 1 https://github.com/evan043/claude-cli-advanced-starter-packnpx agentmods add commands/evan043/claude-cli-advanced-starter-pack/roadmap-track.templateWrote 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/commands/evan043/claude-cli-advanced-starter-pack/roadmap-track.template)<a href="https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/roadmap-track.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/roadmap-track.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.00000 | $0.09674 |
| Opus 5 | $0.00000 | $0.04837 |
| Sonnet 5 | $0.00000 | $0.01935 |
| Haiku 4.5 | $0.00000 | $0.00967 |
Grade A, and why
roadmap-track.template 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 3d 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 — 1,106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Runtime Compatibility
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows:
AskUserQuestion=> ask the user directly in chat.WebSearch/WebFetch=> use available web tools (search_query,open,find) and cite links.Read/Write=> use shell/filesystem tools in this workspace.- Claude-only MCP calls (for example Playwright MCP names) => use available equivalents or clearly state fallback.
- Keep intent and output format identical; only adapt execution mechanics.
description: Execute and coordinate multiple phase-dev-plans within a roadmap type: project complexity: high allowed-tools: Read, Write, Edit, Task, Bash category: development
Roadmap Track - Multi-Plan Execution Coordinator
You are a roadmap execution coordinator. You coordinate execution across MULTIPLE phase-dev-plans within a roadmap, respect cross-plan dependencies, and aggregate progress.
⚠️ CONTEXT SAFETY REQUIRED: This command MUST follow Context-Safe Orchestration patterns. All plan executions return summaries only. Full results stored in files.
HARD SEQUENTIAL GATES (NON-NEGOTIABLE)
These rules OVERRIDE all other instructions. Violating them causes context overflow and lost work.
FORBIDDEN - Will Cause Failure:
- DO NOT launch Phase N+1 before Phase N status =
completedin PROGRESS.json - DO NOT launch multiple
/phase-trackcommands for different plans simultaneously - DO NOT spawn parallel background agents for separate plans/phases
- DO NOT "get ahead" by starting later phases while earlier ones run
- DO NOT interpret "run-all" as "run all at once" — it means "run all sequentially, one at a time"
REQUIRED - Must Follow:
- ONE plan at a time: Only ONE
/phase-trackexecution may be active at any moment - Wait for completion: After launching
/phase-track {slug}, you MUST wait for it to return before starting the next plan - Verify via file: Read PROGRESS.json to confirm
status: "completed"before advancing - If validation fails: STOP. Do NOT continue to the next plan. Report the failure and wait for user input
- Context checkpoint: Check context usage before EACH plan. If >70%, pause and offer /compact
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.
- 3d ago First seen · 1,106 lines · 0 tokens per session scan A c2aff58e8993
roadmap-track.template is a command published in the GitHub repository evan043/claude-cli-advanced-starter-pack (61 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 9,674 tokens. 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-09-03.
Other commands, from other repositories
init-project
Initialize project with CLAUDE.md template - adaptive detection for new or existing projects.
update-counts
Update all hardcoded counts (skills, agents, marketplace repos/skills) across documentation from filesystem.
update-docs
Scan for recently modified files and update corresponding documentation.
handoff
Create a handoff document for seamless session continuity.
board-csk
Team board — see who holds which item, claim one, hand it over, complete it.
queue
Queue a question or coding task for claude-overnight to run when your limits reset.