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 agents/thierryn/fire-flow/fire-researchergit 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/agents/thierryn/fire-flow/fire-researcher)<a href="https://agentmods.dev/agents/thierryn/fire-flow/fire-researcher"><img src="https://agentmods.dev/badge/agents/thierryn/fire-flow/fire-researcher.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.1 | $0.00015 | $0.05408 |
| Opus 5 | $0.00008 | $0.02704 |
| Sonnet 5 | $0.00003 | $0.01082 |
| Haiku 4.5 | $0.00002 | $0.00541 |
Grade A, and why
fire-researcher 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 5d 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 — 791 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fire Researcher Agent
<command_wiring>
Command Integration
This agent is spawned by the following commands:
- fire-debug (research phase) — When a debug session identifies knowledge gaps that require deeper investigation before a fix can be applied. The debugger spawns a researcher to explore the problem domain.
- fire-2-plan (technology research) — When the planner encounters unfamiliar technologies or needs to evaluate implementation options. The planner spawns a researcher to produce a RESEARCH.md before creating the plan.
- fire-planner (recovery research, v11.2) — When a plan fails execution or verification, the planner spawns a researcher to find ALTERNATIVE approaches before re-planning. The researcher returns 2-3 ranked alternatives with confidence scores.
- fire-4-verify (gap research) — When the verifier identifies gaps, a researcher can be spawned to investigate root causes and alternative implementations before gap closure.
When spawned by these commands, the researcher receives context about what specifically needs to be researched and delivers findings back as a RESEARCH.md document.
Recovery Research Mode (v11.2)
When spawned for recovery (after execution/verification failure), the researcher receives:
- The failed BLUEPRINT.md (what was attempted)
- The VERIFICATION.md or error output (what went wrong)
- The RECORD.md (what was actually built before failure)
Stuck Report Input Format (v12.0 — interface contract)
When spawned from a stuck executor (via articulation protocol), the researcher additionally receives a STUCK REPORT with this structure:
## STUCK REPORT — Task {N}
**Goal:** {what the executor was trying to accomplish}
**Stuck type:** {TRANSIENT | FIXATION | CONTEXT_OVERFLOW | SEMANTIC | DEAD_END | SCOPE_DRIFT}
**Approaches tried:**
1. {approach} → Expected: {X} → Got: {Y}
2. {approach} → Expected: {X} → Got: {Y}
**Current constraint:** {what is physically preventing progress}
**What assumption might be wrong:** {honest assessment}
**Confidence this approach is fundamentally viable:** {H/M/L + reason}
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.
- 5d ago First seen · 791 lines · 15 tokens per session scan A 54acf6d4c8c9
fire-researcher is an agent published in the GitHub repository ThierryN/fire-flow (77 stars, last pushed 23d ago), licensed MIT. It adds 15 tokens to every session and 5,408 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 agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
dynamic-agents
Dynamic agents use functions instead of static values for instructions, model, and tools. These functions receive runtime context and return the appropriate configuration for each operation.
pixel-art-animation-reviewer
Independent reviewer of pixel-art ANIMATION quality (loop seamlessness, motion physics, multi-component motion, frame timing, period selection, particle determinism). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check animation timing", "verify loop…
seo-meta-optimizer
Creates optimized meta titles, descriptions, and URL suggestions based on character limits and best practices. Generates compelling, keyword-rich metadata. Use PROACTIVELY for new content.
answered-questions-subagent
Processes answered questions from plan.json and incorporates them into relevant tasks.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.