Borrowing it
Nothing to install: this file belongs to musingfox/cc-plugins. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/musingfox/cc-plugins/main/CLAUDE.mdgit clone --depth 1 https://github.com/musingfox/cc-pluginsWrote 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/musingfox/cc-plugins/claude-md)<a href="https://agentmods.dev/instructions/musingfox/cc-plugins/claude-md"><img src="https://agentmods.dev/badge/instructions/musingfox/cc-plugins/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/musingfox/cc-plugins/claude-md"><img src="https://agentmods.dev/badge/instructions/musingfox/cc-plugins/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00556 | $0.00556 |
| Opus 5.5 | $0.00222 | $0.00222 |
| Sonnet 5.5 | $0.00111 | $0.00111 |
| Haiku 4.5 | $0.00056 | $0.00056 |
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 1mo 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Claude Code Plugin Marketplace — multiple independent plugins. Plugin list lives in .claude-plugin/marketplace.json.
Plugin / marketplace spec, component structure, and frontmatter fields follow the official Claude Code documentation — do not hard-code conventions here; consult the docs when in doubt.
Adding / Modifying a Plugin
- Follow the official plugin structure; write
.claude-plugin/plugin.json. - Add entry to root
.claude-plugin/marketplace.json. - Keep root
README.mdin sync (plugin listing, install commands).
The hooks below live in .githooks/. Setup once per clone:
git config core.hooksPath .githooks
Commit Messages
.githooks/commit-msg enforces Conventional Commits on the subject:
<type>[(scope)][!]: <description>. The plugin name is a scope, not a type —
feat(spiral):, not spiral:. fixup! / squash! and git's own merge and revert
subjects pass through. Commits made before the hook do not conform; leave them alone.
Version Management
Claude Code uses plugin.json version to detect updates — no bump → no cache refresh.
.githooks/pre-commit auto-bumps the patch version for every plugin whose content is
in the commit, once per unpushed batch: it compares against the last pushed state, so a
stack of commits before a push costs one bump per plugin, and --amend / fixup! never
bump twice. The bump lands in the same commit, so one git push ships it.
Manual minor/major bump: edit plugin.json version and commit it — the hook skips any
plugin whose version already differs from the pushed one.
.githooks/pre-push only guards: it refuses a push where a plugin's content changed but
its version did not (a commit made with --no-verify or from a clone without
core.hooksPath). .githooks/post-commit re-stages the bumped manifest after a
git commit <pathspec>, which otherwise leaves the real index on the old version.
A slash command runs the installed copy, not this working tree, so a plugin edited here
is not what /<plugin>:<command> loads in the session that edited it. To exercise the change
now, drive the workflow from the working-tree file by hand; to exercise it as a command, push,
reinstall, and start a fresh session.
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.
- 1mo ago Changed · +4 lines · +110 tokens per session f51987027757
- 1mo ago Changed · +14 lines · +184 tokens per session 765af1835f3b
- 1mo ago Changed · +5 lines · +56 tokens per session ef2f786311ed
- 1mo ago First seen · 24 lines · 206 tokens per session scan A f0c97975a86d
cc-plugins CLAUDE.md is an instructions file published in the GitHub repository musingfox/cc-plugins (2 stars, last pushed yesterday), licensed MIT. It adds 556 tokens to every session, about $0.0022 per session on Opus 5.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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).