Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Yassinello/claude-plugin-prd-workflownpx agentmods add commands/yassinello/claude-plugin-prd-workflow/plugin-updateWrote 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/plugin-update)<a href="https://agentmods.dev/commands/yassinello/claude-plugin-prd-workflow/plugin-update"><img src="https://agentmods.dev/badge/commands/yassinello/claude-plugin-prd-workflow/plugin-update/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/yassinello/claude-plugin-prd-workflow/plugin-update"><img src="https://agentmods.dev/badge/commands/yassinello/claude-plugin-prd-workflow/plugin-update.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00687 |
| Opus 5.5 | $0.00000 | $0.00275 |
| Sonnet 5.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 1mo 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.
- 1mo 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 11mo 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
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.
sm-buff
You usually don't run buff directly — run sm sail. sm sail drives the whole PR to green and calls buff watch / triage for you, stopping only when it needs you to act (see /sm-sail). Reach for sm buff here only for surgical work: inspecting a specific failure, or resolving a single review thread when sail has parked on…
sm-swab
Run slop-mop's iterative development loop for this repository.