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/fabriqaai/specs.md/firegit clone --depth 1 https://github.com/fabriqaai/specs.mdWhat 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.00013 | $0.00298 |
| Opus 5 | $0.00006 | $0.00149 |
| Sonnet 5 | $0.00003 | $0.00060 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
fire 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.
What it actually says
Activate FIRE
Command: /specsmd-fire
Activation
You are now the FIRE Orchestrator for specsmd.
IMMEDIATELY read and adopt the persona from:
→ .specsmd/fire/agents/orchestrator/agent.md
Critical First Steps
- Read Config:
.specsmd/fire/memory-bank.yaml - Check Initialization: Verify
.specs-fire/state.yamlexists - If NOT initialized → Execute
project-initskill - If initialized → Execute
routeskill to determine next action
Your Skills
- Project Init:
.specsmd/fire/agents/orchestrator/skills/project-init/SKILL.md→ Initialize new project - Route:
.specsmd/fire/agents/orchestrator/skills/route/SKILL.md→ Route to appropriate agent - Status:
.specsmd/fire/agents/orchestrator/skills/status/SKILL.md→ Show project status
Routing Targets
- Planning: Planner Agent →
/specsmd-fire-planner - Building: Builder Agent →
/specsmd-fire-builder
Begin
Activate now. Read your agent definition and start the orchestration process.
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 · 47 lines · 13 tokens per session scan A 41dc83f4394d
fire is a command published in the GitHub repository fabriqaai/specs.md (205 stars, last pushed 10d ago), licensed MIT. It adds 13 tokens to every session and 298 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
specify
Create or update the feature specification from a natural language feature description.
speckit.git.validate
Validate current branch follows feature branch naming conventions.
speckit.wrap-test
Self-test wrap command — pre/post around core.
/spdd-reasons-canvas
Generate REASONS-Canvas structured prompts from business context without external template.
speckit.assess.intake
Capture and normalize a raw idea (text, URL, ticket, or codebase pointer) into an intake note.
proposal
Create a structured feature proposal in docs/11-proposals/.