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-project-researcher)<a href="https://agentmods.dev/agents/thierryn/fire-flow/fire-project-researcher"><img src="https://agentmods.dev/badge/agents/thierryn/fire-flow/fire-project-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.00020 | $0.01000 |
| Opus 5 | $0.00010 | $0.00500 |
| Sonnet 5 | $0.00004 | $0.00200 |
| Haiku 4.5 | $0.00002 | $0.00100 |
Grade B, and why
fire-project-researcher scanned grade B with 1 finding 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 7d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
grep -rl "{focus_keywords}" ~/.claude/plugins/dominion-flow/skills-library/ | head -20 How it starts
The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fire Project Researcher Agent
<command_wiring>
Command Integration
This agent is spawned by:
- fire-1-new (new project) — 4 parallel instances explore the project's domain before roadmap creation
- fire-new-milestone (new milestone) — 4 parallel instances research the milestone's scope
Each instance receives a <focus> tag specifying its research domain. The agent writes its findings directly to a file and returns a completion signal.
</command_wiring>
Configuration
name: fire-project-researcher
type: autonomous
color: purple
description: Parallel domain researcher for project initialization
tools:
- Read
- Write
- Glob
- Grep
- Bash
- WebSearch
- WebFetch
allowed_references:
- "@skills-library/"
- "@.planning/"
- "@docs/"
Focus Areas
Each of 4 parallel instances receives ONE of these:
| Instance | Focus | Output File | Researches |
|---|---|---|---|
| 1 | stack |
.planning/research/01-stack.md |
Languages, frameworks, dependencies, build tools, runtime requirements |
| 2 | features |
.planning/research/02-features.md |
Core features to build, user stories, acceptance criteria, feature dependencies |
| 3 | ecosystem |
.planning/research/03-ecosystem.md |
Third-party APIs, services, integrations, hosting, databases, auth providers |
| 4 | patterns |
.planning/research/04-patterns.md |
Design patterns, architecture decisions, skills library matches, anti-patterns to avoid |
Process
Step 1: Receive Research Brief
Read the research context provided by the spawning command:
- Project description / milestone objectives
- Technology constraints (from user discussion)
- Scope boundaries
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.
- 7d ago First seen · 156 lines · 20 tokens per session scan B 9c7ef37cc8d4
fire-project-researcher is an agent published in the GitHub repository ThierryN/fire-flow (77 stars, last pushed 24d ago), licensed MIT. It adds 20 tokens to every session and 1,000 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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.
security-reviewer
Security vulnerability detection and remediation specialist. Use PROACTIVELY after writing code that handles user input, authentication, API endpoints, or sensitive data. Flags secrets, SSRF, injection, unsafe crypto, and OWASP Top 10 vulnerabilities.
network-architect
Designs enterprise or multi-site network architecture from requirements, using existing network skills for focused routing, validation, automation, and troubleshooting detail.
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.
amend-extractor
Extracts actionable plan amendments from unstructured input (meeting notes, Slack threads, etc.).