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-todosgit 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-todos)<a href="https://agentmods.dev/commands/thierryn/fire-flow/fire-todos"><img src="https://agentmods.dev/badge/commands/thierryn/fire-flow/fire-todos.svg" alt="Measured on agentmods" 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 | $0.00010 | $0.02038 |
| Opus 5 | $0.00005 | $0.01019 |
| Sonnet 5 | $0.00002 | $0.00408 |
| Haiku 4.5 | $0.00001 | $0.00204 |
Grade A, and why
fire-todos 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 yesterday.
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 — 336 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fire-todos
Capture ideas and tasks during sessions, list pending todos, and select work
Purpose
Quick task capture and review system for ideas, issues, and tasks that surface during Dominion Flow sessions. Enables "thought -> capture -> continue" flow without losing context or derailing current work.
Commands:
/fire-todos add [description]- Capture a new todo/fire-todos list [area]- List pending todos/fire-todos(no args) - List all pending todos
Arguments
arguments:
action:
required: false
type: string
enum: [add, list]
default: list
description: "Action to perform"
description:
required: false
type: string
description: "For 'add': description of the todo. For 'list': optional area filter"
examples:
- "/fire-todos" - List all pending todos
- "/fire-todos add Fix auth token refresh" - Add a new todo
- "/fire-todos list api" - List todos in 'api' area
Process: Add Todo
Step 1: Ensure Directory
mkdir -p .planning/todos/pending .planning/todos/done
Step 2: Check Existing Areas
ls .planning/todos/pending/*.md 2>/dev/null | xargs -I {} grep "^area:" {} 2>/dev/null | cut -d' ' -f2 | sort -u
Note existing areas for consistency.
Step 3: Extract Content
With arguments: Use as the title/focus.
/fire-todos add Fix auth token refresh-> title = "Fix auth token refresh"
Without arguments: Analyze recent conversation to extract:
- The specific problem, idea, or task discussed
- Relevant file paths mentioned
- Technical details (error messages, line numbers)
Formulate:
title: 3-10 word descriptive title (action verb preferred)problem: What's wrong or why this is neededsolution: Approach hints or "TBD" if just an ideafiles: Relevant paths from conversation
Step 4: Infer Area
| Path pattern | Area |
|---|---|
src/api/*, api/* |
api |
src/components/*, src/ui/* |
ui |
src/auth/*, auth/* |
auth |
src/db/*, database/* |
database |
tests/*, __tests__/* |
testing |
docs/* |
docs |
.planning/* |
planning |
scripts/*, bin/* |
tooling |
| No files or unclear | general |
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.
- yesterday First seen · 336 lines · 10 tokens per session scan A 2b8752642529
fire-todos is a command published in the GitHub repository ThierryN/fire-flow (77 stars, last pushed 23d ago), licensed MIT. It adds 10 tokens to every session and 2,038 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-09-03.
Other commands, from other repositories
aside
Answer a quick side question without interrupting or losing context from the current task. Resume work automatically after answering.
evolve
Analyze instincts and suggest or generate evolved structures.
plan
Create implementation plan with risk assessment.
inbox
Check and respond to inter-agent messages.
caveman-compress
Compress a markdown/text file into caveman format to save tokens.
inventory
Track wiki-adjacent things the user cares about: items, Ideas, ingest candidates, entities, corpora, open questions, tasks, and other durable inventory records.