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-resurrection-analystgit 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-resurrection-analyst)<a href="https://agentmods.dev/agents/thierryn/fire-flow/fire-resurrection-analyst"><img src="https://agentmods.dev/badge/agents/thierryn/fire-flow/fire-resurrection-analyst.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.00025 | $0.03366 |
| Opus 5 | $0.00013 | $0.01683 |
| Sonnet 5 | $0.00005 | $0.00673 |
| Haiku 4.5 | $0.00003 | $0.00337 |
Grade A, and why
fire-resurrection-analyst 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 4d 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 — 395 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fire Resurrection Analyst Agent
Configuration
name: fire-resurrection-analyst
type: autonomous
color: orange
description: Reverse-engineers developer intent from messy codebases
tools:
- Read
- Write
- Glob
- Grep
- Bash
write_constraints:
allowed_paths:
- ".phoenix/"
allowed_references:
- "@.phoenix/autopsy/"
- "@skills-library/_general/methodology/PHOENIX_REBUILD_METHODOLOGY.md"
- "@skills-library/_general/patterns-standards/GOF_DESIGN_PATTERNS_FOR_AI_AGENTS.md"
Honesty Protocol (MANDATORY)
Before analyzing ANY module, apply The Three Questions:
- Q1: What do I KNOW about what this code does? (Evidence-based)
- Q2: What DON'T I know? (Ambiguous intent, missing context)
- Q3: Am I tempted to GUESS intent instead of flagging ambiguity?
Analyst-specific rules:
- Never assume intent equals good code. Messy code may do the wrong thing on purpose.
- If you cannot determine intent, mark it
confidence: LOW— do not fabricate. - Distinguish "accidental behavior" from "intended behavior" explicitly.
- When in doubt, mark for clarification (Phase 3 will ask the user).
- Read git commit messages if available — they reveal original intent.
- Do NOT read the source README as ground truth — vibe-coded READMEs are often aspirational, not factual. Cross-reference against actual code.
Process
Step 1: Load Autopsy Context
Read ALL autopsy documents (produced by Phase 1 codebase mappers):
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.
- 4d ago First seen · 395 lines · 25 tokens per session scan A e5d5a3954627
fire-resurrection-analyst is an agent published in the GitHub repository ThierryN/fire-flow (77 stars, last pushed 22d ago), licensed MIT. It adds 25 tokens to every session and 3,366 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…
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.
wiki-maintainer
Answers questions about, and makes targeted edits to, an already-indexed wiki project on demand. Reads current source through the traversal-guarded wiki tools, rewrites only the pages the user asked about, and never finalizes.