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/juanmhidalgo/claude-plugins/claude-mdgit clone --depth 1 https://github.com/juanmhidalgo/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/juanmhidalgo/claude-plugins/claude-md)<a href="https://agentmods.dev/instructions/juanmhidalgo/claude-plugins/claude-md"><img src="https://agentmods.dev/badge/instructions/juanmhidalgo/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.00643 | $0.00643 |
| Opus 5 | $0.00321 | $0.00321 |
| Sonnet 5 | $0.00129 | $0.00129 |
| Haiku 4.5 | $0.00064 | $0.00064 |
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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
<project_context>
Claude Code plugins marketplace. Each top-level directory (e.g., code-review/, feature-dev/) is a plugin that bundles slash commands, agents, and skills. The marketplace registry lives in .claude-plugin/marketplace.json.
</project_context>
Plugin layout
.claude-plugin/
marketplace.json # Marketplace registry
<plugin-name>/
.claude-plugin/
plugin.json # Plugin metadata (name, version, description)
commands/ # Slash commands (*.md)
agents/ # Specialized agents (*.md)
skills/<name>/SKILL.md # Skills with optional references/
scripts/ # Shell scripts
CHANGELOG.md
README.md
For deeper conventions (frontmatter fields, discoverability, progressive disclosure), see .claude/rules/plugin-creation.md (auto-loaded when working in a plugin directory). For skill testing, see .claude/rules/skill-testing.md.
<critical_rules>
Version Management
When modifying any plugin, YOU MUST complete these steps IN ORDER:
- Bump the version in the plugin's
.claude-plugin/plugin.json - Use semantic versioning: patch (0.0.x) for fixes, minor (0.x.0) for features, major (x.0.0) for breaking changes
- Update the CHANGELOG.md in the plugin's root with the changes made
- Mirror the new version in
.claude-plugin/marketplace.json— the registry duplicates every plugin's version, and a stale entry pins installs to the old version
NEVER skip version bumping. Two PostToolUse hooks enforce this: version-bump-check.sh warns when a plugin file is edited without a bump or CHANGELOG entry, and marketplace-sync-check.sh warns when a registry version drifts from its plugin.json. Bypass either with SKIP_VERSION_CHECK=1 for genuinely in-progress work.
When editing marketplace.json, change the version lines in place. Re-serializing the file (e.g. json.dump) reflows every inline keywords array and turns a 3-line change into a 120-line diff.
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 · 72 lines · 643 tokens per session scan A 1b54e3bf1097
claude-plugins CLAUDE.md is an instructions file published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed 11d ago), licensed MIT. It adds 643 tokens to every session, about $0.0032 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
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).
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 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.
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.