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 agentmods add instructions/bgreenwell/claude-plugins/claude-mdgit clone --depth 1 https://github.com/bgreenwell/claude-pluginsWrote 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/instructions/bgreenwell/claude-plugins/claude-md)<a href="https://agentmods.dev/instructions/bgreenwell/claude-plugins/claude-md"><img src="https://agentmods.dev/badge/instructions/bgreenwell/claude-plugins/claude-md.svg" alt="Measured on agentmods" 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 | $0.01412 | $0.01412 |
| Opus 5 | $0.00706 | $0.00706 |
| Sonnet 5 | $0.00282 | $0.00282 |
| Haiku 4.5 | $0.00141 | $0.00141 |
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 3d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Context for Claude Code when working with this repository.
What This Repository Is
This is a Claude Code plugin marketplace - a distribution point for Claude Code plugins. The repository structure follows the official plugin marketplace specification.
Owner: Brandon Greenwell ([email protected])
Distribution: GitHub (bgreenwell/claude-plugins)
Repository Structure
claude-plugins/
├── .claude-plugin/
│ └── marketplace.json # Marketplace catalog (CRITICAL)
└── [plugin-name]/ # Each plugin in its own directory
├── .claude-plugin/
│ └── plugin.json # Plugin metadata
├── skills/ # Skills (markdown with YAML frontmatter)
│ └── skill-name.md
├── commands/ # Slash commands (optional)
├── agents/ # Specialized agents (optional)
├── hooks/ # Lifecycle hooks (optional)
└── README.md # User documentation
Important: Each plugin is a top-level directory. Check .claude-plugin/marketplace.json for the complete list.
Critical Files
.claude-plugin/marketplace.json
The marketplace catalog. This file:
- Must use valid JSON syntax
- Lists all plugins in the
pluginsarray - Must validate with
cforge validatebefore commits - Uses kebab-case for names
Per-Plugin Files
Required:
.claude-plugin/plugin.json- Plugin metadata and component referencesREADME.md- User-facing documentation
Component Directories (create as needed):
skills/- Skills that teach Claude how to use external tools (markdown with YAML frontmatter)commands/- Slash commands for users (markdown with YAML frontmatter)agents/- Specialized sub-agents with specific capabilities (markdown with YAML frontmatter)hooks/- Lifecycle event handlers (shell scripts)
Common Development Tasks
Adding a New Plugin
Recommended: Use claude-forge CLI
cd /path/to/claude-plugins
cforge new-plugin --name plugin-name --description "Plugin description"
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.
- 3d ago First seen · 172 lines · 1,412 tokens per session scan A 67332213227c
claude-plugins CLAUDE.md is an instructions file published in the GitHub repository bgreenwell/claude-plugins (2 stars, last pushed 8mo ago), licensed MIT. It adds 1,412 tokens to every session, about $0.0071 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.
Other instructions, from other repositories
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).
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.