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-updategit 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.00687 |
| Opus 5 | $0.00000 | $0.00344 |
| Sonnet 5 | $0.00000 | $0.00137 |
| Haiku 4.5 | $0.00000 | $0.00069 |
Grade C, and why
plugin-update scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf claude-prd-workflow How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Update Command
You are helping the user update the claude-prd-workflow plugin to the latest version.
Your Task
Run the automated update script that handles everything.
Steps
-
Navigate to plugin directory
cd ~/.claude-code/plugins/claude-prd-workflow -
Run update script
node bin/update.js
The script automatically:
- ✅ Checks current version
- ✅ Fetches latest version from GitHub
- ✅ Backs up current state
- ✅ Updates via git pull or manual download
- ✅ Reinstalls to update global commands/agents/skills
- ✅ Runs health check to verify installation
- ✅ Shows what's new
- Post-update
- Remind user to restart Claude Code
- Suggest running
/plugin-healthto verify - Link to CHANGELOG.md for details
Alternative: Manual Update
If automatic update fails, provide manual instructions:
# Backup config
cp -r ~/.claude-code/plugins/claude-prd-workflow/.claude ~/prd-config-backup
# Update via git
cd ~/.claude-code/plugins/claude-prd-workflow
git pull origin main
node install.js
# Or fresh install
cd ~/.claude-code/plugins
rm -rf claude-prd-workflow
git clone https://github.com/Yassinello/claude-prd-workflow
cd claude-prd-workflow
node install.js
# Restore config if needed
cp -r ~/prd-config-backup ~/.claude-code/plugins/claude-prd-workflow/.claude
# Verify
node bin/check-health.js
Important Notes
- The update script automatically backs up your config
- Your PRD files in
product/are never touched - If update fails, the plugin stays on the old version (safe)
- Always restart Claude Code after updating
- Run
/plugin-healthto verify the update succeeded
Example Output
🔄 Updating claude-prd-workflow plugin...
📦 Current version: 2.7.0
============================================================
🔍 Checking for updates...
Checking git status...
Fetching latest version from GitHub...
Pulling latest changes...
============================================================
🔨 Reinstalling to update global files...
Running install.js...
✅ Copied commands/
✅ Copied agents/
✅ Copied skills/
✅ Installed 17 slash commands
✅ Installed 17 AI agents
✅ Installed 13 skills
🏥 Running automatic health check...
✅ All systems operational!
============================================================
✅ Update complete!
📦 Updated: 2.7.0 → 2.8.0
💡 Important:
1. Restart Claude Code to see the changes
2. Run /plugin-health to verify the update
3. Check CHANGELOG.md for what's new
============================================================
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 · 123 lines · 0 tokens per session scan C f37edb28fe78
plugin-update 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 687 tokens. A static security scan graded it C with 1 finding (recursive force delete). 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…