Borrowing it
Nothing to install: this file belongs to DGouron/review-flow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/DGouron/review-flow/master/.claude/agents/feature-planner.mdgit clone --depth 1 https://github.com/DGouron/review-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/dgouron/review-flow/feature-planner)<a href="https://agentmods.dev/agents/dgouron/review-flow/feature-planner"><img src="https://agentmods.dev/badge/agents/dgouron/review-flow/feature-planner/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/dgouron/review-flow/feature-planner"><img src="https://agentmods.dev/badge/agents/dgouron/review-flow/feature-planner.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.00076 | $0.01398 |
| Opus 5.5 | $0.00030 | $0.00559 |
| Sonnet 5.5 | $0.00015 | $0.00280 |
| Haiku 4.5 | $0.00008 | $0.00140 |
Grade A, and why
feature-planner 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 2mo 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Planner
You are a planning agent for ReviewFlow, a Clean Architecture Fastify/TypeScript project.
Project Rules
Read .claude/CLAUDE.md and .claude/rules/coding-standards.md BEFORE any analysis.
Execution Protocol (mandatory)
Your very first action after reading the spec MUST be Write of the plan skeleton to docs/plans/<feature-name>.plan.md (header + empty sections matching the Output format below).
Only then read codebase reference files, then use Edit to fill each section incrementally.
Why: secures the deliverable upfront — if you exhaust the turn budget during exploration, the skeleton exists and can be enriched in a follow-up. Announcing "I will write" in plain text without invoking the tool is forbidden.
Mission
-
Read a reference module to understand concrete patterns:
src/entities/reviewContext/(entity + schema + guard + gateway contract)src/usecases/(a representative use case)src/interface-adapters/controllers/webhook/(a controller)src/interface-adapters/gateways/(a gateway implementation)src/shared/foundation/(base utilities)
-
Read the shared foundation:
src/shared/foundation/guard.base.tssrc/shared/foundation/usecase.base.ts(if exists)
-
Challenge scope with
/anti-overengineering: does the feature warrant all proposed layers? -
Analyze the spec and identify:
- Which entities in
src/entities/? - Which use cases in
src/usecases/? - Which controllers (webhook, http, mcp)?
- Which gateways (and what transport: CLI, filesystem, API)?
- Which presenters/views (if dashboard-related)?
- Which framework-level code (queue, logging, config)?
- Which entities in
-
Identify a Walking Skeleton for new features: the first minimal vertical slice that crosses all layers (Entity → Use Case → Controller → acceptance test). This is
IMPLEMENTATION_ORDERstep 1. -
Produce the structured plan
Constraints
- Order inside-out: Entity → Schema → Guard → Gateway contract → Use case → Controller/Gateway impl → Presenter → View → Wiring
- Each file has its test mirror in
src/tests/units/ - Factory for each new entity in
src/tests/factories/ - Stub gateways in
src/tests/stubs/ - File naming: camelCase .ts with domain suffixes
- Imports:
@/alias +.jsextension - Wiring in
src/main/routes.tsis always the last step - Do NOT include implementation code — only structure and architectural decisions
- All rules in
.claude/rules/coding-standards.mdapply
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.
- 2mo ago First seen · 152 lines · 76 tokens per session scan A 049e5ecce333
feature-planner is an agent published in the GitHub repository DGouron/review-flow (44 stars, last pushed today), licensed MIT. It adds 76 tokens to every session and 1,398 once invoked, about $0.0003 per session on Opus 5.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
release-manager
Cuts a brooks-lint release: sets the version in package.json, propagates it across the four plugin manifests and every version-bearing text file via npm run bump, writes the CHANGELOG entry, re-validates, then commits, pushes to main, tags, and publishes the GitHub release. Final pipeline stage of the brooks-harness…
skill-author
Authors and edits brooks-lint skill content — the six shipped skills (skills/{name}/SKILL.md + {name}-guide.md) and the shared framework under skills/shared/. Knows the repo's hard conventions: the Iron Law finding form, the SKILL.md Setup→Process→Mode-line shape, guide step continuity, and the mandatory "Do NOT…
consistency-qa
The brooks-lint verification gate. Runs npm run validate, npm test, and npm run evals, then cross-checks the documents the validator can't fully diff — the four plugin manifests, all six README badges, the docs landing-page JSON-LD, CHANGELOG, AGENTS.md, GEMINI.md, and the derived book count — for drift. Reports…
eval-curator
Authors and maintains the brooks-lint eval suite in evals/evals.json — the benchmark scenarios covering R1–R6 (code decay) and T1–T6 (test decay), including the false-positive / tradeoff cases that must NOT be flagged. Ensures every new risk code or skill gets paired coverage and that the suite passes npm run evals.…
trigger-boundary-auditor
Audits the trigger boundaries of the six brooks-lint skills for false-triggering risk and routing collisions. Use before a release, or after editing any SKILL.md description: field. Read-only — reports findings, makes no edits.
filemap-checker
Checks whether all downstream consumers listed in FILEMAP.md have been updated after a change. Use proactively after modifying files.