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 davistroy/claude-marketplace/plugin install personal-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/davistroy/claude-marketplace/validate-plugin)<a href="https://agentmods.dev/commands/davistroy/claude-marketplace/validate-plugin"><img src="https://agentmods.dev/badge/commands/davistroy/claude-marketplace/validate-plugin.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.00021 | $0.05281 |
| Opus 5 | $0.00010 | $0.02641 |
| Sonnet 5 | $0.00004 | $0.01056 |
| Haiku 4.5 | $0.00002 | $0.00528 |
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 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.
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 — 481 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate Plugin Command
Perform comprehensive validation of a plugin's structure, frontmatter, version synchronization, and content quality. Use this command before committing changes to catch common errors.
Input Validation
Required Arguments:
<plugin-name>- Name of the plugin to validate (must match a subdirectory inplugins/that contains.claude-plugin/plugin.json)
Optional Arguments:
--all- Validate all plugins in the repository--fix- Attempt to auto-fix simple issues (formatting, missing fields)--verbose- Show detailed output for all checks (not just failures)--strict- Fail on any pattern violation (treats warnings as errors)--report- Generate detailed compliance report toreports/validation-[timestamp].md--scorecard- Generate maturity scorecard for plugins (see Maturity Scorecard section)--check-updates- Check for available plugin updates by comparing local vs remote marketplace versions
Validation: If required arguments are missing, display the usage message: the full flag list, the eight example invocations, and the dynamically-discovered plugin list. If plugin-name is not found (and --all not specified), display an error naming the missing plugin plus the same discovered plugin list and a hint to use --all. See references/validate-plugin-examples.md for the exact text of both messages.
Plugin Discovery: Use the Glob tool to scan plugins/*/.claude-plugin/plugin.json. Each match yields a valid plugin name from the directory path. If no plugins are found, report: "Error: No plugins found in the plugins/ directory."
--all Flag Behavior: When --all is specified, scan plugins/ for all subdirectories containing .claude-plugin/plugin.json and validate each one. Do NOT rely on a hardcoded list of plugin names.
Instructions
Phase 1: Structure Validation
Verify the plugin has the required directory structure and files.
1.1 Required Files Check
Check for plugin.json (required); at least one of commands/ (flat *.md files, filename becomes command name) or skills/ (nested [skill-name]/SKILL.md directories, uppercase filename required). See references/validate-plugin-examples.md for the required directory structure diagram.
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 · 481 lines · 21 tokens per session scan A 550241d11fba
validate-plugin is a command published in the GitHub repository davistroy/claude-marketplace (5 stars, last pushed 5d ago), licensed MIT. It adds 21 tokens to every session and 5,281 once invoked, about $0.0001 per session on Opus 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-09-04.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.