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/anthony-spruyt/claude-plugins/claude-mdgit clone --depth 1 https://github.com/anthony-spruyt/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/anthony-spruyt/claude-plugins/claude-md)<a href="https://agentmods.dev/instructions/anthony-spruyt/claude-plugins/claude-md"><img src="https://agentmods.dev/badge/instructions/anthony-spruyt/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.00352 | $0.00352 |
| Opus 5 | $0.00176 | $0.00176 |
| Sonnet 5 | $0.00070 | $0.00070 |
| Haiku 4.5 | $0.00035 | $0.00035 |
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.
What it actually says
CLAUDE.md
Repository Purpose
Plugin monorepo for Claude Code. Contains the hookify-plus engine and rule plugins.
Structure
hookify-plus/— Rule engine plugin (convention-based discovery)security-hooks/— 23 blocking rules (requires hookify-plus)best-practices/— 6 warning rules (requires hookify-plus)tests/— Integration tests for all rules
Commands
# Run tests
python3 tests/helpers/run_hookify_tests.py tests/hooks/hookify_test_cases.yaml --verbose
# Run bats integration tests
bats tests/hooks/
# Run unit tests
pytest tests/unit/ -v
Versioning
Plugin versions are read from plugin.json manifests. claude plugins update compares the installed version string against the manifest — same string means "already at latest" even if code changed.
When making changes in a PR, bump the version in both files:
<plugin>/.claude-plugin/plugin.json— the plugin's own manifest.claude-plugin/marketplace.json— the marketplace registry
Use semver: patch for bug fixes, minor for new rules/features, major for breaking changes.
If you forget, users must uninstall/reinstall to pick up changes.
Plugin Discovery Convention
Rules live in hookify-plus/ directories. The engine scans:
.claude/hookify-plus/*.md— project-level~/.claude/hookify-plus/*.md— global<sibling_plugin>/hookify-plus/*.md— plugin-provided (same marketplace)
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 · 47 lines · 352 tokens per session scan A 0084b9f9fc27
claude-plugins CLAUDE.md is an instructions file published in the GitHub repository anthony-spruyt/claude-plugins (2 stars, last pushed yesterday), licensed MIT. It adds 352 tokens to every session, about $0.0018 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).
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.
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).
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.