Borrowing it
Nothing to install: this file belongs to tmchow/tmc-marketplace. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tmchow/tmc-marketplace/main/.claude/skills/validate-plugin/SKILL.mdgit clone --depth 1 https://github.com/tmchow/tmc-marketplaceWrote 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/tmchow/tmc-marketplace/validate-plugin)<a href="https://agentmods.dev/skills/tmchow/tmc-marketplace/validate-plugin"><img src="https://agentmods.dev/badge/skills/tmchow/tmc-marketplace/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/skills/tmchow/tmc-marketplace/validate-plugin"><img src="https://agentmods.dev/badge/skills/tmchow/tmc-marketplace/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.00634 |
| Opus 5.5 | $0.00004 | $0.00254 |
| Sonnet 5.5 | $0.00002 | $0.00127 |
| Haiku 4.5 | $0.00001 | $0.00063 |
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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Validator
Validate a plugin meets marketplace requirements before publishing.
Usage
/validate-plugin <plugin-name>
Or validate all plugins:
/validate-plugin --all
Validation Checks
1. Plugin Structure
# Check required files exist
ls plugins/<plugin-name>/.claude-plugin/plugin.json
ls plugins/<plugin-name>/README.md
ls plugins/<plugin-name>/skills/ # At least skills/ or agents/ must exist
2. plugin.json Validation
Required fields:
name- must match directory nameversion- semver format (e.g., "0.1.0")description- non-empty stringauthor.name- non-empty stringskills- path to skills directory (if skills exist)agents- path to agents directory (if agents exist)
# Validate JSON syntax
cat plugins/<plugin-name>/.claude-plugin/plugin.json | jq .
3. Skill Validation
For each plugins/<plugin-name>/skills/*/SKILL.md:
Required frontmatter:
---
name: skill-name # Required
description: ... # Required - when Claude should use this
---
Optional frontmatter:
disable-model-invocation: true # User-only skill
user-invocable: false # Claude-only skill
Check: Frontmatter must be valid YAML between --- markers
4. Agent Validation
For each plugins/<plugin-name>/agents/*/AGENT.md:
Required frontmatter:
---
name: agent-name # Required
description: ... # Required - when Claude should use this agent
---
5. Marketplace Registry
Check .claude-plugin/marketplace.json contains entry:
{
"plugins": [
{
"name": "<plugin-name>",
"source": "./plugins/<plugin-name>",
"description": "...",
"version": "..."
}
]
}
6. No Deprecated Commands
Verify no commands/ directory exists (commands merged into skills in Claude Code 2.1.3+)
Output Format
Validating plugin: <plugin-name>
[PASS] Plugin structure valid
[PASS] plugin.json valid
[PASS] 2 skills validated
[WARN] No agents defined (optional)
[PASS] Marketplace entry found
[PASS] No deprecated commands
Result: VALID (5 passed, 1 warning, 0 errors)
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 · 125 lines · 11 tokens per session scan A f0491b6e03c9
validate-plugin is a skill published in the GitHub repository tmchow/tmc-marketplace (22 stars, last pushed 7mo ago), licensed MIT. It adds 11 tokens to every session and 634 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-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…