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-4-verifygit 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-4-verify)<a href="https://agentmods.dev/commands/thierryn/fire-flow/fire-4-verify"><img src="https://agentmods.dev/badge/commands/thierryn/fire-flow/fire-4-verify.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.00012 | $0.11116 |
| Opus 5 | $0.00006 | $0.05558 |
| Sonnet 5 | $0.00002 | $0.02223 |
| Haiku 4.5 | $0.00001 | $0.01112 |
Grade A, and why
fire-4-verify scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "http://localhost:3000/api/products?limit=5" | jq '.data | length' How it starts
The opening of the file, as written. The whole thing — 976 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fire-4-verify
Verify phase N with combined must-haves and WARRIOR 70-point validation
Purpose
Perform comprehensive verification of a completed phase by combining Dominion Flow's goal-backward must-haves verification with 70-point quality validation checklist. Generates a detailed verification report and routes to gap closure if needed.
Arguments
arguments:
phase_number:
required: true
type: integer
description: "Phase number to verify (e.g., 1, 2, 3)"
example: "/fire-4-verify 3"
optional_flags:
--detailed: "Include verbose output for all checks"
--quick: "Run only critical checks (must-haves + security)"
--report-only: "Generate report without routing to gap closure"
Process
Step 1: Load Verification Context
â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”
DOMINION FLOW > PHASE {N} VERIFICATION
â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”â”
Load Context:
@.planning/CONSCIENCE.md
@.planning/phases/{N}-{name}/*.BLUEPRINT.md # All plans
@.planning/phases/{N}-{name}/*-RECORD.md # All summaries
Extract:
- All must_haves from plan frontmatter
- All warrior_validation items from plans
- Skills applied during execution
- Key files created/modified
Step 2: Spawn fire-verifier
â—† Spawning fire-verifier for Phase {N}...
Verifier Context:
<verification_scope>
Phase: {N} - {name}
Plans to Verify: {list}
Total Must-Haves: {count}
WARRIOR Checks: 70 items across 8 categories
</verification_scope>
<must_haves>
{Aggregated must_haves from all plans}
</must_haves>
<warrior_checklist>
@references/validation-checklist.md
</warrior_checklist>
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 · 976 lines · 12 tokens per session scan A 827719ccff52
fire-4-verify is a command published in the GitHub repository ThierryN/fire-flow (77 stars, last pushed 22d ago), licensed MIT. It adds 12 tokens to every session and 11,116 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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 阶段状态机）.