fire-assumptions

fire-assumptions is a command for coding agents from ThierryN/fire-flow. It costs 11 tokens per session (483 once invoked), scanned A, original, MIT.

A command that lists and checks the assumptions being made about a project phase before work begins.

In plain words
What is it for?
Use it before planning or executing a phase, such as building a dashboard, to review technical and project assumptions.
Why use it?
It exposes unverified guesses early, reducing the risk of planning or building on incorrect information.

Command

Part of the dominion-flow plugin — 5 skills, 51 commands, 15 agents shipped together

Install

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.

agentmods
npx agentmods add commands/thierryn/fire-flow/fire-assumptions
Clone the repo
git clone --depth 1 https://github.com/ThierryN/fire-flow

Or install dominion-flow, the plugin that ships this one along with the rest of its 5 skills, 51 commands, 15 agents.

Wrote 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.

agentmods badge for fire-assumptions

README.md
[![agentmods](https://agentmods.dev/badge/commands/thierryn/fire-flow/fire-assumptions.svg)](https://agentmods.dev/commands/thierryn/fire-flow/fire-assumptions)
Your own site
<a href="https://agentmods.dev/commands/thierryn/fire-flow/fire-assumptions"><img src="https://agentmods.dev/badge/commands/thierryn/fire-flow/fire-assumptions.svg" alt="Measured on agentmods" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 483 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00011 $0.00483
Opus 5 $0.00005 $0.00242
Sonnet 5 $0.00002 $0.00097
Haiku 4.5 $0.00001 $0.00048

Measured 4d ago against content hash 45dc00595f7b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

fire-assumptions 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.

commands/fire-assumptions.md · 79 lines

How it starts

The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/fire-assumptions

Surface Claude's assumptions about a phase approach before planning. Prevents silent improvisation.


Arguments

arguments:
  phase:
    required: false
    type: string
    description: "Phase to list assumptions for. Defaults to current phase."

Process

Step 1: Load Context

Read CONSCIENCE.md, VISION.md, and phase description.

Step 2: Generate Assumptions

For the target phase, list all assumptions Claude is making:

+---------------------------------------------------------------+
|           DOMINION FLOW >>> ASSUMPTION VALIDATION                 |
+---------------------------------------------------------------+
|                                                                 |
|  Phase: 03 - Dashboard                                         |
|                                                                 |
|  Assumptions I'm making:                                       |
|                                                                 |
|  TECHNICAL:                                                    |
|  1. [VALIDATED] React 18+ is available (confirmed in pkg.json)|
|  2. [UNVALIDATED] WebSocket support in deployment target       |
|  3. [UNVALIDATED] Chart library compatible with SSR            |
|                                                                 |
|  INFRASTRUCTURE:                                               |
|  4. [VALIDATED] PostgreSQL is the database                     |
|  5. [UNVALIDATED] Redis available for real-time features       |
|                                                                 |
|  INTEGRATION:                                                  |
|  6. [UNVALIDATED] Stripe API supports batch operations         |
|                                                                 |
+-----------------------------------------------------------------+

Step 3: Validate or Acknowledge

For each UNVALIDATED assumption:

  • Can it be validated now? (check docs, test, research)
  • If yes: validate and update status
  • If no: acknowledge risk and document in ASSUMPTIONS.md

Read the full file on GitHub · 79 lines

Changes

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.

  1. 4d ago First seen · 79 lines · 11 tokens per session scan A 45dc00595f7b

Subscribe to this mod's changes

fire-assumptions is a command published in the GitHub repository ThierryN/fire-flow (77 stars, last pushed 22d ago), licensed MIT. It adds 11 tokens to every session and 483 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.