What is claude-plugins CLAUDE.md?

Instructions for maintaining a Claude Code plugin marketplace, including its marketplace file, plugin folders, validation commands, and repository conventions.

Use them when creating or updating plugins, editing marketplace.json, validating a plugin, or linting the repository's Markdown and plugin files.

They provide a consistent structure for adding plugins and checking that the marketplace and its documentation are valid.

claude-plugins CLAUDE.md — Instructions file by cblecker

Install

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.

agentmods

npx agentmods add instructions/cblecker/claude-plugins/claude-md

Clone the repo

git clone --depth 1 https://github.com/cblecker/claude-plugins

Per session 710 This file is loaded in full into every session.

When invoked 710 The same file — it is already loaded in full.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00710	$0.00710
Opus 5	$0.00355	$0.00355
Sonnet 5	$0.00142	$0.00142
Haiku 4.5	$0.00071	$0.00071

Measured 2d ago against content hash 01feb8433efe, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

claude-plugins CLAUDE.md 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.

CLAUDE.md · 68 lines

How it starts

The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

Personal Claude Code plugin marketplace

Architecture

.
├── .claude-plugin/
│   └── marketplace.json      # Marketplace manifest (lists all plugins)
├── git/                       # Custom plugin: git workflows & safety
├── github/                    # MCP wrapper: GitHub tools
├── gws/                       # Custom plugin: Google Workspace CLI skills
├── pr-review-toolkit/         # Custom plugin: PR review workflow
└── CLAUDE.md

Each plugin directory contains .claude-plugin/plugin.json and its own components (skills, hooks, agents, MCP configs). Plugins are at the repository root in a flat structure.

Commands

Command	Purpose
`claude plugin validate .`	Validate marketplace
`claude plugin validate ./<plugin-name>`	Validate specific plugin
`npx markdownlint-cli2 --config ${CLAUDE_PROJECT_DIR}/.markdownlint-cli2.jsonc "*/.md"`	Lint markdown files
`uvx skillsaw --strict`	Lint plugin

Adding a Plugin

Create plugin directory at repository root using /plugin-dev:create-plugin

Add entry to .claude-plugin/marketplace.json:

{"name": "plugin-name", "source": "./plugin-name", "strict": true}

Update README.md Available Plugins table
Validate: claude plugin validate . and claude plugin validate ./<plugin-name>

Conventions

Use kebab-case for all names
Use ${CLAUDE_PLUGIN_ROOT} for portable paths in hooks/MCP configs
When editing plugin files (other than README.md or CLAUDE.md), bump the version in that plugin's .claude-plugin/plugin.json following semver:
- patch: bug fixes, typo corrections, minor wording changes
- minor: new skills, commands, hooks, agents, or backward-compatible behavior changes
- major: breaking changes (renamed/removed skills, changed hook behavior, restructured plugin)
Only bump once per PR branch. Before bumping, check git diff main -- <plugin>/.claude-plugin/plugin.json to see if the version was already bumped. Skip if it was, unless the accumulated changes now warrant a higher semver level (e.g., patch already bumped but a new skill was added — upgrade to minor)
Use plugin-dev skills: /plugin-dev:create-plugin, /plugin-dev:skill-reviewer, /plugin-dev:plugin-validator
CodeRabbit auto-review is disabled (reviews.auto_review.enabled: false in .coderabbit.yaml). Reviews are rate-limited, so request one manually with an @coderabbitai review comment only when the branch is ready — not after every push
When addressing automated review feedback on a PR (Copilot, CodeRabbit): wait until every reviewer has finished reviewing the current head, then push fixes for all findings as a single commit — one push per review round, not one per reviewer

Read the full file on GitHub · 68 lines

Changes

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 · 68 lines · 710 tokens per session scan A 01feb8433efe

Subscribe to this mod's changes

claude-plugins CLAUDE.md is an instructions file published in the GitHub repository cblecker/claude-plugins (5 stars, last pushed 5d ago), licensed Apache-2.0. It adds 710 tokens to every session, about $0.0036 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-31.

Planning

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

claude-plugins CLAUDE.md