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.
npx agentmods add commands/evan043/claude-cli-advanced-starter-pack/roadmap-status.templategit 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/commands/evan043/claude-cli-advanced-starter-pack/roadmap-status.template)<a href="https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/roadmap-status.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/roadmap-status.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.01035 |
| Opus 5 | $0.00000 | $0.00517 |
| Sonnet 5 | $0.00000 | $0.00207 |
| Haiku 4.5 | $0.00000 | $0.00103 |
Grade A, and why
roadmap-status.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 6d 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 — 138 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: Roadmap progress dashboard model: haiku
Roadmap Status - Multi-Phase Progress Dashboard
You are a roadmap progress tracking specialist. Display comprehensive status for roadmaps and their phases.
Execution Protocol
Step 1: Discover Roadmaps
Scan for roadmap files:
.claude/docs/roadmaps/*/ROADMAP.json.claude/roadmaps/*.jsonROADMAP.jsonin project root
Step 2: Load and Parse
For each discovered roadmap:
- Load ROADMAP.json
- For each project/phase, load its PROGRESS.json
- Calculate completion percentages
- Identify blocked items
Step 3: Display Dashboard
╔═══════════════════════════════════════════════════════════════════════════╗
║ ROADMAP STATUS DASHBOARD ║
╠═══════════════════════════════════════════════════════════════════════════╣
║ ║
║ Active Roadmaps: {{count}} ║
║ ║
╠═══════════════════════════════════════════════════════════════════════════╣
{{#each roadmaps}}
║ ║
║ 📋 {{name}} ({{slug}}) ║
║ ────────────────────────────────────────────────────────────────────────── ║
║ ║
║ Progress: [{{progressBar}}] {{percentage}}% ║
║ Phases: {{completedPhases}}/{{totalPhases}} complete ║
║ Tasks: {{completedTasks}}/{{totalTasks}} complete ║
{{#if githubIssue}}
║ GitHub: #{{issueNumber}} ({{issueUrl}}) ║
{{/if}}
║ ║
║ Phase Status: ║
{{#each phases}}
║ {{statusEmoji}} Phase {{number}}: {{name}} ║
║ Status: {{status}} | Tasks: {{taskProgress}} ║
{{#if blocked}}
║ ⚠️ BLOCKED: {{blockedReason}} ║
{{/if}}
{{/each}}
║ ║
{{/each}}
╚═══════════════════════════════════════════════════════════════════════════╝
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.
- 6d ago First seen · 138 lines · 0 tokens per session scan A 00072b0271f4
roadmap-status.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 1,035 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-08-30.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
auto-browse
Auto-browse — learn, optimize, and graduate browser operations or web data-mining workflows.
release-harn
Run the tag-first Harn release workflow.
discover
Search the Everruns(Dev) API catalog for available operations.
fix-issue
!gh issue view $ARGUMENTS 2>/dev/null || echo "Could not fetch issue $ARGUMENTS".
qa
Smoke or browser-walk a running app. Report only. Do not implement. Do not merge.