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-1c-setupgit clone --depth 1 https://github.com/ThierryN/fire-flowWhat 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.00016 | $0.02385 |
| Opus 5 | $0.00008 | $0.01192 |
| Sonnet 5 | $0.00003 | $0.00477 |
| Haiku 4.5 | $0.00002 | $0.00238 |
Grade A, and why
fire-1c-setup 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 3d 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 — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fire-1c-setup
Install CLI tools, create WARRIOR handoff, verify all files, show completion
Purpose
Finalize project initialization: install all CLI tools the locked stack requires, create the WARRIOR handoff, and verify every file exists. This is Step 3 of 3 in project initialization.
Flow: /fire-1a-new → /fire-1b-research → /fire-1c-setup
Prerequisite: .planning/VISION.md (locked) and .planning/ROADMAP.md must exist (created by /fire-1b-research).
EXECUTION ORDER
STEP 1: Validate prerequisites → VISION.md + ROADMAP.md exist
STEP 2: WARRIOR Handoff Init → create handoff file
STEP 3: Zero-Friction Tooling → install CLIs from VISION.md, write TOOLING-LOG.md
STEP 4: SKILLS-INDEX.md → create empty tracking file
STEP 4.5: Seed per-project skills/ → create skills/ folder + README.md + .gitkeep
STEP 5: Update CONSCIENCE.md → set status to "Ready to plan"
STEP 6: MANDATORY FILE GATE → verify ALL 16 files exist
FINAL: Completion Display → show full project summary
Complete each step before starting the next.
Step 1: Validate Prerequisites
test -f .planning/VISION.md && test -f .planning/ROADMAP.md && echo "READY" || echo "MISSING — run /fire-1b-research first"
If files are missing, stop and tell the user to run /fire-1b-research first.
Step 2: WARRIOR Handoff Init
Create handoff directory if not exists:
mkdir -p ~/.claude/warrior-handoffs/
Create initial handoff file:
~/.claude/warrior-handoffs/{PROJECT_NAME}_YYYY-MM-DD_init.md
Include: project name, core value, locked stack, phase count, current status, key decisions made, next steps.
Step 3: Zero-Friction Tooling (MANDATORY)
Claude auto-installs ALL CLI tools the locked VISION.md stack requires. The user should never manually install anything.
Read VISION.md and install everything the stack needs.
Reference: @skills-library/_general/methodology/ZERO_FRICTION_CLI_SETUP.md
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.
- 3d ago First seen · 283 lines · 16 tokens per session scan A 659dc0aa10e9
fire-1c-setup is a command published in the GitHub repository ThierryN/fire-flow (77 stars, last pushed 21d ago), licensed MIT. It adds 16 tokens to every session and 2,385 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.