Borrowing it
Nothing to install: this file belongs to peterblazejewicz/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/peterblazejewicz/claude-plugins/main/CLAUDE.mdgit clone --depth 1 https://github.com/peterblazejewicz/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/peterblazejewicz/claude-plugins/claude-md)<a href="https://agentmods.dev/instructions/peterblazejewicz/claude-plugins/claude-md"><img src="https://agentmods.dev/badge/instructions/peterblazejewicz/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.02455 | $0.02455 |
| Opus 5 | $0.01228 | $0.01228 |
| Sonnet 5 | $0.00491 | $0.00491 |
| Haiku 4.5 | $0.00246 | $0.00246 |
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 6d 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 — 82 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.
Repository Overview
A Claude Code plugin marketplace providing two plugins: avalonia-dev (Avalonia / MAUI structural review) and dotnet-skills (.NET/C# engineering workflow skills, indirect fork of addyosmani/agent-skills). This is a content-only repository with no build system — all files are markdown and JSON.
Plugin Architecture
The marketplace structure:
.claude-plugin/marketplace.json # Marketplace manifest listing all plugins
plugins/<plugin-name>/ # INSTALLED to user machines — keep it lean
.claude-plugin/plugin.json # Plugin metadata
commands/*.md # Slash commands (markdown with YAML frontmatter)
skills/<skill-name>/SKILL.md # Skill definitions with references
skills/<skill-name>/references/ # Skill reference files (patterns, guides)
LICENSES/ # Third-party license texts (MIT must travel with content)
NOTICE.md, README.md # Attribution + user-facing plugin docs
sync-state/<plugin-name>/ # NOT installed to users — maintainer artifacts only
vendor/<upstream>/ # Pristine upstream snapshot (for indirect-fork plugins)
UPSTREAM.md, SYNC.md # Pinned commit + per-skill port ledger
scripts/sync-agent-skills.ps1 # Maintainer-only re-sync tool
Invariant: plugins/<name>/ contains only what end users need at runtime. Anything that exists to help maintainers keep the plugin in sync with an upstream source belongs in sync-state/<name>/ and is never published via the marketplace. The source field in marketplace.json points at plugins/<name>/, so everything under that path gets installed when a user runs claude plugins install <name>.
Version coupling: when bumping a plugin's version, update both plugins/<name>/.claude-plugin/plugin.json and the matching entry in .claude-plugin/marketplace.json. Users pulling via claude plugins marketplace update won't see the new version unless both are in sync.
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.
- 6d ago First seen · 82 lines · 2,455 tokens per session scan A f6cd510793e1
claude-plugins CLAUDE.md is an instructions file published in the GitHub repository peterblazejewicz/claude-plugins (7 stars, last pushed 2mo ago), licensed MIT. It adds 2,455 tokens to every session, about $0.0123 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
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.
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).
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).
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.
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.