fire-1b-research

fire-1b-research is a command for Claude Code from ThierryN/fire-flow. It costs 17 tokens per session (1,797 once invoked), scanned A, original, MIT.

A project-research command for Dominion Flow that studies technology options, chooses an architecture direction, and creates a development roadmap. It is the second step in a three-step project setup process.

In plain words
What is it for?
Use it after the project-initialisation step to research technologies, gather findings, select an architecture branch, lock the chosen vision, write a roadmap, and continue to the setup step.
Why use it?
It turns an initial project description and requirements into researched design choices and an ordered plan. It also checks that the required project and requirements files exist before starting.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: names the AskUserQuestion tool.

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-1b-research
Clone the repo
git clone --depth 1 https://github.com/ThierryN/fire-flow

Made for: Claude Code.

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-1b-research

README.md
[![agentmods](https://agentmods.dev/badge/commands/thierryn/fire-flow/fire-1b-research.svg)](https://agentmods.dev/commands/thierryn/fire-flow/fire-1b-research)
Your own site
<a href="https://agentmods.dev/commands/thierryn/fire-flow/fire-1b-research"><img src="https://agentmods.dev/badge/commands/thierryn/fire-flow/fire-1b-research.svg" alt="Measured on agentmods" height="20"></a>
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,797 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.1 $0.00017 $0.01797
Opus 5 $0.00009 $0.00898
Sonnet 5 $0.00003 $0.00359
Haiku 4.5 $0.00002 $0.00180

Measured 6d ago against content hash 31ee520e8419, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

fire-1b-research 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.

commands/fire-1b-research.md · 211 lines

How it starts

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

/fire-1b-research

Spawn researchers, select architecture vision, generate roadmap


Purpose

Research the technology landscape, select a coherent architecture, and generate the project roadmap. This is Step 2 of 3 in project initialization.

Flow: /fire-1a-new/fire-1b-research/fire-1c-setup

Prerequisite: .planning/PROJECT.md and .planning/REQUIREMENTS.md must exist (created by /fire-1a-new).


EXECUTION ORDER

STEP 1: Validate prerequisites     → PROJECT.md + REQUIREMENTS.md exist
STEP 2: Research Synthesis          → spawn researchers, search GitHub, write SYNTHESIS.md
STEP 3: Vision Branch Selection     → spawn fire-vision-architect, user picks branch, LOCK VISION.md
STEP 4: Roadmap Generation          → spawn fire-roadmapper, write ROADMAP.md
FINAL:  Chain to next command       → tell user to run /fire-1c-setup

Complete each step before starting the next. Each step produces a file — verify it exists before proceeding.


Step 1: Validate Prerequisites

test -f .planning/PROJECT.md && test -f .planning/REQUIREMENTS.md && echo "READY" || echo "MISSING — run /fire-1a-new first"

If files are missing, stop and tell the user to run /fire-1a-new first.

Read .planning/PROJECT.md to determine mode (forward/backward) for Step 3.


Step 2: Research Synthesis (MANDATORY)

Spawn 4 parallel researchers (or sequential if resources are limited):

Researcher Focus Output
STACK Technology ecosystem, versions, compatibility research/STACK.md
FEATURES Feature implementation patterns, complexity research/FEATURES.md
ARCHITECTURE Folder structure, data flow, API design research/ARCHITECTURE.md
PITFALLS Common mistakes, known issues, anti-patterns research/PITFALLS.md

Every researcher MUST search GitHub for open source reference projects:

Search for 2-3 real open source projects similar to what the user is building:

  • Repo name, stars, last updated
  • Tech stack used
  • Folder structure patterns
  • Key patterns worth adopting
  • Mistakes visible in their issues/PRs

Read the full file on GitHub · 211 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. 6d ago First seen · 211 lines · 17 tokens per session scan A 31ee520e8419

Subscribe to this mod's changes

fire-1b-research is a command published in the GitHub repository ThierryN/fire-flow (77 stars, last pushed 23d ago), licensed MIT. It adds 17 tokens to every session and 1,797 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.