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/lexfrei/ccc/claude-mdgit clone --depth 1 https://github.com/lexfrei/cccWhat 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.00959 | $0.00959 |
| Opus 5 | $0.00479 | $0.00479 |
| Sonnet 5 | $0.00192 | $0.00192 |
| Haiku 4.5 | $0.00096 | $0.00096 |
Grade A, and why
ccc 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 — 41 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.
What This Is
Claude Code Companions (CCC) — an external marketplace repository for Claude Code plugins. It contains no application code; only plugin definitions (agents, skills, MCP servers) distributed via the Claude Code plugin marketplace system.
Repository Structure
Top-level directories group plugins by their primary component type, and one plugin may ship several types. There is no top-level agents/ directory: agents are always a directory inside a plugin, so a plugin that ships only agents lives under skills/ as well.
skills/— Skill definitions (markdown prompts inskills/<name>/skills/<skill>/SKILL.md, metadata inskills/<name>/.claude-plugin/plugin.json). A single skill plugin can bundle multiple skills (e.g.,review-toolkitcontainsbranch-review,pr-review), and it can also ship agents inskills/<name>/agents/<agent>.md—becomebundles a set of specialist agents next to its roles. Claude Code scans that directory automaticallymcp/— MCP server definitions (server config inmcp/<name>/.mcp.json, metadata inmcp/<name>/.claude-plugin/plugin.json)hooks/— Hook plugins (hook config inhooks/<name>/hooks/hooks.json, scripts inhooks/<name>/scripts/, metadata inhooks/<name>/.claude-plugin/plugin.json)
The marketplace registry is .claude-plugin/marketplace.json — it indexes all plugins with names, descriptions, source paths, and categories.
Adding a New Plugin
- Create the directory under the appropriate type (
skills/,mcp/, orhooks/) - Add
.claude-plugin/plugin.jsonwith name, version, description, author - Add the content file(s):
skills/<skill>/SKILL.mdfor skills,agents/<agent>.mdfor agents,.mcp.jsonfor MCP servers,hooks/hooks.json+ scripts for hooks — all relative to the plugin root - Add a
README.mdin the plugin directory: what the plugin does, installation commands, a section per bundled skill/agent, and how to extend it if applicable (convention applies to new plugins; older plugins are backfilled opportunistically) - Register the plugin in
.claude-plugin/marketplace.jsonunder thepluginsarray - Update
README.mdto include the new plugin in the appropriate table
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 · 41 lines · 959 tokens per session scan A 266ecbffb1c8
ccc CLAUDE.md is an instructions file published in the GitHub repository lexfrei/ccc (9 stars, last pushed 3d ago), licensed BSD-3-Clause. It adds 959 tokens to every session, about $0.0048 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.