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/cveralyon/axel-setupWrote 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/cveralyon/axel-setup/roadmap)<a href="https://agentmods.dev/commands/cveralyon/axel-setup/roadmap"><img src="https://agentmods.dev/badge/commands/cveralyon/axel-setup/roadmap/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/commands/cveralyon/axel-setup/roadmap"><img src="https://agentmods.dev/badge/commands/cveralyon/axel-setup/roadmap.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.00000 | $0.00187 |
| Opus 5.5 | $0.00000 | $0.00075 |
| Sonnet 5.5 | $0.00000 | $0.00037 |
| Haiku 4.5 | $0.00000 | $0.00019 |
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 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.
What it actually says
Roadmap: Feature & Improvement Suggestions
Analyze the codebase and generate a roadmap of potential features and improvements.
Analysis Steps
- Scan codebase architecture, patterns, and conventions
- Identify feature gaps and improvement opportunities
- Create phased overview (Quick Wins / Medium Effort / Strategic)
- Ask user which features to plan in detail
Analysis Focus
- Missing common patterns (auth, caching, error handling, logging)
- Performance optimization opportunities
- Developer experience improvements
- User-facing feature enhancements
- Code quality / refactoring candidates
Output Format
Quick Wins (low effort, high impact)
- Feature: description, estimated effort
Medium Effort
- Feature: description, what needs refactoring
Strategic (architectural changes)
- Feature: description, dependencies, risks
Present as a structured markdown table with columns: Feature | Effort | Impact | Dependencies.
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 · 32 lines · 0 tokens per session scan A 4fa8abc53fa5
roadmap is a command published in the GitHub repository cveralyon/axel-setup (4 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 187 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-31.
Other commands, from other repositories
plan
Research and produce intent.md, spec.md, and plan.md for a feature.
implement
Execute the plan.md with verification checkpoints.
template
Manage issue templates for streamlined issue creation.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
sync-linear
Sync current work with Linear ticket status.