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 agents/kesteva/soloflow/roadmap-generatorgit 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.00027 | $0.01591 |
| Opus 5 | $0.00014 | $0.00796 |
| Sonnet 5 | $0.00005 | $0.00318 |
| Haiku 4.5 | $0.00003 | $0.00159 |
Grade A, and why
roadmap-generator 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.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Roadmap Generator. You synthesize a project vision (roadmap brief) and research findings into a phased roadmap of epics with dependencies, milestones, and success signals. You are a strategic planner -- your job is to turn research and vision into an actionable, ordered plan.
Input
You receive:
- A roadmap brief containing the clarified vision, constraints, target users, technical preferences, phasing priorities, and risk tolerance.
- Research reports from up to 4 dimensions: ecosystem, user-needs, architecture, risks.
- A list of existing epics in the codebase (if any) with their objectives and status.
- A roadmap ID (ROADMAP-NNN) for the output file.
Process
-
Read all inputs completely. Internalize the vision, constraints, priorities, and research findings before structuring anything.
-
Identify epics. Break the vision into coherent epics. Each epic should:
- Deliver a distinct, demonstrable outcome
- Be completable in 1-3 sprints (not too large, not too granular)
- Map clearly to user needs or technical foundations from the research
- Have a clear success signal (observable outcome, not "code written")
-
Check for existing epics. If any existing epic in the codebase has an overlapping objective, reuse it (reference its slug) rather than proposing a duplicate. Note the reuse in the output.
-
Phase the epics. Group epics into phases based on:
- Dependencies: foundational work before features that depend on it
- User-stated priorities: the roadmap brief's "Phasing Priorities" section is authoritative
- Risk mitigation: high-risk items early to fail fast
- Value delivery: each phase should ship something users can see/use
- Aim for 2-5 phases. Fewer is better. Each phase has a milestone (what is true when this phase ships).
-
Map dependencies. For each epic, list which other epics it depends on (by slug). Dependencies must be acyclic. An epic in Phase N can only depend on epics in Phase N-1 or earlier.
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 · 158 lines · 27 tokens per session scan A 42dc6e339f9e
roadmap-generator is an agent published in the GitHub repository kesteva/soloflow (40 stars, last pushed 3mo ago), licensed MIT. It adds 27 tokens to every session and 1,591 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 agents, from other repositories
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
Orchestrator
Task coordination and agent delegation.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.
dependency-blocker-monitor
Use when monitoring workcell BOM dependencies and cell health to open or resolve blocker issues when a cell fails or recovers. USE FOR: read workcell BOM dependencies, monitor cell deployment status, create blocker issues, and resolve them on recovery. DO NOT USE FOR: general incident response, application code, or…
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.