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/thierryn/fire-flow/fire-map-codebasegit 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.00011 | $0.01999 |
| Opus 5 | $0.00005 | $0.01000 |
| Sonnet 5 | $0.00002 | $0.00400 |
| Haiku 4.5 | $0.00001 | $0.00200 |
Grade A, and why
fire-map-codebase 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 — 314 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fire-map-codebase
Analyze existing codebase using parallel agents to produce structured codebase documents
Purpose
Analyze existing codebase using parallel fire-codebase-mapper agents to produce structured codebase documents. Each mapper agent explores a focus area and writes documents directly to .planning/codebase/. The orchestrator only receives confirmations, keeping context usage minimal.
Output: .planning/codebase/ folder with 7 structured documents about the codebase state.
Arguments
arguments:
focus_area:
required: false
type: string
description: "Optional area to focus mapping on (e.g., 'api', 'auth', 'database')"
example: "/fire-map-codebase auth"
When to Use
Use /fire-map-codebase for:
- Brownfield projects before initialization (understand existing code first)
- Refreshing codebase map after significant changes
- Onboarding to an unfamiliar codebase
- Before major refactoring (understand current state)
- When CONSCIENCE.md references outdated codebase info
- Before
/fire-0-orientwhen joining existing project
Skip /fire-map-codebase for:
- Greenfield projects with no code yet (nothing to map)
- Trivial codebases (<5 files)
Process
Step 1: Check Existing Map
ls .planning/codebase/*.md 2>/dev/null | wc -l
If codebase documents exist:
Use AskUserQuestion:
- header: "Existing Map"
- question: "Codebase map already exists. What would you like to do?"
- options:
- "Refresh all (Recommended)" - Re-analyze entire codebase
- "Refresh specific area" - Only update one focus area
- "Skip" - Keep existing map
Step 2: Create Directory Structure
mkdir -p .planning/codebase
Step 3: Display Spawning Banner
+------------------------------------------------------------------------------+
| FIRE MAP CODEBASE |
+------------------------------------------------------------------------------+
| |
| Spawning 4 parallel mapper agents... |
| |
| -> Agent 1: Tech focus (STACK.md, INTEGRATIONS.md) |
| -> Agent 2: Architecture focus (ARCHITECTURE.md, STRUCTURE.md) |
| -> Agent 3: Quality focus (CONVENTIONS.md, TESTING.md) |
| -> Agent 4: Concerns focus (CONCERNS.md) |
| |
| Focus area: {focus_area or "entire codebase"} |
| |
+------------------------------------------------------------------------------+
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 · 314 lines · 11 tokens per session scan A 90bd4eb2e959
fire-map-codebase is a command published in the GitHub repository ThierryN/fire-flow (77 stars, last pushed 19d ago), licensed MIT. It adds 11 tokens to every session and 1,999 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
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.