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/complete-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/complete-prd)<a href="https://agentmods.dev/commands/yassinello/claude-plugin-prd-workflow/complete-prd"><img src="https://agentmods.dev/badge/commands/yassinello/claude-plugin-prd-workflow/complete-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.00016 | $0.01271 |
| Opus 5 | $0.00008 | $0.00635 |
| Sonnet 5 | $0.00003 | $0.00254 |
| Haiku 4.5 | $0.00002 | $0.00127 |
Grade A, and why
complete-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 5d 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Complete PRD Command
Mark a PRD as complete after successful PR merge and deployment.
Purpose
Close the PRD lifecycle:
- Review and merge PR (if needed)
- Verify production deployment
- Update PRD status to "Complete"
- Move PRD to
04-complete/ - Clean up worktree and branch
- Document completion metrics
Workflow
1. Identify PRD to Complete
List PRDs from 02-ready/ and 03-in-progress/ with their PR status:
- PRD ID and feature name
- Branch name
- PR status (merged ✅ / open 🔄 / none ❌)
User selects PRD by number, ID, or filename.
2. Check PR Status
If no PR:
- ❌ Cannot complete without PR
- Suggest: Create PR first or use
/code-prdto finish implementation
If PR open:
- Show PR details (branch, checks, approvals, conflicts)
- Ask: Review and merge now? (yes/no)
If PR merged:
- ✅ Proceed to deployment verification
3. Review & Merge PR (if open)
PR Review checklist:
- Code quality: Clean, readable, follows patterns
- Tests: Coverage adequate, passing
- Security: No obvious vulnerabilities
- Performance: No regressions
- Documentation: Updated if needed
Merge process:
- Check CI/CD status (all green?)
- Check conflicts (rebase if needed)
- Merge to main branch
- Delete feature branch (optional)
4. Verify Deployment
Check deployment status:
- Latest commit on main deployed?
- Deployment successful?
- Health checks passing?
- Rollback needed?
If not deployed:
- Wait for auto-deployment OR
- Trigger manual deployment OR
- Schedule completion after deployment
5. Update PRD Document
Add completion section to PRD frontmatter:
---
status: complete
completed_date: YYYY-MM-DD
pr_number: #XX
pr_url: https://github.com/...
deployment_verified: true
actual_effort: X days
notes: |
Brief completion notes
---
6. Move to Complete
git mv product/prds/03-in-progress/PRD-XXX-name.md product/prds/04-complete/
git commit -m "docs: Complete PRD-XXX - Feature Name"
git push origin main
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.
- 5d ago First seen · 233 lines · 16 tokens per session scan A bf2e8fcc1e68
complete-prd is a command published in the GitHub repository Yassinello/claude-plugin-prd-workflow (12 stars, last pushed 9mo ago), licensed MIT. It adds 16 tokens to every session and 1,271 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
brooks-health
Run a Brooks-Lint codebase health dashboard across all four dimensions.
brooks-debt
Run a Brooks-Lint tech debt assessment.
plan
Turn an approved spec into an implementation plan an engineer with zero context could execute — with a quality controller that blocks placeholders and hollow tasks.
audit
Onboard an existing codebase: every domain's checks over the whole tree, then a triaged plan to bring it in line.
test
Run the repository's actual test suite: every ecosystem's canonical runner — NOT run is never green.
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.