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/kesteva/soloflow/summarize-roadmapgit clone --depth 1 https://github.com/kesteva/soloflowWhat 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.00016 | $0.00826 |
| Opus 5 | $0.00008 | $0.00413 |
| Sonnet 5 | $0.00003 | $0.00165 |
| Haiku 4.5 | $0.00002 | $0.00083 |
Grade A, and why
summarize-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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/soloflow:summarize-roadmap
Print the current state of the backlog as a roadmap-style report: one line per active task, grouped by epic, with totals at the bottom. Read-only — no state mutations, no agent spawns.
Steps
-
Check initialization. If
.soloflow/does not exist, report: "SoloFlow not initialized. Run/soloflow:initfirst." and stop. -
Fetch all active tasks. Run:
node "${CLAUDE_PLUGIN_ROOT}/scripts/state/plan-query.js" --format jsonWith no filters, this returns every task under
.soloflow/active/plans/**/TASK-*-plan.mdas a JSON array. Each element carries the task's frontmatter (id,title,status,epic,depends_on,scope_summary,plan_path). -
Empty-state. If the result is
[], print and stop:## Roadmap Summary No active tasks. Use `/soloflow:idea-extractor` or `/soloflow:roadmap` to seed the backlog. -
Group by epic. Bucket tasks by their
epicfrontmatter field. Treatnull, missing, or empty-string as theOrphans (no epic)bucket. Sort non-orphan buckets alphabetically by slug; the orphans bucket goes last. Within each bucket, sort tasks byidascending. -
Resolve epic heading. For each non-orphan slug:
- Try
Readon.soloflow/active/plans/<slug>/EPIC-<slug>.md. - If not found, try
.soloflow/archive/done/<slug>/EPIC-<slug>.md. - If found, parse frontmatter and use
objectiveas the heading text andstatusas the parenthetical badge. - If neither is found or
objectiveis absent, fall back to the slug itself as the heading and omit the status badge.
- Try
-
Format the report. Per-task line:
- [<status>] TASK-NNN — <title>The task's
titlefield is the one-sentence summary. Use raw status values (ready,deferred,pending,in_progress,blocked,stuck,human_needed).Add an indented
↳ blocked by: TASK-A, TASK-Bline only when the task'sstatusisblockedANDdepends_onis a non-empty list.
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.
- 3d ago First seen · 68 lines · 16 tokens per session scan A da666c49b217
summarize-roadmap is a command published in the GitHub repository kesteva/soloflow (40 stars, last pushed 3mo ago), licensed MIT. It adds 16 tokens to every session and 826 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.