What is claude-code-plugins CLAUDE.md?

A set of project instructions for maintaining a Claude Code plugin marketplace, including its file layout, naming rules, style, versioning, and steps for adding plugins.

Use it when creating, updating, versioning, or reviewing plugins in the mlz11-cc-marketplace.

It gives coding agents a shared set of rules so marketplace changes follow the expected structure and conventions.

claude-code-plugins CLAUDE.md — Instructions file by mlz11

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/mlz11/claude-code-plugins/claude-md

Clone the repo

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

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

When invoked 479 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.00479	$0.00479
Opus 5	$0.00239	$0.00239
Sonnet 5	$0.00096	$0.00096
Haiku 4.5	$0.00048	$0.00048

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

Security

Grade A, and why

claude-code-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 · 62 lines

What it actually says

CLAUDE.md

This is a Claude Code plugin marketplace owned by mlz11.

Structure

.claude-plugin/marketplace.json   # Marketplace catalog
plugins/<name>/                   # Each plugin is a subdirectory
  .claude-plugin/plugin.json      # Plugin manifest
  skills/<name>/SKILL.md          # Skill definitions
  README.md                       # Plugin-level docs

Style

Never use em dashes (—). Use " - " (spaced hyphen) or parentheses instead.

Conventions

Marketplace name: mlz11-cc-marketplace
Commit messages: conventional commits (feat:, fix:, docs:, etc.) enforced by .githooks/commit-msg
Plugin names: kebab-case
License: MIT
Each plugin must have its own README.md, plugin.json, and at least one skill

Adding a Plugin

Create plugins/<plugin-name>/ with the structure above
Add an entry to .claude-plugin/marketplace.json in the plugins array
Include a README.md with install instructions and usage examples

Versioning

Source of truth: plugin.json version field (semver: x.y.z)
Catalog mirror: marketplace.json includes version for discoverability but plugin.json is authoritative
Both must stay in sync - enforced by .githooks/pre-push
Git tags: <plugin-name>/v<semver> (e.g. swimlanes/v1.2.0)

Bumping a version

./scripts/bump.sh <plugin-name> <major|minor|patch|x.y.z>

This updates both plugin.json and marketplace.json, commits, and creates a git tag in one step.

Validation

./scripts/validate-versions.sh            # all plugins
./scripts/validate-versions.sh swimlanes  # one plugin

Runs automatically on git push via the pre-push hook.

Testing Locally

cc --plugin-dir ./plugins/<plugin-name>

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 · 62 lines · 479 tokens per session scan A ef659237663f

Subscribe to this mod's changes

claude-code-plugins CLAUDE.md is an instructions file published in the GitHub repository mlz11/claude-code-plugins (2 stars, last pushed 6mo ago), licensed MIT. It adds 479 tokens to every session, about $0.0024 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.

claude-code cli developer-tools marketplace plugins

claude-code-plugins CLAUDE.md

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

CLAUDE.md

Structure

Style

Conventions

Adding a Plugin

Versioning

Bumping a version

Validation

Testing Locally

What this file has done since we first saw it

Other instructions, from other repositories

ai-coding-tools AGENTS.md

skills AGENTS.md

claude-code-marketplace CLAUDE.md

claude-skills CLAUDE.md

awesome-claude-plugins CLAUDE.md

claude-plugins CLAUDE.md