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 sean-sunagaku/claude-code-plugin --skill marketplace-validategit clone --depth 1 https://github.com/sean-sunagaku/claude-code-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/skills/sean-sunagaku/claude-code-plugin/marketplace-validate)<a href="https://agentmods.dev/skills/sean-sunagaku/claude-code-plugin/marketplace-validate"><img src="https://agentmods.dev/badge/skills/sean-sunagaku/claude-code-plugin/marketplace-validate/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/sean-sunagaku/claude-code-plugin/marketplace-validate"><img src="https://agentmods.dev/badge/skills/sean-sunagaku/claude-code-plugin/marketplace-validate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00181 | $0.01273 |
| Opus 5 | $0.00090 | $0.00636 |
| Sonnet 5 | $0.00036 | $0.00255 |
| Haiku 4.5 | $0.00018 | $0.00127 |
Grade A, and why
marketplace-validate 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 9d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Marketplace Validate
claude-code-plugin リポジトリの構造を検証し、エラーを自動修正する。
対象リポジトリ
PLUGIN_REPO=/Users/babashunsuke/Repository/claude-code-plugin
VALIDATE_SCRIPT=$PLUGIN_REPO/.github/scripts/validate-marketplace.sh
FIX_SCRIPT=scripts/fix-marketplace.sh
スキーマ制約（重要）
plugins[] エントリで許可されるキーは以下の 6 つのみ:
name, source, description, version, author, keywords
それ以外のキー（例: "status", "type" 等）を追加すると Claude Code がプラグインを読み込めなくなる。
Beta スキルの表現は description に [Beta] プレフィックスを付けることで行う（専用フィールドは使わない）。
チェック項目
| # | チェック | 対象 |
|---|---|---|
| 1 | marketplace.json が valid JSON | .claude-plugin/marketplace.json |
| 2 | 必須フィールド (name, version, description, owner) | marketplace.json トップレベル |
| 3 | 各プラグインの skill ディレクトリが存在 | <source>/skills/<name>/ |
| 4 | SKILL.md が存在し frontmatter に name/description がある | 各スキル |
| 5 | .claude-plugin/plugin.json が存在し name が一致 |
各スキル |
| 6 | agents/ の各 .md に name/description frontmatter がある | Agent Team 型スキル |
| 7 | references/ のファイルが SKILL.md から参照されている | 各スキル |
| 8 | ディスク上に存在するが marketplace.json に未登録のスキル | 全体 |
| 9 | plugins[] エントリに不正キーがないか | 各プラグイン |
ワークフロー
Step 1: Claude Code CLI でスキーマ検証
claude plugin validate .
Validation passed になることを確認。失敗したら出力のエラー内容を修正する。
Step 2: 構造バリデーション実行
bash $PLUGIN_REPO/.github/scripts/validate-marketplace.sh
出力の ERROR: と WARN: を確認する。
Step 3: 自動修正
エラーがあれば fix スクリプトを実行:
# dry-run で修正内容を確認
bash scripts/fix-marketplace.sh --dry-run
# 実際に修正
bash scripts/fix-marketplace.sh
fix スクリプトが自動修正するもの:
- missing plugin.json:
~/.claude/skills/<name>/にあればコピー、なければ marketplace.json から生成 - plugin.json name 不一致: marketplace.json の name に合わせて修正
- version 不一致: plugin.json の version を正として marketplace.json を更新
- 不正キーの削除: スキーマで許可されていないキーを自動削除
- orphaned entries: ディレクトリが存在しない marketplace.json エントリを削除
- unregistered skills: ディスク上にあるが未登録のスキルを報告（手動対応）
Step 4: 再バリデーション
修正後に再度バリデーションを実行し、全て PASSED になることを確認:
claude plugin validate .
bash $PLUGIN_REPO/.github/scripts/validate-marketplace.sh
What ships with it
1 file 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.
- 9d ago First seen · 124 lines · 181 tokens per session scan A 28dfcf514df1
marketplace-validate is a skill published in the GitHub repository sean-sunagaku/claude-code-plugin (36 stars, last pushed 1mo ago), licensed MIT. It adds 181 tokens to every session and 1,273 once invoked, about $0.0009 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…