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/dropfan/claude-code-plugins/claude-mdgit clone --depth 1 https://github.com/DropFan/claude-code-pluginsWhat 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.00775 | $0.00775 |
| Opus 5 | $0.00387 | $0.00387 |
| Sonnet 5 | $0.00155 | $0.00155 |
| Haiku 4.5 | $0.00077 | $0.00077 |
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 yesterday.
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.
This is a copy
91% identical to claude-code-plugins AGENTS.md — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Plugins Collection
This is a Claude Code plugin marketplace repository.
Repository Structure
.claude-plugin/
marketplace.json # Marketplace manifest, declares all available plugins
plugins/
<plugin-name>/ # Self-developed plugin directory
.claude-plugin/
plugin.json # Plugin metadata
commands/ # User-invokable slash commands
agents/ # Subagent definitions
skills/ # Skill modules
hooks/ # Hook configurations
scripts/
sync-plugins.sh # Sync plugin.json metadata to marketplace.json and README.md
validate-plugins.sh # Validate plugin structure and metadata (plugin.json, frontmatter, naming)
verify-sync.sh # Detect drift between plugin.json and marketplace.json (--run-sync to fix)
lark-rebuild.py # Rebuild the lark plugin from lark-cli skill sources
tests/
run-tests.sh # Automated test runner
*-manual-tests.md # Manual test checklists per plugin
.github/workflows/
ci.yml # CI: validate-plugins + verify-sync + tests
Plugin Management
- Self-developed plugins — Source code lives directly under
plugins/<name>/ - Curated plugins — Referenced in
marketplace.jsonvia GitHub source pointing to external repos
Development Guidelines
Adding a Self-developed Plugin
- Create a plugin directory under
plugins/ - Create
.claude-plugin/plugin.jsonwith metadata (this is the single source of truth) - Add an entry to the
pluginsarray inmarketplace.jsonwith a relative path as source - Run
bash scripts/sync-plugins.shto auto-sync metadata tomarketplace.jsonandREADME.md
Note:
plugin.jsonis the single source of truth for self-developed plugins. Do NOT manually edit plugin metadata inmarketplace.jsonorREADME.md— run the sync script instead. The sync covers thedescription,version,author,keywords, andlicensefields; other fields are not propagated.
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.
- yesterday First seen · 87 lines · 775 tokens per session scan A 21c59e955a58
claude-code-plugins CLAUDE.md is an instructions file published in the GitHub repository DropFan/claude-code-plugins (7 stars, last pushed 26d ago), licensed MIT. It adds 775 tokens to every session, about $0.0039 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to claude-code-plugins AGENTS.md, differing in 2 lines, and is treated as a copy.
Other instructions, from other repositories
moo.md CLAUDE.md
Instructions for saadshahd/moo.md, covering claude.md, what this is, conventions, philosophy and model-judgment boundaries.
director-mode-lite copilot-instructions.md
Instructions for claude-world/director-mode-lite: This is a Shell/Markdown toolkit for Claude Code Director Mode. Keep shell scripts POSIX-compatible where possible. Markdown files are the primary deliverable.
Codelens-AI CLAUDE.md
Instructions for Akshat2634/Codelens-AI, covering claude.md — codelens-ai, project overview, tech stack, project structure and data flow.
agents-plugins AGENTS.md
Instructions for CitiesSkylinesModding/agents-plugins, covering agents.md, project overview, tech stack, repository structure and commands.
dotclaude CLAUDE.md
Instructions for JHostalek/dotclaude: Treat these instructions as binding user-level invariants, not suggestions or style preferences.
codeframe AGENTS.md
AGENTS.md instructions for frankbria/codeframe: The guidelines for this repo live in CLAUDE.md. Read that file.