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/list-prds)<a href="https://agentmods.dev/commands/yassinello/claude-plugin-prd-workflow/list-prds"><img src="https://agentmods.dev/badge/commands/yassinello/claude-plugin-prd-workflow/list-prds.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.00015 | $0.00819 |
| Opus 5 | $0.00008 | $0.00409 |
| Sonnet 5 | $0.00003 | $0.00164 |
| Haiku 4.5 | $0.00002 | $0.00082 |
Grade A, and why
list-prds 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 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.
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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
List PRDs Command
Display all PRDs across directories with filtering and sorting.
Purpose
Quick overview of PRD status:
- View all PRDs at a glance
- Filter by status, priority, grade
- Sort by various criteria
- Track progress across projects
Workflow
1. Scan PRD Directories
Scan all PRD directories:
01-draft/: Drafts awaiting review02-ready/: Reviewed, ready for development03-in-progress/: Currently being implemented04-complete/: Completed features05-archived/: Archived PRDs
2. Display PRD Table
📋 PRDs Overview (15 total)
| ID | Feature | Status | Priority | Grade | Owner | Effort |
|----|---------|--------|----------|-------|-------|--------|
| 003 | OAuth2 Integration | Complete ✅ | P0 | A- | Alice | 7d |
| 005 | Dark Mode | In Progress 🔄 | P1 | B+ | Bob | 3d |
| 007 | API v2 | Ready 📦 | P0 | A | - | 12d |
| 008 | Export Feature | Draft 📝 | P2 | C | - | 5d |
| 009 | Mobile App | Archived 🗄️ | P1 | B | - | 30d |
Summary:
• Draft: 3 PRDs
• Ready: 2 PRDs
• In Progress: 1 PRD
• Complete: 8 PRDs
• Archived: 1 PRD
3. Apply Filters (Optional)
Filter by status:
/list-prds --status=ready
Filter by priority:
/list-prds --priority=P0
Filter by grade:
/list-prds --min-grade=B
Combine filters:
/list-prds --status=ready --priority=P0
4. Sort Results
Sort options:
--sort=priority: By priority (P0 first)--sort=grade: By grade (A first)--sort=date: By creation date--sort=effort: By estimated effort
Flags
Filters:
--status={draft|ready|in-progress|complete|archived}--priority={P0|P1|P2}--min-grade={A|B|C|D|F}--owner={name}
Display:
--sort={priority|grade|date|effort}--reverse: Reverse sort order--limit=N: Show only N results--verbose: Show more details
Examples:
/list-prds
/list-prds --status=ready --priority=P0
/list-prds --min-grade=B --sort=effort
/list-prds --verbose
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 · 130 lines · 15 tokens per session scan A 5cfd7d5474de
list-prds is a command published in the GitHub repository Yassinello/claude-plugin-prd-workflow (12 stars, last pushed 9mo ago), licensed MIT. It adds 15 tokens to every session and 819 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.