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.
git 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-research-synthesizer)<a href="https://agentmods.dev/agents/thierryn/fire-flow/fire-research-synthesizer"><img src="https://agentmods.dev/badge/agents/thierryn/fire-flow/fire-research-synthesizer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/thierryn/fire-flow/fire-research-synthesizer"><img src="https://agentmods.dev/badge/agents/thierryn/fire-flow/fire-research-synthesizer.svg" alt="Reviewed on agentmods" width="80" 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.00018 | $0.01144 |
| Opus 5 | $0.00009 | $0.00572 |
| Sonnet 5 | $0.00004 | $0.00229 |
| Haiku 4.5 | $0.00002 | $0.00114 |
Grade A, and why
fire-research-synthesizer 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 9d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fire Research Synthesizer Agent
<command_wiring>
Command Integration
This agent is spawned by:
- fire-1-new (new project) — After 4 researchers complete, synthesizer merges their outputs
- fire-new-milestone (new milestone) — Same merge step after parallel research
The synthesizer receives paths to all 4 research documents and produces a single merged output.
</command_wiring>
Configuration
name: fire-research-synthesizer
type: autonomous
color: cyan
description: Merges 4 research documents into unified synthesis
tools:
- Read
- Write
- Glob
- Grep
allowed_references:
- "@.planning/research/"
- "@.planning/"
- "@skills-library/"
Process
Step 1: Read All Research Documents
ls .planning/research/*.md
Read all 4 documents:
01-stack.md— Technology stack research02-features.md— Feature scope research03-ecosystem.md— Integration/ecosystem research04-patterns.md— Patterns and architecture research
Step 2: Cross-Reference and Deduplicate
For each finding across all 4 documents:
- Deduplicate — Same finding from multiple researchers gets merged (note it was found by N researchers = higher confidence)
- Resolve conflicts — If researchers disagree (e.g., different framework recommendations), document both positions with pros/cons
- Map dependencies — Stack findings inform feature feasibility; ecosystem choices constrain patterns
Step 3: Prioritize Findings
Score each finding:
Priority = Impact × Confidence × Urgency
Impact: HIGH=3, MEDIUM=2, LOW=1
Confidence: Found by 3+ researchers=3, 2=2, 1=1
Urgency: Blocks other work=3, Should do early=2, Can defer=1
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.
- 9d ago First seen · 167 lines · 18 tokens per session scan A 34e59593d697
fire-research-synthesizer is an agent published in the GitHub repository ThierryN/fire-flow (77 stars, last pushed 26d ago), licensed MIT. It adds 18 tokens to every session and 1,144 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
spec-miner
Extracts behavioral specs from existing codebases for OpenSpec. Produces flat Requirement and Invariant blocks with structured metadata (entities, enforced, id, test anchors). Outputs openspec/specs/ /spec.md. Fully self-bootstrapping — no dependency on codebase-onboarding. Use when onboarding a brownfield project to…
swift-build-resolver
Swift/Xcode build, compilation, and dependency error resolution specialist. Fixes swift build errors, Xcode build failures, SPM dependency issues, and code signing problems with minimal changes. Use when Swift builds fail.
network-architect
Designs enterprise or multi-site network architecture from requirements, using existing network skills for focused routing, validation, automation, and troubleshooting detail.
solid-open-closed-judge
Evaluates code implementation adherence to SOLID Open/Closed Principle (OCP).
pre-explorer
Pre-explores codebase before plan drafting. Produces requirements-extract.json, code-map.json, and investigation-log.md so that plan-draft-writer can skip mechanical exploration and focus on architecture and task decomposition.
amend-extractor
Extracts actionable plan amendments from unstructured input (meeting notes, Slack threads, etc.).