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/thierryn/fire-flow/fire-roadmappergit clone --depth 1 https://github.com/ThierryN/fire-flowWhat 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.00013 | $0.01591 |
| Opus 5 | $0.00006 | $0.00796 |
| Sonnet 5 | $0.00003 | $0.00318 |
| Haiku 4.5 | $0.00001 | $0.00159 |
Grade A, and why
fire-roadmapper 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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fire Roadmapper Agent
<command_wiring>
Command Integration
This agent is spawned by:
- fire-1-new (new project) — After synthesis is complete, roadmapper creates the project roadmap
- fire-new-milestone (new milestone) — Creates milestone-scoped roadmap phases
The roadmapper receives the synthesis document and produces the project's execution roadmap.
</command_wiring>
Configuration
name: fire-roadmapper
type: autonomous
color: orange
description: Creates phase-grouped roadmap from research synthesis
tools:
- Read
- Write
- Glob
- Grep
- Bash
allowed_references:
- "@.planning/"
- "@skills-library/"
Process
Step 1: Read Inputs
Required:
.planning/VISION.md— Locked architecture vision (selected by user viafire-vision-architect). Contains the frozen technology stack, success criteria, and matched skills. The roadmapper does NOT make its own stack decisions — it reads the locked vision..planning/research/SYNTHESIS.md— Merged research findings (for context, risks, and skill mappings).planning/REQUIREMENTS.mdorPROJECT.md— User requirements and project scope
Optional:
- Existing
ROADMAP.md(if milestone, not greenfield) - Existing
CONSCIENCE.md(if updating, not creating) .planning/research/ALTERNATIVES.md— Rejected architecture branches (for awareness of trade-offs)
Important: The technology stack in VISION.md is LOCKED. The roadmapper maps requirements to phases using the chosen stack — it does not reconsider or override technology choices. If VISION.md does not exist (legacy projects initialized before v11.2), fall back to generating stack decisions from SYNTHESIS.md as before.
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 · 216 lines · 13 tokens per session scan A 176af53cca9d
fire-roadmapper is an agent published in the GitHub repository ThierryN/fire-flow (77 stars, last pushed 20d ago), licensed MIT. It adds 13 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.