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.
git clone --depth 1 https://github.com/ThierryN/fire-flowWrote 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.
[](https://agentmods.dev/commands/thierryn/fire-flow/fire-reflect)<a href="https://agentmods.dev/commands/thierryn/fire-flow/fire-reflect"><img src="https://agentmods.dev/badge/commands/thierryn/fire-flow/fire-reflect/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.
<a href="https://agentmods.dev/commands/thierryn/fire-flow/fire-reflect"><img src="https://agentmods.dev/badge/commands/thierryn/fire-flow/fire-reflect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00003 | $0.01585 |
| Opus 5.5 | $0.00001 | $0.00634 |
| Sonnet 5.5 | $0.00001 | $0.00317 |
| Haiku 4.5 | $0.00000 | $0.00159 |
Grade A, and why
fire-reflect 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 1mo 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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fire-reflect
Capture, search, and review failure reflections. Reflexion-style self-reflection for cross-session learning.
Purpose
After any failure (debug resolution, test failure, approach rotation, stalled loop), capture what was tried, why it failed, and what actually worked as a persistent reflection. Future sessions search these before investigating.
Arguments
arguments:
action:
required: false
type: string
description: "Action to perform: capture (default), search, list, review"
example: "/fire-reflect capture"
optional_flags:
--from debug: "Auto-extract from most recent resolved debug session"
--from session: "Extract from current session context"
--project <name>: "Tag with project name"
--severity <level>: "minor | moderate | critical (default: moderate)"
--search <query>: "Search reflections by keyword/symptom"
Process
Step 1: Determine Action
IF args contain "search" or --search:
→ Go to Search Mode (Step 5)
IF args contain "list":
→ Go to List Mode (Step 6)
IF args contain "review":
→ Go to Review Mode (Step 7)
ELSE:
→ Capture Mode (Step 2)
Step 2: Gather Reflection Content
If --from debug:
- Read most recent file in
.planning/debug/resolved/ - Extract: symptoms, eliminated hypotheses, root cause, fix applied
- Auto-fill reflection fields
If --from session:
- Review current conversation context
- Identify: failed approaches, what was tried, what worked
- Auto-fill reflection fields
If interactive (default): Ask using AskUserQuestion:
- What was the problem? — Brief symptom description
- What did you try that failed? — Each approach and why it didn't work
- What actually worked? — The solution that resolved it
- The lesson — One-sentence takeaway for future self
- Search triggers — When should future agents find this?
Step 3: Generate Reflection File
Create file at ~/.claude/reflections/{date}_{slug}.md:
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.
- 1mo ago First seen · 238 lines · 3 tokens per session scan A 21959c0494d0
fire-reflect is a command published in the GitHub repository ThierryN/fire-flow (78 stars, last pushed 2mo ago), licensed MIT. It adds 3 tokens to every session and 1,585 once invoked, about $0.0000 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-08-30.
Other commands, from other repositories
debug
View EverMem debug logs to troubleshoot memory saving and retrieval issues.
lint
Run health check on a project — orphans, contradictions, stale claims, gaps, suggested cross-links. Usage: /mb:lint [-p ] [project-id].
engram-solution
Crystallize a verified error→fix pair as praxis (CRS 1.0, never decays).
doctor
Diagnose lore — environment checks, effective config, memory/index state. Read-only.
learn
Extract patterns and learnings from current session.
rem_help
Each section is printed verbatim by --help for the command it names. The agreed design is issue #1656; change a page there and here together.