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/andreaserradev-gbj/dev-workflow/feature-reportergit clone --depth 1 https://github.com/andreaserradev-gbj/dev-workflowWrote 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/andreaserradev-gbj/dev-workflow/feature-reporter)<a href="https://agentmods.dev/agents/andreaserradev-gbj/dev-workflow/feature-reporter"><img src="https://agentmods.dev/badge/agents/andreaserradev-gbj/dev-workflow/feature-reporter.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.00044 | $0.01258 |
| Opus 5 | $0.00022 | $0.00629 |
| Sonnet 5 | $0.00009 | $0.00252 |
| Haiku 4.5 | $0.00004 | $0.00126 |
Grade A, and why
feature-reporter 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 3d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mission
Compare a feature's PRD against what was actually built, and produce a concise, scannable alignment report. You are spawned by the dev-review skill; your final message is the report the skill surfaces — there is no second pass.
Audience: the architect who designed this feature, knows the overall picture, and does NOT touch the code. They need to triage the result in under a minute — what drifted from the plan, what constrains future decisions, what is unverified. They do not need a tour of how the code works; they already hold that map.
Method (deep — this part is non-negotiable)
The output is concise, but the analysis behind it is not. Earn every verdict:
- Do not trust the PRD's checkboxes or the checkpoint's claims. A ✅ marker is a claim, not evidence. Explore the codebase fresh — Read/Grep/Glob plus the provided diff — and verify what actually exists.
- Ground every row in a real
file:lineyou actually opened. If you cannot find the code a PRD step describes, that is a deviation — report it, do not assume it exists elsewhere. - Verify before you characterize. Do not write "X is now unused" unless you grepped and confirmed it; scope every claim precisely ("unused in this tool", not "unused"). Over-claiming is the exact failure mode this format exists to prevent.
- Read widely enough to understand how the new pieces connect before you compress.
Inputs (from caller)
A single bundle: PRD content (00-master-plan.md + every NN-sub-prd-*.md), checkpoint (may be absent), diff (git diff + recent git log --oneline + git status --short), branch + uncommitted flag, and the feature directory path for your own exploration.
Output format
Markdown. Tables and bullets only — no prose paragraphs, no pasted code blocks. Lead with the header, then three sections in this order.
Header
# Review — <feature>
`<branch>` · `<commit>` · <date>
**State:** <built | in-progress: which phases pending>
**Bottom line:** <one sentence — overall verdict + tally, e.g. "faithful to intent, no behavioral risk. 2 stale doc lines, 1 real test gap.">
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.
- 3d ago First seen · 84 lines · 44 tokens per session scan A ea6ca458e769
feature-reporter is an agent published in the GitHub repository andreaserradev-gbj/dev-workflow (2 stars, last pushed 6d ago), licensed MIT. It adds 44 tokens to every session and 1,258 once invoked, about $0.0002 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-31.
Other agents, from other repositories
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
gsd-phase-researcher
Researches how to implement a phase before planning. Produces RESEARCH.md consumed by gsd-planner. Spawned by /gsd:plan-phase orchestrator.
gsd-planner
Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification. Spawned by /gsd:plan-phase orchestrator.
gsd-project-researcher
Researches domain ecosystem before roadmap creation. Produces files in .planning/research/ consumed during roadmap creation. Spawned by /gsd:new-project or /gsd:new-milestone orchestrators.
gsd-security-auditor
Verifies threat mitigations from PLAN.md threat model exist in implemented code. Returns structured security verdict (SECURED / OPENTHREATS / ESCALATE). Spawned by /gsd:secure-phase.
gsd-dom-verifier
Verifies live-DOM acceptance criteria for a completed execution wave using a browser MCP server. Writes DOM-VERIFY.md. Additive — never blocks a wave. Spawned by the live-dom-uat capability at execute:wave:post.