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/jezweb/claude-skills/roadmapgit clone --depth 1 https://github.com/jezweb/claude-skillsWrote 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/jezweb/claude-skills/roadmap)<a href="https://agentmods.dev/commands/jezweb/claude-skills/roadmap"><img src="https://agentmods.dev/badge/commands/jezweb/claude-skills/roadmap.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.00015 | $0.00173 |
| Opus 5 | $0.00008 | $0.00086 |
| Sonnet 5 | $0.00003 | $0.00035 |
| Haiku 4.5 | $0.00002 | $0.00017 |
Grade A, and why
roadmap 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.
What it actually says
Load the roadmap skill.
Parse $ARGUMENTS for mode:
plan [topic]— generate a ROADMAP.md from a brief or deep-research outputstart— begin executing from phase 1, don't stop until done or stuckresume— pick up from where the last session left off, keep goingstatus— show which phases are complete and what's next
Default: plan if no roadmap exists, resume if one does.
Examples: /roadmap plan markdown note app on cloudflare, /roadmap start, /roadmap resume, /roadmap status
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 · 17 lines · 15 tokens per session scan A a4ff0d4cd1fe
roadmap is a command published in the GitHub repository jezweb/claude-skills (996 stars, last pushed 2mo ago), licensed MIT. It adds 15 tokens to every session and 173 once invoked, about $0.0001 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 commands, from other repositories
genshijin-compress
Markdown・テキストファイルを原始人形式へ安全圧縮.
review
Submit a story for verification (In Progress → In Review, no PR yet).
wp-cleanup
Find and clean up unused PHP code, Composer dependencies, imports, and dead code in WordPress projects.
audit
Adversarial, exhaustive review of the entire repository across code, tests, documentation, and configuration, with optional fixing in the same run. Assumes the code is incorrect until proven otherwise. This is the default command when the invocation names no other.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.