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/archive-prd)<a href="https://agentmods.dev/commands/yassinello/claude-plugin-prd-workflow/archive-prd"><img src="https://agentmods.dev/badge/commands/yassinello/claude-plugin-prd-workflow/archive-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.1 | $0.00010 | $0.02599 |
| Opus 5 | $0.00005 | $0.01300 |
| Sonnet 5 | $0.00002 | $0.00520 |
| Haiku 4.5 | $0.00001 | $0.00260 |
Grade A, and why
archive-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 8d 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 — 336 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Archive PRD Command
Move completed or cancelled PRDs to archive folder with metadata preservation.
Purpose
Keep PRD directories clean while preserving historical context:
- Archive completed features
- Archive cancelled/deprecated PRDs
- Maintain searchable history
- Generate archive summary
Workflow
Step 1: List Archivable PRDs
Show PRDs from:
04-complete/- Completed and merged- Any directory if user wants to cancel/deprecate
📦 **PRDs Available for Archiving**
## Completed (Ready to Archive)
| # | PRD ID | Feature | Completed | Days Since |
|---|--------|---------|-----------|------------|
| 1 | PRD-001 | Project Setup | 2025-09-15 | 40 days |
| 2 | PRD-002 | CI/CD Pipeline | 2025-09-20 | 35 days |
| 3 | PRD-005 | Database Schema | 2025-10-10 | 15 days |
## Other PRDs
To archive a PRD from another status (e.g., cancelled):
- Enter PRD ID manually
- Enter filename
Which PRD to archive? (number, PRD-XXX, or filename)
Step 2: Confirm Archive Reason
Ask user:
Why are you archiving PRD-005 (Database Schema)?
1. ✅ Completed and shipped
2. ❌ Cancelled (no longer needed)
3. 🔀 Superseded by another PRD
4. 🚫 Blocked indefinitely
5. Other (specify)
Select reason: (1-5)
Step 3: Collect Archive Metadata
Based on reason, ask relevant questions:
If Completed:
- PR number (if not in PRD)
- Production deploy date
- Any learnings/retrospective notes
If Cancelled:
- Why cancelled?
- Was any work done?
- Lessons learned
If Superseded:
- Superseded by which PRD?
- What changed in approach?
Step 4: Update PRD Header
Add archive metadata to PRD:
**Status**: Archived
**Archive Reason**: Completed and shipped
**Archived Date**: 2025-10-25
**PR**: #42
**Production Deploy**: 2025-10-15
**Archive Notes**: Successful implementation, no major issues. Performance exceeded targets.
Step 4.5: Auto-Close Orphaned PRs (NEW)
Purpose: Clean up draft PRs that were never developed
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.
- 8d ago First seen · 336 lines · 10 tokens per session scan A 651ec84992a6
archive-prd is a command published in the GitHub repository Yassinello/claude-plugin-prd-workflow (12 stars, last pushed 9mo ago), licensed MIT. It adds 10 tokens to every session and 2,599 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.