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/geoffjay/claude-plugins/claude-mdgit clone --depth 1 https://github.com/geoffjay/claude-pluginsWhat 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.00946 | $0.00946 |
| Opus 5 | $0.00473 | $0.00473 |
| Sonnet 5 | $0.00189 | $0.00189 |
| Haiku 4.5 | $0.00095 | $0.00095 |
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 3d 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 — 132 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 personal Claude Code plugins marketplace repository following a granular, composable architecture. The project is currently in early development stage - the plugin infrastructure and documentation exist, but the actual plugins are not yet implemented.
Architecture Philosophy
Core Principles
- Single Responsibility: Each plugin does one thing well (Unix philosophy)
- Composability: Mix and match plugins based on needs rather than forced bundling
- Context Efficiency: Smaller, focused tools for better LLM performance
- Progressive Disclosure: Skills use three-tier architecture (metadata → instructions → resources)
Target Structure
The repository is designed to support:
- Specialized Agents: Domain experts with deep knowledge, model-optimized (Haiku/Sonnet)
- Workflow Orchestrators: Multi-agent coordination systems for complex operations
- Development Tools: Project scaffolding, security scanning, test generation utilities
- Agent Skills: Modular knowledge packages following Anthropic's Agent Skills Specification
Repository Structure
claude-plugins/
├── .claude-plugin/
│ └── marketplace.json # Plugin marketplace catalog (currently empty)
├── plugins/ # Plugin directories (to be created)
│ └── {plugin-name}/
│ ├── agents/ # Specialized agents (optional)
│ ├── commands/ # Tools and workflows (optional)
│ └── skills/ # Modular knowledge packages (optional)
├── docs/
│ └── architecture.md # Detailed architecture documentation
├── .github/
│ ├── CONTRIBUTING.md # Contribution guidelines
│ ├── CODE_OF_CONDUCT.md # Community standards
│ └── ISSUE_TEMPLATE/ # Issue templates
└── README.md # Quick start guide
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.
- 3d ago First seen · 132 lines · 946 tokens per session scan A 424bf6330541
claude-plugins CLAUDE.md is an instructions file published in the GitHub repository geoffjay/claude-plugins (8 stars, last pushed 10mo ago), licensed MIT. It adds 946 tokens to every session, about $0.0047 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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.