What is roadmap-status?

A read-only status command that gathers the recorded state of one roadmap across all its repository workstreams. A roadmap is a planned set of related work, and a workstream is one repository's part of it.

Use it to see which work needs attention, is running, recently finished, or stopped, and why.

It brings status that is scattered across files and agent sessions into one view without changing shared project data.

How bredmond1019/claude-sdk-rs configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to bredmond1019/claude-sdk-rs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/bredmond1019/claude-sdk-rs/main/.claude/commands/roadmap-status.md

Clone the repo

git clone --depth 1 https://github.com/bredmond1019/claude-sdk-rs

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/bredmond1019/claude-sdk-rs/roadmap-status/github.svg)](https://agentmods.dev/commands/bredmond1019/claude-sdk-rs/roadmap-status)

Your own site

<a href="https://agentmods.dev/commands/bredmond1019/claude-sdk-rs/roadmap-status"><img src="https://agentmods.dev/badge/commands/bredmond1019/claude-sdk-rs/roadmap-status/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/bredmond1019/claude-sdk-rs/roadmap-status"><img src="https://agentmods.dev/badge/commands/bredmond1019/claude-sdk-rs/roadmap-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 37 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,514 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00037	$0.01514
Opus 5.5	$0.00015	$0.00606
Sonnet 5.5	$0.00007	$0.00303
Haiku 4.5	$0.00004	$0.00151

Measured 11d ago against content hash cafbf6908cc5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

roadmap-status 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 11d 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.

.claude/commands/roadmap-status.md · 122 lines

How it starts

The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Roadmap Status — one mid-run view of a roadmap's lanes

A roadmap runs as several concurrent lanes, one per repo, each in its own agent session. Asking "where is this roadmap" today means reading every one of those sessions. The information is already on disk, scattered across four artifact families that nothing joins. This command joins them, for one roadmap, and reports.

This command derives nothing. Ranking, dedup and staleness scoring belong to mev (rank_carryover, cluster_by_finding_id, effective-priority propagation); this command projects what is already on disk, exactly as /consolidate-run does for post-run findings — per the fleet discipline "mev owns the derivation; bastion projects it" (core/bastion/src/serve/handlers/attention.rs:140-141). It implements no ranking, dedup, or staleness logic of its own.

This command writes nothing — anywhere. No state.json, no record file, no lock, no cache. Several lanes may be running concurrently against the same roadmap while this runs; a status tool that mutates shared state during a concurrent run is the contention pattern this fleet has repeatedly been bitten by (CLAUDE.md standing rule 10).

Not these

Not /attention — that triages stale items fleet-wide against brain.toml thresholds. This command is scoped to one roadmap's live lanes, not staleness triage.
Not /next — that recommends what to work on next. This command reports what already happened and is happening; it makes no recommendation.
Not /consolidate-run — that correlates findings across finished lane runs into proposed carryover[] entries after the fact. This command is a live, mid-run read; it proposes nothing and writes nothing.

Variables

$ARGUMENTS:

Usage: /roadmap-status --roadmap <slug>

Flag	Required	What it does
`--roadmap <slug>`	no	The roadmap to report on. Omit to list candidate roadmaps instead.

--roadmap omitted → list the candidate roadmaps (from scripts/roadmap_status_discovery.py with no --roadmap) with their last activity, and stop. Never guess which roadmap was meant — a status read against the wrong roadmap is worse than no read.

Read the full file on GitHub · 122 lines

Changes

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.

11d ago First seen · 122 lines · 37 tokens per session scan A cafbf6908cc5

Subscribe to this mod's changes

roadmap-status is a command published in the GitHub repository bredmond1019/claude-sdk-rs (23 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 37 tokens to every session and 1,514 once invoked, about $0.0001 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-10-26.

Project management

roadmap-status next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
roadmap-statusbredmond1019/claude-sdk-rs	Command	23	1mo ago	Apache-2.0	A	37	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

claude-sdk-rs: Command for Claude Code