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-double-checkgit 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-double-check)<a href="https://agentmods.dev/commands/thierryn/fire-flow/fire-double-check"><img src="https://agentmods.dev/badge/commands/thierryn/fire-flow/fire-double-check.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.00007 | $0.02861 |
| Opus 5 | $0.00003 | $0.01430 |
| Sonnet 5 | $0.00001 | $0.00572 |
| Haiku 4.5 | $0.00001 | $0.00286 |
Grade A, and why
fire-double-check 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 -X POST http://localhost:3000/api/auth/login \ How it starts
The opening of the file, as written. The whole thing — 461 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fire-double-check
Verify before you claim victory
Purpose
A rigorous validation command inspired by superpowers:verification-before-completion. Prevents false completion claims by requiring evidence-based verification. Integrates with WARRIOR honesty protocols to ensure claims match reality.
Arguments
arguments:
target:
required: false
type: string
description: "What to verify - defaults to current work"
examples:
- "/fire-double-check" # Verify current work
- "/fire-double-check 'login feature'"
- "/fire-double-check phase 2"
- "/fire-double-check PR#45"
optional_flags:
--deep: "Run extended verification including edge cases"
--fast: "Quick sanity check only (not recommended)"
--focus: "Specific area: tests, security, types, build"
--fix: "Attempt to fix issues found (default: report only)"
Core Principle
EVIDENCE BEFORE ASSERTION
┌─────────────────────────────────────────────────────────────────┐
│ │
│ ✗ WRONG: "The tests pass" → then run tests │
│ ✓ RIGHT: Run tests → "The tests pass (output: 45/45)" │
│ │
│ ✗ WRONG: "I fixed the bug" → hope it works │
│ ✓ RIGHT: Reproduce → fix → verify fix → "Bug fixed (proof)" │
│ │
└─────────────────────────────────────────────────────────────────┘
Process
Step 1: Identify Claims
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
DOMINION FLOW ► DOUBLE CHECK
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Target: {target or "Current Work"}
Mode: Evidence-Based Verification
Analyze what's being claimed:
## Claims to Verify
Based on context, the following claims need verification:
| # | Implicit Claim | Evidence Required |
|---|----------------|-------------------|
| 1 | Code compiles | Build output |
| 2 | Tests pass | Test runner output |
| 3 | Feature works | Demo or test |
| 4 | No regressions | Full test suite |
| 5 | Types are correct | TypeScript output |
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 · 461 lines · 7 tokens per session scan A 9ec3be05c141
fire-double-check is a command published in the GitHub repository ThierryN/fire-flow (77 stars, last pushed 22d ago), licensed MIT. It adds 7 tokens to every session and 2,861 once invoked, about $0.0000 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 阶段状态机）.