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 commands/yassinello/claude-plugin-prd-workflow/create-prdgit 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/create-prd)<a href="https://agentmods.dev/commands/yassinello/claude-plugin-prd-workflow/create-prd"><img src="https://agentmods.dev/badge/commands/yassinello/claude-plugin-prd-workflow/create-prd.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.00014 | $0.02401 |
| Opus 5 | $0.00007 | $0.01201 |
| Sonnet 5 | $0.00003 | $0.00480 |
| Haiku 4.5 | $0.00001 | $0.00240 |
Grade A, and why
create-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 4d 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 — 351 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create PRD Command
Create a new Product Requirements Document with interactive questions to refine scope before generation.
Purpose
Generate well-scoped PRDs through:
- Interactive clarifying questions
- AI-assisted content generation
- Standardized structure
- Automatic ID assignment
- Draft mode by default (review later on feature branch)
Workflow
Step 0: Check for Template Usage (NEW in v2.6)
Check for --template flag:
/create-prd --template=ecommerce "Add shopping cart feature"
If template specified:
- List available templates if
--list-templates - Load template YAML file
- Pre-fill PRD sections from template
- Skip to Step 3 (generation)
Available Templates (7 total):
- 🛒
ecommerce- Online store with cart, checkout, payments - 💼
saas- SaaS app with auth, billing, dashboard - 📱
mobile-app- Cross-platform mobile with offline support - 🔌
api-service- REST/GraphQL API with documentation - ⚙️
admin-panel- Admin dashboard with CRUD operations - 📊
analytics-dashboard- Real-time analytics and reporting - 🔗
integration- Third-party API integration with webhooks
List templates:
/create-prd --list-templates
📋 Available PRD Templates:
1. 🛒 ecommerce - E-Commerce Store
Online store with product catalog, cart, checkout, and payments
2. 💼 saas - SaaS Application
SaaS app with authentication, billing, and user dashboard
3. 📱 mobile-app - Mobile Application
Cross-platform mobile app for iOS and Android
4. 🔌 api-service - API Service
RESTful API or GraphQL service with documentation
5. ⚙️ admin-panel - Admin Dashboard
Internal admin panel with CRUD and user management
6. 📊 analytics-dashboard - Analytics Dashboard
Real-time analytics and reporting dashboard
7. 🔗 integration - Third-Party Integration
Integration with third-party API and webhooks
Usage: /create-prd --template=<name> "Your feature description"
Example: /create-prd --template=ecommerce "Add shopping cart"
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.
- 4d ago First seen · 351 lines · 14 tokens per session scan A a2b4a0a26593
create-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 2,401 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.