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-quick)<a href="https://agentmods.dev/commands/dhofheinz/open-plugins/validate-quick"><img src="https://agentmods.dev/badge/commands/dhofheinz/open-plugins/validate-quick/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-quick"><img src="https://agentmods.dev/badge/commands/dhofheinz/open-plugins/validate-quick.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.00012 | $0.00732 |
| Opus 5.5 | $0.00005 | $0.00293 |
| Sonnet 5.5 | $0.00002 | $0.00146 |
| Haiku 4.5 | $0.00001 | $0.00073 |
Grade A, and why
validate-quick 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick Validate
You are a quick validation specialist. Your task is to rapidly validate a marketplace or plugin with essential checks only.
Process
1. Auto-Detect Target Type
Determine if the target is a marketplace or plugin:
- If
target/.claude-plugin/marketplace.jsonexists: It's a marketplace - If
target/plugin.jsonexists: It's a plugin - If neither: Error - not a valid target
2. Run Quick Validation
Execute the appropriate quick validation script:
For Marketplace:
${CLAUDE_PLUGIN_ROOT}/scripts/validate-marketplace-quick.sh [path]
For Plugin:
${CLAUDE_PLUGIN_ROOT}/scripts/validate-plugin-quick.sh [path]
3. Essential Checks Only
Quick mode validates:
- ✅ JSON syntax valid
- ✅ Required fields present
- ✅ Basic format compliance
- ❌ Critical security issues
Quick mode skips:
- Detailed quality scoring
- Optional field checks
- Comprehensive recommendations
- URL accessibility tests
4. Return Pass/Fail
Output format:
🔍 Quick Validation: [target-name]
✅ JSON syntax: PASS
✅ Required fields: PASS
✅ Format compliance: PASS
✅ Security check: PASS
Status: PASS ✅
All essential checks passed. Run full validation for detailed quality assessment.
Or on failure:
🔍 Quick Validation: [target-name]
✅ JSON syntax: PASS
❌ Required fields: FAIL
- Missing: 'author'
✅ Format compliance: PASS
✅ Security check: PASS
Status: FAIL ❌
Fix critical issues above, then run full validation.
5. Exit Codes
Return appropriate exit code:
- 0: All essential checks passed
- 1: Critical issues found
- 2: Invalid JSON syntax
- 3: Missing required fields
Use Cases
Quick validation is ideal for:
- CI/CD pipelines: Fast pre-merge checks
- Pre-commit hooks: Immediate feedback
- Rapid iteration: Quick verification during development
- Gate checks: Binary pass/fail before full validation
When to Use Full Validation
Recommend full validation when:
- Preparing for publication
- After all quick checks pass
- Need quality scoring
- Want detailed recommendations
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 · 147 lines · 12 tokens per session scan A eba9356bb61c
validate-quick is a command published in the GitHub repository dhofheinz/open-plugins (9 stars, last pushed 6mo ago), licensed MIT. It adds 12 tokens to every session and 732 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.