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-transitiongit 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-transition)<a href="https://agentmods.dev/commands/thierryn/fire-flow/fire-transition"><img src="https://agentmods.dev/badge/commands/thierryn/fire-flow/fire-transition.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.00019 | $0.01278 |
| Opus 5 | $0.00010 | $0.00639 |
| Sonnet 5 | $0.00004 | $0.00256 |
| Haiku 4.5 | $0.00002 | $0.00128 |
Grade A, and why
fire-transition 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 today.
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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fire-transition
Phase completion ceremony: metrics, bottleneck report, skill extraction, trend update, and next phase routing.
Arguments
arguments:
phase:
required: false
type: string
description: "Phase to transition from. Defaults to current phase."
Process
Step 1: Validate Phase Completion
+---------------------------------------------------------------+
| DOMINION FLOW >>> PHASE TRANSITION |
+---------------------------------------------------------------+
Check:
- All plans in phase have RECORD.md files
- UAT verification passed (or user override)
- No open P0 blockers in BLOCKERS.md
- No open P1 blockers without acknowledgment
If validation fails: present issues, offer fix or override.
Step 2: Collect Phase Metrics
Aggregate from all RECORD.md files in the phase:
Phase Metrics:
plans_completed: [N]
total_duration: [N]m
avg_plan_duration: [N]m
total_tasks: [N]
tasks_blocked: [N]
files_created: [N]
files_modified: [N]
lines_added: [N]
lines_removed: [N]
tests_added: [N]
skills_applied: [N]
honesty_checkpoints: [N]
total_commits: [N]
blocker_count: [N]
blocker_resolution_rate: [N]%
Step 3: Bottleneck Detection
Run bottleneck detection algorithm (see references/metrics-and-trends.md):
| Rule | Condition | Flag |
|---|---|---|
| Slow Plan | Duration > 2x phase average | BOTTLENECK:SLOW |
| Blocked Plan | >20% tasks blocked | BOTTLENECK:BLOCKED |
| Failed Verification | >1 verification cycle | BOTTLENECK:QUALITY |
| Fan-Out Blocker | Blocks 2+ downstream plans | BOTTLENECK:CRITICAL_PATH |
| Complexity Spike | Lines > 3x average | BOTTLENECK:COMPLEXITY |
+---------------------------------------------------------------+
| BOTTLENECK REPORT |
+---------------------------------------------------------------+
| |
| Flagged Plans: |
| | Plan | Flag | Duration | Suggestion | |
| |------|------|----------|------------| |
| | 03-05 | SLOW | 18m (avg: 12m) | Break into smaller plans | |
| |
| Phase Health: Speed 7/10, Quality 9/10, Efficiency 8/10 |
| Overall: 8/10 |
+-----------------------------------------------------------------+
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.
- today First seen · 187 lines · 19 tokens per session scan A 9843ee515f09
fire-transition is a command published in the GitHub repository ThierryN/fire-flow (77 stars, last pushed 22d ago), licensed MIT. It adds 19 tokens to every session and 1,278 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
awesome-chatgpt
Search awesome-ChatGPT-repositories for open-source GitHub repositories related to ChatGPT and LLMs.
init
Scaffold a new MindBase project (v2 layout). Usage: /mb:init [template] [-- mission ...].
commit
智能生成 Git 提交信息并提交.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
doctor.es
Diagnostica problemas de inferencia LLM en Mac: asiai doctor verifica el estado de los motores, conflictos de puertos, carga de modelos y estado de la GPU.
requirement-review
需求文档多角色评审（requirement-review）：需求文档 → 7-Agent 并行评审 → 重构高质量需求文档（Runtime 受控流程，0-7 阶段状态机）.