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/lucasnad27/claude-plugins/claude-mdgit clone --depth 1 https://github.com/lucasnad27/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/lucasnad27/claude-plugins/claude-md)<a href="https://agentmods.dev/instructions/lucasnad27/claude-plugins/claude-md"><img src="https://agentmods.dev/badge/instructions/lucasnad27/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.00271 | $0.00271 |
| Opus 5 | $0.00135 | $0.00135 |
| Sonnet 5 | $0.00054 | $0.00054 |
| Haiku 4.5 | $0.00027 | $0.00027 |
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 today.
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.
What it actually says
claude-plugins
Marketplace repo. Each plugin under plugins/ versions independently. Releases go
through .claude/skills/cut-a-release.
Testing a plugin before you release it
Load the working tree directly for one session — no marketplace entry, no config changes:
claude plugin disable <plugin-name> --scope user
cd /path/to/a/real/test/repo
claude --plugin-dir ~/dev/claude-plugins/plugins/<plugin-name>
Re-enable with claude plugin enable <plugin-name> when done.
--plugin-dir takes the plugin directory (the one holding .claude-plugin/plugin.json),
not the repo root. It loads alongside installed plugins, which is why the disable is not
optional: a --plugin-dir copy whose name matches an installed plugin is shadowed by the
installed one with no warning — you get the released version and think you're testing main.
claude plugin validate <path> --strict checks manifests without starting a session.
For a persistent local install instead, claude plugin marketplace add ~/dev/claude-plugins
works, but the marketplace name comes from marketplace.json and collides with the
GitHub-sourced one already registered. Remove that first.
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.
- today First seen · 28 lines · 271 tokens per session scan A 91936e1a230e
claude-plugins CLAUDE.md is an instructions file published in the GitHub repository lucasnad27/claude-plugins (3 stars, last pushed 5d ago), licensed MIT. It adds 271 tokens to every session, about $0.0014 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-09-05.
Other instructions, from other repositories
planning-with-files AGENTS.md
AGENTS.md instructions for OthmanAdi/planning-with-files, covering agents.md — planning-with-files agent reference card, commit rules, release checklist (12 steps), version bump scope and changelog format.
openrouter-mcp-multimodal AGENTS.md
AGENTS.md instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).
OpenMicro AGENTS.md
Instructions for stephenleo/OpenMicro, covering openmicro — project conventions and releases.
ai-usagebar CLAUDE.md
Claude Code instructions for akitaonrails/ai-usagebar, covering claude.md, release checklist — must do all of these, hard invariants — never break these, secret-discipline rules (learned the hard way) and live api smoke discipline.
living-manual CLAUDE.md
Instructions for dougstanford/living-manual, covering living-manual, start of every session, how work lands — non-negotiable, user's manual (living-manual) and releasing.
yandex360-mcp CLAUDE.md
Claude Code instructions for pa1ch/yandex360-mcp, covering claude.md — гайд для ассистента, как устроен релиз (всё автоматически по тегу), процедура релиза (шаги ассистента), гарды and архитектура (кратко).