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/zate/cc-plugins/claude-mdgit clone --depth 1 https://github.com/Zate/cc-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.05747 | $0.05747 |
| Opus 5 | $0.02874 | $0.02874 |
| Sonnet 5 | $0.01149 | $0.01149 |
| Haiku 4.5 | $0.00575 | $0.00575 |
Grade A, and why
cc-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.
How it starts
The opening of the file, as written. The whole thing — 658 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Plugin Marketplace - Developer Guide
This repository is a marketplace for Claude Code plugins. This document provides guidance for agents working in this codebase on how to build, structure, and contribute plugins.
Table of Contents
- Repository Structure
- Official Plugin Structure
- Plugin Development Guidelines
- Development Workflow
- Recommended Workflow Pattern (devloop)
- Command Orchestration Pattern
- .devloop/ Directory Structure
- Key Principles
- Marketplace Structure
- Versioning Guidelines
Repository Structure
cc-plugins/
├── .claude-plugin/
│ └── marketplace.json # Marketplace configuration (required)
├── plugins/ # Individual plugin directories
├── templates/ # Templates for creating new plugins
├── docs/ # Additional documentation
├── CLAUDE.md # This file - guidance for agents
├── CONTRIBUTING.md # Contribution guidelines
└── README.md # Public-facing marketplace documentation
Official Plugin Structure
Each plugin MUST follow this structure:
plugin-name/
├── .claude-plugin/
│ └── plugin.json # Required manifest file
├── agents/ # Optional: Agent definitions (.md files)
├── skills/ # Optional: Skills and commands (subdirs with SKILL.md)
├── hooks/ # Optional: Event handlers
├── .mcp.json # Optional: MCP server configuration
├── .lsp.json # Optional: LSP server configuration
├── settings.json # Optional: Plugin default settings
└── README.md # Plugin documentation
Note: commands/ is legacy. Both commands/deploy.md and skills/deploy/SKILL.md create /deploy. Use skills/ for new development.
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 · 658 lines · 5,747 tokens per session scan A 7296f5f7b588
cc-plugins CLAUDE.md is an instructions file published in the GitHub repository Zate/cc-plugins (10 stars, last pushed 1mo ago), licensed MIT. It adds 5,747 tokens to every session, about $0.0287 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
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.
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).
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.