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/sgaunet/claude-plugins/claude-mdgit clone --depth 1 https://github.com/sgaunet/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/sgaunet/claude-plugins/claude-md)<a href="https://agentmods.dev/instructions/sgaunet/claude-plugins/claude-md"><img src="https://agentmods.dev/badge/instructions/sgaunet/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 | $0.03232 | $0.03232 |
| Opus 5 | $0.01616 | $0.01616 |
| Sonnet 5 | $0.00646 | $0.00646 |
| Haiku 4.5 | $0.00323 | $0.00323 |
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 4d 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 — 301 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
This is a Claude Code Plugin Marketplace repository that contains specialized agent definitions for DevOps and software engineering workflows. The repository follows the Claude Code plugin ecosystem structure, providing reusable agents that can be proactively activated based on context.
Architecture
Marketplace Structure
.claude-plugin/
└── marketplace.json # Marketplace definition and plugin registry
plugins/
├── devops-infrastructure/ # Infrastructure & operations agents
│ ├── .claude-plugin/
│ │ └── plugin.json
│ ├── agents/ # Agent definitions (5 agents)
│ └── commands/ # Custom slash commands (1 command)
│ # (no .mcp.json — declares no MCP servers)
│
├── software-engineering/ # General engineering workflows
│ ├── .claude-plugin/
│ │ └── plugin.json
│ ├── agents/ # Agent definitions (8 agents)
│ ├── commands/ # Custom slash commands (13 commands)
│ ├── skills/ # Reusable skills (4 skills)
│ └── .mcp.json # MCP server integration (context7)
│
├── go-specialist/ # Go language expertise
│ ├── .claude-plugin/
│ │ └── plugin.json
│ ├── agents/ # Agent definitions (1 agent)
│ ├── commands/ # Custom slash commands (7 commands)
│ ├── skills/ # Reusable skills (4 skills)
│ └── .mcp.json # MCP server integration (context7)
│
└── bash-specialist/ # Bash scripting expertise
├── .claude-plugin/
│ └── plugin.json
├── agents/ # Agent definitions (1 agent)
├── skills/ # Reusable skills (1 skill)
└── .mcp.json # MCP server integration (context7)
Agent Architecture
Agents are defined in markdown files with YAML frontmatter in plugins/*/agents/. Each agent follows this structure:
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.
- 4d ago First seen · 301 lines · 3,232 tokens per session scan A 21b48b284e2b
claude-plugins CLAUDE.md is an instructions file published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 2d ago), licensed MIT. It adds 3,232 tokens to every session, about $0.0162 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-30.
Other instructions, from other repositories
axiom AGENTS.md
Instructions for netopsengineer/axiom, covering agent instructions, scope, repository map, canonical sources and ownership matrix.
claude-plugins AGENTS.md
Instructions for jontsai/claude-plugins, covering agent guidelines, project overview, key constraints, plugin structure and validation.
Product-Marketing-Skills CLAUDE.md
Claude Code instructions for stefanoskarakasis/Product-Marketing-Skills, covering claude.md, versioning & releases, release procedure (manual, until ci enforcement exists) and after any repo change.
open-plugin CLAUDE.md
Instructions for baodq97/open-plugin, covering claude.md, project overview, structure, key decisions and conventions.
PM-Copilot-by-Product-Faculty CLAUDE.md
Claude Code instructions for Productfculty-aipm/PM-Copilot-by-Product-Faculty, covering pm copilot — global instructions, session start protocol, memory update protocol, context loading (all pm operations) and framework defaults.
claude-code-plugins CLAUDE.md
Claude Code instructions for qte77/claude-code-plugins, a project described as: A Claude Code plugin marketplace providing skills, rules, and scripts extracted from a production development workflow.