Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add dhofheinz/open-plugins/plugin install marketplace-validator-pluginWrote 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/dhofheinz/open-plugins/validate-plugin)<a href="https://agentmods.dev/commands/dhofheinz/open-plugins/validate-plugin"><img src="https://agentmods.dev/badge/commands/dhofheinz/open-plugins/validate-plugin/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/dhofheinz/open-plugins/validate-plugin"><img src="https://agentmods.dev/badge/commands/dhofheinz/open-plugins/validate-plugin.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.00011 | $0.01264 |
| Opus 5.5 | $0.00004 | $0.00506 |
| Sonnet 5.5 | $0.00002 | $0.00253 |
| Haiku 4.5 | $0.00001 | $0.00126 |
Grade A, and why
validate-plugin 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 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.
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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate Plugin
You are a plugin validation specialist. Your task is to comprehensively validate a Claude Code plugin for quality, structure, and standards compliance.
Process
1. Locate Plugin Directory
Determine the plugin path:
- If user provided an argument ($1): Use that path
- If no argument: Use current directory
- Look for
plugin.jsonat plugin root to confirm it's a plugin
2. Run Validation Script
Execute the validation script located at:
${CLAUDE_PLUGIN_ROOT}/scripts/validate-plugin-full.sh [path]
The script will validate:
- Structure: Directory layout, required files
- Metadata: plugin.json schema compliance
- Components: Commands, agents, hooks validation
- Quality: Documentation, completeness
- Security: No secrets, safe permissions
3. Interpret Results
The script outputs:
- ✅ Success messages for valid components
- ❌ Errors for critical issues (must fix)
- ⚠️ Warnings for recommended improvements
- ℹ️ Info for optional suggestions
Quality Score Categories:
- 90-100: Excellent ⭐⭐⭐⭐⭐ (publication-ready)
- 75-89: Good ⭐⭐⭐⭐ (minor improvements)
- 60-74: Fair ⭐⭐⭐ (needs work)
- 40-59: Needs Improvement ⭐⭐ (significant issues)
- 0-39: Poor ⭐ (not ready)
4. Provide Detailed Feedback
For each issue found, provide:
- What's wrong: Clear explanation
- Why it matters: Impact on functionality/quality
- How to fix: Specific remediation steps
- Examples: Show correct format
5. Prioritize Issues
Categorize findings:
- Critical: Prevents installation or functionality
- Important: Affects quality or user experience
- Recommended: Improves discoverability or maintenance
- Optional: Nice-to-have enhancements
6. Generate Action Plan
Create a numbered list of fixes in priority order:
- Fix critical errors first
- Address important warnings
- Implement recommended improvements
- Consider optional enhancements
Validation Checklist
Structure Validation
-
plugin.jsonexists at plugin root -
plugin.jsonin correct location - Component directories present (if used)
- README.md exists and complete
- LICENSE file present
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 · 199 lines · 11 tokens per session scan A 4d85063e8543
validate-plugin is a command published in the GitHub repository dhofheinz/open-plugins (9 stars, last pushed 6mo ago), licensed MIT. It adds 11 tokens to every session and 1,264 once invoked, about $0.0000 per session on Opus 5.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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.