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/notorious-ai/claude-plugins/claude-mdgit clone --depth 1 https://github.com/notorious-ai/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/notorious-ai/claude-plugins/claude-md)<a href="https://agentmods.dev/instructions/notorious-ai/claude-plugins/claude-md"><img src="https://agentmods.dev/badge/instructions/notorious-ai/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.03410 | $0.03410 |
| Opus 5 | $0.01705 | $0.01705 |
| Sonnet 5 | $0.00682 | $0.00682 |
| Haiku 4.5 | $0.00341 | $0.00341 |
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 5d 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 — 346 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 Navigation
Understanding This Repository's Structure
This repository uses a flat structure where each top-level directory represents a single, standalone plugin. There is no nesting or categorization - every plugin directory sits at the root level. The repository includes a marketplace file (.claude-plugin/marketplace.json) to enable easy discovery and installation.
To browse available plugins:
ls -d */
Each plugin directory contains its own .claude-plugin/plugin.json manifest, README.md, and optional component directories (commands, agents, skills, hooks, MCP config).
Finding Examples
Official Reference Repositories:
- anthropics/claude-code - Official Claude Code plugins
- anthropics/skills - Official Skills collection
Note: Like this repository, the official repositories use .claude-plugin/marketplace.json to enable plugin discovery. You can browse the marketplace file to understand their structure and locate individual plugins.
To explore plugins in this repository:
- Browse plugin directories at the root level
- Read plugin READMEs to understand their purpose and capabilities
- Examine component directories within plugins:
commands/- Slash command instruction filesagents/- Subagent configuration filesskills/- Skill directories withSKILL.mdhooks/- Event hook configurations.mcp.json- MCP server configurations
Planning a New Plugin
IMPORTANT: Always Plan Before Creating
When a user requests a new plugin, ALWAYS start with planning. Never immediately create files. Follow this process:
- Understand the Request
- What problem does this plugin solve?
- What capabilities should it provide?
- What are the expected inputs and outputs?
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.
- 5d ago First seen · 346 lines · 3,410 tokens per session scan A 22eb70eb3c7d
claude-plugins CLAUDE.md is an instructions file published in the GitHub repository notorious-ai/claude-plugins (5 stars, last pushed 10d ago), licensed MIT. It adds 3,410 tokens to every session, about $0.0170 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).
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.
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).