Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add poindexter12/waypoint --skill plugin-validatorgit clone --depth 1 https://github.com/poindexter12/waypointWrote 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/skills/poindexter12/waypoint/plugin-validator)<a href="https://agentmods.dev/skills/poindexter12/waypoint/plugin-validator"><img src="https://agentmods.dev/badge/skills/poindexter12/waypoint/plugin-validator/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/skills/poindexter12/waypoint/plugin-validator"><img src="https://agentmods.dev/badge/skills/poindexter12/waypoint/plugin-validator.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.00064 | $0.01371 |
| Opus 5.5 | $0.00026 | $0.00548 |
| Sonnet 5.5 | $0.00013 | $0.00274 |
| Haiku 4.5 | $0.00006 | $0.00137 |
Grade A, and why
plugin-validator 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Validator
Validation Checks
1. Manifest Validation
- plugin.json exists at correct location
- Valid JSON syntax
- Required fields present (name, description, version)
- Semantic versioning format (X.Y.Z)
- Array fields properly formatted (agents, commands, skills)
- No duplicate entries
2. Structure Validation
- Referenced agents exist at specified paths
- Referenced commands exist at specified paths
- Referenced skills exist at specified paths
- File paths are relative (not absolute)
- No broken file references
- Directory structure follows conventions
3. Frontmatter Validation
- YAML syntax is valid
- Required fields present (name, description)
- Field values match allowed types
- Tools list is valid (if specified)
- Model value is valid (sonnet|opus|haiku|inherit)
- No conflicting or deprecated fields
4. Dependency Validation
- No circular dependencies between agents/skills
- Skill references resolve correctly
- Tool permissions are valid
- Cross-references between components exist
- External dependencies documented
5. Configuration Validation
- No conflicting settings between components
- File permissions are readable
- No duplicate agent/command names
- Version consistency across files
- Repository metadata accurate
Process
-
Identify plugin location
# Find plugin.json find . -name "plugin.json" -o -name ".claude-plugin/plugin.json" -
Run manifest validation
- Parse JSON syntax
- Check required fields
- Validate semver format
- Verify array structures
-
Validate file structure
- Read manifest file references
- Check each referenced file exists
- Verify paths are relative
- Check directory conventions
-
Check frontmatter
- For each agent/command file
- Parse YAML frontmatter
- Validate required fields
- Check field value constraints
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 213 lines · 64 tokens per session scan A 8a6b1e11ebae
plugin-validator is a skill published in the GitHub repository poindexter12/waypoint (7 stars, last pushed 9mo ago), licensed MIT. It adds 64 tokens to every session and 1,371 once invoked, about $0.0003 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 skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.