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/plugin-versiongit clone --depth 1 https://github.com/Yassinello/claude-plugin-prd-workflowWhat 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.00000 | $0.00626 |
| Opus 5 | $0.00000 | $0.00313 |
| Sonnet 5 | $0.00000 | $0.00125 |
| Haiku 4.5 | $0.00000 | $0.00063 |
Grade A, and why
plugin-version 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 2d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Version Checker
Display the installed version of the claude-prd-workflow plugin and check for updates.
Instructions
You are tasked with displaying version information for the claude-prd-workflow plugin.
Steps
-
Check installed version:
npm list -g claude-prd-workflow --depth=0This shows the currently installed version.
-
Check latest version on npm:
npm view claude-prd-workflow versionThis shows the latest published version on the npm registry.
-
Display comparison:
- Compare installed version vs. latest version
- If versions match: ✅ "You're up to date!"
- If installed < latest: ⚠️ "Update available!"
- If check fails: Provide troubleshooting steps
-
Format output:
Claude PRD Workflow Manager ============================= 📦 Installed version: X.Y.Z 🌐 Latest version: X.Y.Z Status: [✅ Up to date | ⚠️ Update available] [If update available] To update: npm install -g claude-prd-workflow@latest Changelog: https://github.com/Yassinello/claude-prd-workflow/blob/main/CHANGELOG.md -
Additional information:
- Installation path: Show where plugin is installed
- Files status: Verify commands/agents/skills are properly installed
- Quick check:
# Verify files exist ls ~/.claude-code/commands/ | grep -E "(create-prd|review-prd|code-prd)" ls ~/.claude-code/agents/ | grep -E "(prd-reviewer|prd-implementer)"
Error Handling
- Plugin not found: Suggest installation instructions
- npm not available: Explain manual verification method
- Network issues: Show cached info from local files
Example Output
Claude PRD Workflow Manager
=============================
📦 Installed version: 1.2.0
🌐 Latest version: 1.3.0
⚠️ Update available!
New features in v1.3.0:
- Improved PRD validation
- Enhanced security scanning
- Bug fixes for Git worktree
To update:
npm install -g claude-prd-workflow@latest
After updating, restart Claude Code.
Changelog: https://github.com/Yassinello/claude-prd-workflow/blob/main/CHANGELOG.md
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.
- 2d ago First seen · 104 lines · 0 tokens per session scan A 3abbc1e4a50d
plugin-version is a command published in the GitHub repository Yassinello/claude-plugin-prd-workflow (12 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 626 tokens. 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
simplify
The over-engineering review: five tags (delete, stdlib, native, yagni, shrink), a mandatory replacement per finding, and a real null result when there is nothing to cut.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
VibeGuard: ExecPlan
Long-term task execution plan — generates self-contained execution documents from SPEC, supports cross-session recovery.
VibeGuard: Review
Structured code review - first run the guard to obtain the baseline, then review according to security → logic → quality → performance priority.
help
Category: System Syntax: /help [command|topic].
remediate
Close the debt the deterministic lanes cannot version-bump away: the grandfathered broken build, advisories with no direct upgrade path, the lint backlog, missing tests, missing docs. Each run plans that debt as finite work orders and works them in two tiers: deterministic recipes execute first at $0 (lockfile resync…