Borrowing it
Nothing to install: this file belongs to DmitriyYukhanov/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/DmitriyYukhanov/claude-plugins/main/CLAUDE.mdgit clone --depth 1 https://github.com/DmitriyYukhanov/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/dmitriyyukhanov/claude-plugins/claude-md)<a href="https://agentmods.dev/instructions/dmitriyyukhanov/claude-plugins/claude-md"><img src="https://agentmods.dev/badge/instructions/dmitriyyukhanov/claude-plugins/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.1 | $0.01552 | $0.01552 |
| Opus 5 | $0.00776 | $0.00776 |
| Sonnet 5 | $0.00310 | $0.00310 |
| Haiku 4.5 | $0.00155 | $0.00155 |
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 7d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Plugins Repository
Collection of Claude Code plugins: skills, agents, hooks, commands, and scripts.
Repository Hygiene (MANDATORY)
docs/superpowers/ and .serena/ are local-only artifacts — never commit them. They are excluded by .gitignore. The Superpowers brainstorming/planning workflow writes specs and plans into docs/superpowers/specs/ and docs/superpowers/plans/ for the developer's reference; those files stay on the local machine. Tool caches (.serena/, similar) also stay local.
Before every commit, run git diff --cached --name-only and confirm no path under docs/superpowers/ or .serena/ appears. If one does, abort and unstage with git restore --staged <path>. Use targeted git add <path> rather than git add -A / git add . to avoid accidentally staging artifacts.
Plugin Version Bumping (MANDATORY)
When you modify ANY file inside plugins/<name>/, you MUST also bump the "version" in that plugin's .claude-plugin/plugin.json and update the matching version in .claude-plugin/marketplace.json before committing. A pre-commit hook enforces both — commits without a version bump or with mismatched marketplace versions will be rejected.
Semantic Versioning (follow Keep a Changelog):
- PATCH (x.y.Z) — bug fixes, typo corrections, minor documentation tweaks
- MINOR (x.Y.0) — new features, skill improvements, prompt changes, non-breaking additions
- MAJOR (X.0.0) — breaking changes to skill behavior, major restructuring, removed functionality
Examples:
- Fixed a typo in a skill → PATCH (1.1.0 → 1.1.1)
- Rewrote a prompt template, added new sections → MINOR (1.1.0 → 1.2.0)
- Removed a skill, changed plugin interface → MAJOR (1.2.0 → 2.0.0)
Changelog (MANDATORY)
Every plugin has a CHANGELOG.md in its root directory (plugins/<name>/CHANGELOG.md). When you bump a plugin version, you MUST also add a changelog entry. The pre-commit hook enforces this — commits with a version bump but no changelog update will be rejected.
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.
- 7d ago First seen · 117 lines · 1,552 tokens per session scan A 3d19cf595a5b
claude-plugins CLAUDE.md is an instructions file published in the GitHub repository DmitriyYukhanov/claude-plugins (7 stars, last pushed 2d ago), licensed MIT. It adds 1,552 tokens to every session, about $0.0078 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
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.
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.
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).
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.