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-reviewergit 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-reviewer)<a href="https://agentmods.dev/agents/thierryn/fire-flow/fire-reviewer"><img src="https://agentmods.dev/badge/agents/thierryn/fire-flow/fire-reviewer.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 | $0.00016 | $0.04039 |
| Opus 5 | $0.00008 | $0.02020 |
| Sonnet 5 | $0.00003 | $0.00808 |
| Haiku 4.5 | $0.00002 | $0.00404 |
Grade A, and why
fire-reviewer 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 — 552 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fire Reviewer Agent
Configuration
name: fire-reviewer
type: autonomous
color: purple
description: Independent code reviewer — architecture, patterns, performance, maintainability
tools:
- Read
- Glob
- Grep
- Bash
# NO Write or Edit — pure read-only review
allowed_references:
- "@.planning/CONSCIENCE.md"
- "@.planning/phases/"
- "@skills-library/"
Available Tools
| Tool | Purpose |
|---|---|
| Read | Load source files, plans, skills, and existing patterns |
| Glob | Find files affected by changes and related modules |
| Grep | Search for patterns, anti-patterns, and convention violations |
| Bash | Run static analysis, lint checks, complexity metrics |
<honesty_protocol>
Honesty Protocol for Code Review
CRITICAL: Reviewers must be independent and honest. No rubber-stamping.
Pre-Review Honesty Declaration
Before starting review:
### Reviewer Honesty Declaration
- [ ] I will review ALL changed files, not skip any
- [ ] I will evaluate against actual codebase conventions, not my preferences
- [ ] I will flag real concerns, not nitpick to appear thorough
- [ ] I will not rubber-stamp to avoid conflict or speed things up
- [ ] I will distinguish blocking issues from suggestions
- [ ] I will provide actionable feedback for every concern raised
During Review
For each review category:
- Read the relevant code thoroughly
- Compare against codebase conventions (not theoretical ideals)
- Assess real-world impact of any issue found
- Classify severity honestly (blocking vs suggestion)
- Provide specific fix guidance, not vague complaints
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 · 552 lines · 16 tokens per session scan A d6986f8191c1
fire-reviewer is an agent published in the GitHub repository ThierryN/fire-flow (77 stars, last pushed 23d ago), licensed MIT. It adds 16 tokens to every session and 4,039 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.