Borrowing it
Nothing to install: this file belongs to cognitx-leyton/codegraph. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/cognitx-leyton/codegraph/main/.claude/commands/roadmap.mdgit clone --depth 1 https://github.com/cognitx-leyton/codegraphWrote 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/cognitx-leyton/codegraph/roadmap)<a href="https://agentmods.dev/commands/cognitx-leyton/codegraph/roadmap"><img src="https://agentmods.dev/badge/commands/cognitx-leyton/codegraph/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/cognitx-leyton/codegraph/roadmap"><img src="https://agentmods.dev/badge/commands/cognitx-leyton/codegraph/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.00010 | $0.00391 |
| Opus 5.5 | $0.00004 | $0.00156 |
| Sonnet 5.5 | $0.00002 | $0.00078 |
| Haiku 4.5 | $0.00001 | $0.00039 |
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 2mo 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
Update Roadmap (Step 8)
Update ROADMAP.md at the repo root to reflect what was just implemented.
Process
1. Gather context
git log --oneline $(git describe --tags --abbrev=0 2>/dev/null || echo HEAD~10)..HEAD
git diff --stat $(git describe --tags --abbrev=0 2>/dev/null || echo HEAD~10)..HEAD
Read the current ROADMAP.md.
2. Update these sections
"TL;DR — where we are"
- Update branch state, test count, graph stats, package version
"Shipped since the last roadmap update"
- Add new commit list with descriptions
- Group by theme (like existing entries)
"Repository state"
- Update table: branch, unpushed commits, test count, last install
"What's next (ranked)"
- Move completed items out of "What's next"
- Re-rank remaining items if priorities shifted
- Add any new items discovered during implementation
"Known open questions"
- Remove resolved questions
- Add new questions surfaced during work
3. Update the header
> **Last updated:** {today's date} after commits `{first}` → `{last}` ({summary}).
4. Do NOT update these sections
- "Session workflow conventions" — only update if a convention changed
- "Non-goals" — only update if something moved in/out of scope
- "Appendix" — auto-derived from code, update only if file structure changed
Validate
Read the updated ROADMAP.md back and verify it's coherent — a fresh agent should be able to pick up work from it.
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.
- 2mo ago First seen · 56 lines · 10 tokens per session scan A 62dc50d2a4d6
roadmap is a command published in the GitHub repository cognitx-leyton/codegraph (12 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 10 tokens to every session and 391 once invoked, about $0.0000 per session on Opus 5.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
feedback
A design-stage security review for product requirement documents and other planning documents; a PRD is a document describing what a product should do.
va
A read-only security review of a codebase across eight architecture areas, with findings checked against file-and-line evidence.
compliance
A follow-up security check that verifies whether earlier findings were fixed and, depending on the selected mode, looks for new problems.
pentest
A read-only penetration-testing command for examining source code from an attacker’s perspective and producing proof-of-concept checks. Penetration testing is authorized security testing that tries to verify exploitable weaknesses.
run
A security-workflow coordinator that turns a natural-language request into a plan involving code review, verification, attack testing, or reporting.
verify
An independent recheck of a security assessment report that derives conclusions from its own evidence instead of accepting the original findings.