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/littlebearapps/pitchdocs/roadmapgit clone --depth 1 https://github.com/littlebearapps/pitchdocsWhat 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 | $0.00017 | $0.00418 |
| Opus 5 | $0.00009 | $0.00209 |
| Sonnet 5 | $0.00003 | $0.00084 |
| Haiku 4.5 | $0.00002 | $0.00042 |
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 2d 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
Generate or update ROADMAP.md from GitHub milestones, issues, and project boards.
Behaviour
- Load the
roadmapskill for structure and format - Load the
doc-standardsrule for tone - If GitHub MCP tools are unavailable (GitLab/Bitbucket), gather data via
glabCLI, REST API, or git history. Loadplatform-profilesfor CLI equivalents. - Gather data from the hosting platform:
- Milestones and their issues
- Issues labelled
enhancementorfeature - Recent releases/tags for completed milestones
- Structure into current, upcoming, and completed milestones
- Add mission statement (from README or package description)
- Add "How to get involved" section
- Write ROADMAP.md
Arguments
- No arguments: generates full roadmap
- Milestone name: focuses on a specific milestone
full: regenerates from scratch (discards existing content)
Data Sources (Priority Order)
- GitHub Milestones (primary — best structured)
- Issues with milestone assignments
- Issues labelled
enhancement/feature(if no milestones) - Git tags for completed versions
- README/package.json for mission statement
Output
Writes directly to ROADMAP.md. Links issues, uses emoji status indicators, includes comparison links between versions.
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.
- 2d ago First seen · 53 lines · 17 tokens per session scan A cf356a076000
roadmap is a command published in the GitHub repository littlebearapps/pitchdocs (7 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 418 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-31.
Other commands, from other repositories
create-skill
Create an AI skill from any source (URL, repo, PDF, video, notebook, etc.).
install-skill
One-command skill creation and packaging for a target platform.
sync-config
Sync a scraping config's URLs against the live documentation site.
review-renovate
Review and merge renovate PRs with automerge configuration updates.
monitor-ci
Monitors pull request CI checks until they are resolved (pass or fail).
/add-claude-rule
Appends the rule from $ARGUMENTS to CLAUDE.md.