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-new-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-new-milestone)<a href="https://agentmods.dev/commands/thierryn/fire-flow/fire-new-milestone"><img src="https://agentmods.dev/badge/commands/thierryn/fire-flow/fire-new-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.1 | $0.00014 | $0.02105 |
| Opus 5 | $0.00007 | $0.01052 |
| Sonnet 5 | $0.00003 | $0.00421 |
| Haiku 4.5 | $0.00001 | $0.00211 |
Grade A, and why
fire-new-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 6d 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 — 357 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fire-new-milestone
Start a new milestone through unified flow: questioning -> research -> requirements -> roadmap
Purpose
Start a new milestone for an existing project. This is the brownfield equivalent of /fire-1a-new. The project exists, PROJECT.md has history. This command gathers "what's next" and takes you through the full cycle.
Creates/Updates:
.planning/PROJECT.md- Updated with new milestone goals.planning/research/- Domain research (optional).planning/REQUIREMENTS.md- Scoped requirements.planning/VISION.md- Phase structure.planning/CONSCIENCE.md- Updated project memory
After this command: Run /fire-2-plan [N] to start execution.
Arguments
arguments:
milestone_name:
required: false
type: string
description: "Optional milestone name (e.g., 'v1.1 Notifications')"
example: "/fire-new-milestone v1.1 Notifications"
Process
Phase 1: Validate Project
MANDATORY FGTAT STEP - Execute these checks before ANY user interaction:
[ -f .planning/PROJECT.md ] || { echo "ERROR: No PROJECT.md. Run /fire-1a-new first."; exit 1; }
Check for active milestone (VISION.md exists):
[ -f .planning/VISION.md ] && echo "ACTIVE_MILESTONE" || echo "READY_FOR_NEW"
If ACTIVE_MILESTONE:
Use AskUserQuestion:
- header: "Active Milestone"
- question: "A milestone is in progress. What would you like to do?"
- options:
- "Complete current first (Recommended)" - Run /fire-complete-milestone
- "Continue anyway" - Start new milestone (will archive current)
Phase 2: Present Context
Display banner:
+------------------------------------------------------------------------------+
| DOMINION FLOW > NEW MILESTONE |
+------------------------------------------------------------------------------+
Present what shipped:
Last milestone: v[X.Y] [Name] (shipped [DATE])
Key accomplishments:
- [From MILESTONES.md]
- [From MILESTONES.md]
Validated requirements:
- [From PROJECT.md Validated section]
Pending todos:
- [From CONSCIENCE.md if any]
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.
- 6d ago First seen · 357 lines · 14 tokens per session scan A 2c8326fbd1ef
fire-new-milestone is a command published in the GitHub repository ThierryN/fire-flow (77 stars, last pushed 24d ago), licensed MIT. It adds 14 tokens to every session and 2,105 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.
test
Generate comprehensive tests.
commit
智能生成 Git 提交信息并提交.
init
Scaffold a new MindBase project (v2 layout). Usage: /mb:init [template] [-- mission ...].
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.