Borrowing it
Nothing to install: this file belongs to smk-labs/claude-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/smk-labs/claude-plugins/main/CLAUDE.mdgit clone --depth 1 https://github.com/smk-labs/claude-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/smk-labs/claude-plugins/claude-md)<a href="https://agentmods.dev/instructions/smk-labs/claude-plugins/claude-md"><img src="https://agentmods.dev/badge/instructions/smk-labs/claude-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/smk-labs/claude-plugins/claude-md"><img src="https://agentmods.dev/badge/instructions/smk-labs/claude-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.00787 | $0.00787 |
| Opus 5.5 | $0.00315 | $0.00315 |
| Sonnet 5.5 | $0.00157 | $0.00157 |
| Haiku 4.5 | $0.00079 | $0.00079 |
Grade A, and why
claude-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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
claude-plugins
The marketplace repo for my plugins. One plugin per folder at the repo root, listed once in .claude-plugin/marketplace.json. There is no plugins/ directory, and a path that assumes one 404s silently: readable's CDN line carried @main/plugins/readable/assets/rc.css for a year and only ever showed up as an unstyled card.
One source, always the remote
Every machine and every Claude surface installs these plugins from the remote marketplace, https://github.com/smk-labs/claude-plugins.git. A second copy anywhere means two versions, and the stale one wins half the time.
So never leave any of these behind:
- a skill copied into
~/.claude/skills/<name>/or a command into~/.claude/commands/<name>.mdwhen a plugin here already ships it - a marketplace registered with
source: directorypointing at this checkout claude plugin installfrom a local path- a dev override in the Claude desktop config (for readable, an
mcpServers.readable-cardentry whose path points into this checkout instead of~/.claude/plugins/data/readable/server/server.js)
A plugin here MAY register itself with the desktop app on first session, because installing a plugin should be the whole setup. readable does. But an auto-write earns that only by satisfying all four of these, and readable's hooks/connect.sh is the worked example plus the tests:
- every profile, not one. A hook that knows a single config path leaves the other profiles diverged, which is what drives people to hand-copy whole configs between profiles and spread live API tokens doing it.
- one backup per config, ever. Not one per write, or a config full of tokens accumulates copies of itself.
- say it once. The write is useless until the app restarts, so a silent write leaves a user with no feature and no explanation.
- an opt-out that holds. Removal must survive the next session, or removal is not a thing the user can do.
Plus the precondition that makes it safe at all: being registered must not imply being able to act. readable's server refuses to offer its card tool to a host that cannot render one, so registering it in a profile that cannot use it costs nothing.
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 First seen · 42 lines · 787 tokens per session scan A 32292bfd0c35
claude-plugins CLAUDE.md is an instructions file published in the GitHub repository smk-labs/claude-plugins (11 stars, last pushed 28d ago), licensed MIT. It adds 787 tokens to every session, about $0.0031 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-30.
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.
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).
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.