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/Yassinello/claude-plugin-prd-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/commands/yassinello/claude-plugin-prd-workflow/review-prd)<a href="https://agentmods.dev/commands/yassinello/claude-plugin-prd-workflow/review-prd"><img src="https://agentmods.dev/badge/commands/yassinello/claude-plugin-prd-workflow/review-prd/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/commands/yassinello/claude-plugin-prd-workflow/review-prd"><img src="https://agentmods.dev/badge/commands/yassinello/claude-plugin-prd-workflow/review-prd.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.00014 | $0.01620 |
| Opus 5 | $0.00007 | $0.00810 |
| Sonnet 5 | $0.00003 | $0.00324 |
| Haiku 4.5 | $0.00001 | $0.00162 |
Grade A, and why
review-prd 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 9d 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 — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review PRD Command
Comprehensive PRD review following product-first, then technical approach.
Purpose
Review and validate PRDs before development with:
- Product validation: Right problem, right solution, right scope
- Technical feasibility: Can build it, how to build it, risks
- Clear decision: GO/ITERATE/KILL with honest assessment
- Grade assignment: A-F rating for quality tracking
Workflow
1. List & Select PRD
Scan product/prds/01-draft/ and display selection menu with PRD name, priority, and current grade.
2. Complete Review Analysis
Output comprehensive review in one response covering:
A. Product Review
Problem validation:
- User persona and pain point
- Frequency and severity
- Evidence (support tickets, user research, churn data)
- Challenge: Is this real and urgent?
Solution assessment:
- Proposed approach summary
- Scope (what's in, what's out, why)
- Alternative approaches considered
- Simplification opportunities
Component challenge:
- Each major component: Essential vs nice-to-have vs bloat
- Usage estimate and effort
- Impact if removed
- Verdict: Keep/Defer/Remove
User experience:
- Current vs proposed flow
- Friction points identified
- Journey improvements
Success metrics:
- How success is measured
- Targets with baselines
- Acceptance criteria completeness
Strategic context:
- Company strategy alignment
- Competitive landscape
- Timing rationale
Product Score: X/10 with strengths and weaknesses
B. Technical Review
Architecture & design:
- Proposed architecture fit
- Design patterns used
- Integration points
- Technical debt impact
Implementation breakdown:
- Major work areas with realistic estimates
- Critical paths identified
- Testing strategy
Dependencies & blockers:
- Technical dependencies (APIs, services, data)
- Team dependencies
- Hard blockers vs soft dependencies
Tech stack:
- New dependencies and their risks
- Breaking changes
- Tech debt created vs paid
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.
- 9d ago First seen · 266 lines · 14 tokens per session scan A fba2495c7bda
review-prd is a command published in the GitHub repository Yassinello/claude-plugin-prd-workflow (12 stars, last pushed 9mo ago), licensed MIT. It adds 14 tokens to every session and 1,620 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 commands, from other repositories
backlog
The project layer: milestones, epics, and user stories with refusing controllers — spec-seeded, sprint-ready.
sprint
Scope-boxed sprints over the backlog: one active sprint, explicit carry-over, a close that refuses to hide unfinished work.
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.
setup
Use when the user runs /evo:setup (or /evo:setup), asks to configure evolve-loop, onboard, pick per-phase models, or learn how the pipeline works. Auto-detects available LLM CLIs/subscriptions, explains the pipeline concisely, then presents THREE ready-made config presets (Recommended/Economy/Max-quality) the Go…
kickoff-phase
Start a scoped chunk of a larger plan in a fresh session — interview the user first, then implement only that chunk.
forge
Ore in, steel out. Full pipeline: plan → execute → verify. Use: /forge 'task', /forge --full, --discuss, --plan-only, --execute, --park, --resume.