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/clever-cc-plugins/cc-config/claude-mdgit clone --depth 1 https://github.com/clever-cc-plugins/cc-configWrote 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/clever-cc-plugins/cc-config/claude-md)<a href="https://agentmods.dev/instructions/clever-cc-plugins/cc-config/claude-md"><img src="https://agentmods.dev/badge/instructions/clever-cc-plugins/cc-config/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.00731 | $0.00731 |
| Opus 5 | $0.00365 | $0.00365 |
| Sonnet 5 | $0.00146 | $0.00146 |
| Haiku 4.5 | $0.00073 | $0.00073 |
Grade A, and why
cc-config 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cc-config
Reusable Claude Code skills for configuration management, distributed as a Claude Code plugin. Install via the plugin system (see README).
Key Config Files
| File | Purpose |
|---|---|
.claude/format-markdown.sh |
PostToolUse hook: formats Markdown files with prettier after edits |
.claude/guard-secret-files.sh |
PreToolUse hook: blocks reads/edits/writes of secret .env files |
.claudeignore |
Paths excluded from Claude Code indexing |
CLAUDE.md |
Project instructions, loaded every message |
.claude/settings.json |
Permissions, hooks, environment variables |
.githooks/pre-commit |
Secret scanning (gitleaks) + CLAUDE.md table sync |
.github/workflows/claude-code-review.yml |
Automatic PR review via Claude Code |
.github/workflows/claude.yml |
Trigger Claude via @claude mentions in issues/PRs |
.github/workflows/release.yml |
Triggers shared plugin-release workflow — version bump + GitHub release — on push to main |
.gitignore |
Git ignore patterns |
plugins/cc-config/.claude-plugin/plugin.json |
Plugin manifest for the cc-config plugin |
plugins/cc-config/hooks/auto-git-pull.sh |
SessionStart hook: opt-in fetch + fast-forward pull at session start (CC_CONFIG_AUTO_GIT_PULL) |
plugins/cc-config/hooks/check-optimize-staleness.sh |
SessionStart hook: nudges to run /auditing-config when a project has drifted since its last audit |
plugins/cc-config/hooks/hooks.json |
Declares the bundled SessionStart hooks so they apply in any project the plugin is active in |
plugins/cc-config/skills/auditing-config/SKILL.md |
Skill: Audit and optimize an existing Claude Code configuration |
plugins/cc-config/skills/bootstrapping-config/SKILL.md |
Skill: Bootstrap a best-practice Claude Code config for a new project |
scripts/sync-config-table.sh |
Keeps Key Config Files table in sync on each commit |
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 · 55 lines · 731 tokens per session scan A 26fec98af6d2
cc-config CLAUDE.md is an instructions file published in the GitHub repository clever-cc-plugins/cc-config (1 stars, last pushed 8d ago), licensed MIT. It adds 731 tokens to every session, about $0.0037 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
cc-content CLAUDE.md
Claude Code instructions for clever-cc-plugins/cc-content, covering cc-content, key config files, plugin structure, skills and don't.
dev-agent-skills CLAUDE.md
Instructions for fvadicamo/dev-agent-skills, covering claude.md, project overview, architecture, key file: marketplace.json and skill anatomy.
recursive-decomposition-skill AGENTS.md
Instructions for massimodeluisa/recursive-decomposition-skill, covering agents: recursive-decomposition skill, read these first (mandatory), language policy, non-negotiables and commands.
qa-orchestra CLAUDE.md
Claude Code instructions for Anasss/qa-orchestra, covering qa orchestra — claude code instructions, what this project is, quick start, 1. clone into your workspace and 2. fill in your project context.
the-foundry AGENTS.md
AGENTS.md instructions for attac-t/the-foundry, covering the foundry, doctrine and rules.
swarms CLAUDE.md
Instructions for DheerG/swarms, a project described as: Achieve extraordinary results with claude code across a variety of tasks.