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 vinnie357/claude-skills/plugin install claude-codeWrote 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/vinnie357/claude-skills/plugin-marketplace)<a href="https://agentmods.dev/skills/vinnie357/claude-skills/plugin-marketplace"><img src="https://agentmods.dev/badge/skills/vinnie357/claude-skills/plugin-marketplace/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/vinnie357/claude-skills/plugin-marketplace"><img src="https://agentmods.dev/badge/skills/vinnie357/claude-skills/plugin-marketplace.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.00029 | $0.01706 |
| Opus 5 | $0.00015 | $0.00853 |
| Sonnet 5 | $0.00006 | $0.00341 |
| Haiku 4.5 | $0.00003 | $0.00171 |
Grade A, and why
plugin-marketplace 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 6d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Plugin Marketplace
Guide for creating, validating, and managing plugin marketplaces for Claude Code.
Per core:anti-fabrication: verify schema fields and source paths with the validation scripts before claiming an entry is valid — never assert validation results without running them. The validator names the offending field and value; that output is the authority, not this page.
Marketplace schema
A marketplace lives at .claude-plugin/marketplace.json in the repository root.
Required: name (kebab-case), owner (object; name required, email optional), plugins (array, may be empty).
Optional metadata: description, version, and pluginRoot — a base directory that relative plugin source paths resolve against.
Plugin entry schema
Plugin entries use the plugin manifest schema with every field optional, plus the marketplace-only fields source, strict, category, and tags. Any field valid in a plugin.json is therefore valid in an entry — see /claude-code:claude-plugins for the manifest schema and for which fields must never appear in a plugin.json.
Each entry requires name (kebab-case) and source. Beyond those:
- Metadata:
description,version,author,homepage,repository,license(SPDX),keywords,category,tags - Component paths:
commands,agents,hooks,mcpServers,skills - Dependencies:
dependencies, an array of"namespace:plugin-name"strings
Strict mode
strict defaults to true.
true— the plugin must ship its ownplugin.json; marketplace fields supplement it.false— the marketplace entry is the complete manifest; noplugin.jsonneeded.
Choose strict: false for simple self-contained plugins whose configuration all lives in marketplace.json, when centralized management is the goal and the plugin is unlikely to be distributed independently.
Choose strict: true when the plugin has complex configuration, may be distributed separately, has its own versioning lifecycle, or when the marketplace is only adding metadata to a manifest that already exists.
What ships with it
8 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.
- references/marketplace-examples.md 2.2 KB
- references/schema-specification.md 6.4 KB
- references/validation-and-troubleshooting.md 4.6 KB
- scripts/analyze-plugins.nu 2.5 KB
- scripts/format-marketplace.nu 1.3 KB
- scripts/init-marketplace.nu 1.5 KB
- scripts/validate-dependencies.nu 3.1 KB
- scripts/validate-marketplace.nu 18 KB
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.
- 6d ago First seen · 128 lines · 29 tokens per session scan A 65db1aa827cb
plugin-marketplace is a skill published in the GitHub repository vinnie357/claude-skills (25 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 1,706 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-03.
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…
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…
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…