Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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-health)<a href="https://agentmods.dev/commands/yassinello/claude-plugin-prd-workflow/plugin-health"><img src="https://agentmods.dev/badge/commands/yassinello/claude-plugin-prd-workflow/plugin-health.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.00000 | $0.00513 |
| Opus 5 | $0.00000 | $0.00257 |
| Sonnet 5 | $0.00000 | $0.00103 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
plugin-health 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 6d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Health Check Command
You are helping the user verify the health of their claude-prd-workflow plugin installation.
Your Task
Run the health check script and interpret the results for the user.
Steps
-
Navigate to plugin directory
cd ~/.claude-code/plugins/claude-prd-workflow -
Run health check
node bin/check-health.js -
Interpret results
- If all checks pass: Confirm plugin is healthy
- If warnings found: Explain what they mean
- If errors found: Suggest remediation steps
-
Provide next steps
- If healthy: User can use the plugin normally
- If issues: Offer to run
/plugin-repairor manual fix steps
Health Check Components
The health check verifies:
- ✅ Plugin directory exists
- ✅ Plugin metadata is valid
- ✅ Slash commands are installed
- ✅ AI agents are installed
- ✅ Skills are installed
Example Output
🏥 Running health check for claude-prd-workflow...
📁 Checking plugin installation...
✅ Plugin directory found: ~/.claude-code/plugins/claude-prd-workflow
📋 Checking plugin metadata...
✅ Plugin version: 2.7.0
📅 Installed: 10/26/2025
📝 Checking slash commands...
✅ Global commands: 17 files found
🤖 Checking AI agents...
✅ Global agents: 17 files found
⚡ Checking skills...
✅ Global skills: 13 files found
============================================================
📊 HEALTH CHECK SUMMARY
✅ All systems operational!
🎯 You can now use the following commands:
/create-prd - Create a new PRD
/list-prds - List all PRDs
/review-prd - Review a PRD
/code-prd - Start development
💡 Tip: Restart Claude Code if commands are not visible
============================================================
Troubleshooting
If health check fails:
- Offer to run automatic repair:
/plugin-repair - Suggest manual reinstallation:
node install.js - Link to troubleshooting guide
- Suggest reporting issue if problem persists
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.
- 6d ago First seen · 91 lines · 0 tokens per session scan A d18e02b2a4b8
plugin-health 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 513 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
debug
Systematic debugging: root cause before any fix, one hypothesis at a time, and a three-strikes rule that questions the architecture instead of stacking patches.
lint
The canonical linter per ecosystem over your changes: findings are diagnoses you judge, fix, or explain.
verify
让 agent 重新核对最近回复中的所有 file:line 引用与事实性陈述，并报告漂移/缺失。.
logic-fix-all
Autonomous audit-and-fix — after consent, scan the target, fix every logic issue found (all severities), verify each fix, and report anything unresolved.
logic-health
Sweep a whole codebase or directory for logic correctness — use before a release or to identify risk hotspots.
logic-locate
Locate the root cause of a confirmed failure — use when you have a stack trace, failing test, or wrong output.