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-complete-milestonegit 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-complete-milestone)<a href="https://agentmods.dev/commands/thierryn/fire-flow/fire-complete-milestone"><img src="https://agentmods.dev/badge/commands/thierryn/fire-flow/fire-complete-milestone.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.00013 | $0.01770 |
| Opus 5 | $0.00006 | $0.00885 |
| Sonnet 5 | $0.00003 | $0.00354 |
| Haiku 4.5 | $0.00001 | $0.00177 |
Grade A, and why
fire-complete-milestone 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 4d 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 — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fire-complete-milestone
Archive milestone, create historical record, and prepare for next cycle with WARRIOR validation
Purpose
Mark milestone complete, archive to milestones/, and update VISION.md and REQUIREMENTS.md. Creates a historical record of what shipped and prepares the project for the next milestone.
Creates:
.planning/milestones/v{version}-VISION.md- Archived roadmap.planning/milestones/v{version}-REQUIREMENTS.md- Archived requirements- Git tag
v{version}
Arguments
arguments:
version:
required: true
type: string
description: "Version number to complete (e.g., '1.0', '1.1', '2.0')"
example: "/fire-complete-milestone 1.0"
Process
Step 0: Pre-flight Check - WARRIOR Validation
MANDATORY: Check for verification before archiving.
ls .planning/v{version}-VERIFICATION.md 2>/dev/null
If no verification file:
+------------------------------------------------------------------------------+
| WARNING: No Verification Found |
+------------------------------------------------------------------------------+
| |
| No verification record found for v{version}. |
| |
| Recommended: Run `/fire-4-verify` first to ensure: |
| - All must-haves are met |
| - 70-point validation passed |
| - No critical gaps |
| |
| Continue anyway? (verification will be noted as "skipped") |
| |
+------------------------------------------------------------------------------+
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.
- 4d ago First seen · 271 lines · 13 tokens per session scan A b38de8b47302
fire-complete-milestone is a command published in the GitHub repository ThierryN/fire-flow (77 stars, last pushed 22d ago), licensed MIT. It adds 13 tokens to every session and 1,770 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
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 阶段状态机）.