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/charlesjones-dev/claude-code-plugins-dev/claude-mdgit clone --depth 1 https://github.com/charlesjones-dev/claude-code-plugins-devWhat 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.01696 | $0.01696 |
| Opus 5 | $0.00848 | $0.00848 |
| Sonnet 5 | $0.00339 | $0.00339 |
| Haiku 4.5 | $0.00170 | $0.00170 |
Grade A, and why
claude-code-plugins-dev 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.
How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Repository Overview
This is a marketplace for custom Claude Code plugins, skills, and other extensions. The repository follows a structured plugin system where each plugin is self-contained with its own metadata and skills.
Official Documentation
For detailed information about Claude Code plugins, refer to these official documentation resources:
- Plugins: Core concepts and guide for creating and using Claude Code plugins
- Plugins Reference: Technical reference for plugin structure, metadata schemas, and command formats
- Plugin Marketplaces: Guide for creating and managing plugin marketplaces like this repository
These documentation resources provide authoritative information on plugin development best practices, metadata schemas, and marketplace structure that should be consulted when developing new plugins.
Architecture
Marketplace Structure
The repository uses a two-level metadata system:
-
Root marketplace manifest (
.claude-plugin/marketplace.json): Central registry that defines:- Marketplace owner and metadata
- List of all available plugins with their source paths, descriptions, and categories
- Plugin root directory location (
./plugins)
-
Individual plugin manifests (
plugins/{plugin-name}/.claude-plugin/plugin.json): Each plugin has its own metadata including name, version, description, author, and license.
Plugin Organization
Plugins are organized under the plugins/ directory:
plugins/
{plugin-name}/
.claude-plugin/
plugin.json # Plugin metadata
skills/
{skill-name}/
SKILL.md # Skill implementation
agents/ # Optional
{agent-name}.md # Subagent definition
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 · 165 lines · 1,696 tokens per session scan A 57ccbe0b5ff8
claude-code-plugins-dev CLAUDE.md is an instructions file published in the GitHub repository charlesjones-dev/claude-code-plugins-dev (34 stars, last pushed 1mo ago), licensed MIT. It adds 1,696 tokens to every session, about $0.0085 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 instructions, from other repositories
gwm-cli AGENTS.md
Instructions for kbrdn1/gwm-cli, covering gwm-cli — house rules for ai assistants, 🔴 primordial rule — test-driven development is mandatory, the tdd loop (red → green → refactor), what counts as "behaviour" and exceptions (narrow, must be argued in the pr description).
gwm-cli CLAUDE.md
Instructions for kbrdn1/gwm-cli, covering gwm-cli — house rules for ai assistants, 🔴 primordial rule — test-driven development is mandatory, the tdd loop (red → green → refactor), what counts as "behaviour" and exceptions (narrow, must be argued in the pr description).
geminicli-git-tools-extension GEMINI.md
Instructions for paufortiana/geminicli-git-tools-extension, covering git tools extension, commands and standards.
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.
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).