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/cwakim/claude-plugins/claude-mdgit clone --depth 1 https://github.com/cwakim/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/cwakim/claude-plugins/claude-md)<a href="https://agentmods.dev/instructions/cwakim/claude-plugins/claude-md"><img src="https://agentmods.dev/badge/instructions/cwakim/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.00504 | $0.00504 |
| Opus 5 | $0.00252 | $0.00252 |
| Sonnet 5 | $0.00101 | $0.00101 |
| Haiku 4.5 | $0.00050 | $0.00050 |
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.
What it actually says
claude-plugins
A personal Claude Code plugin marketplace. The repo is cwakim/claude-plugins;
the marketplace and each plugin live under it.
Layout
.claude-plugin/marketplace.json # marketplace manifest (lists every plugin)
plugins/<name>/.claude-plugin/plugin.json # per-plugin manifest
plugins/<name>/commands/*.md # the plugin's slash commands
plugins/<name>/README.md # per-plugin docs
README.md # root: install + plugin table
Gotchas (read before editing manifests)
- The marketplace
namemust not contain "claude". The loader rejects any name containing "claude" as impersonating an official marketplace. That is whymarketplace.jsonis namedcwakim-pluginseven though the repo and install path arecwakim/claude-plugins. Do not "fix" this mismatch. - Bump versions in two places, in sync. A plugin's version lives in both
plugins/<name>/.claude-plugin/plugin.jsonand its entry in.claude-plugin/marketplace.json. They must match. - Install/update uses the marketplace suffix:
/plugin install <name>@cwakim-plugins(a bare<name>is ambiguous).
Adding a plugin
- Create
plugins/<name>/.claude-plugin/plugin.json(name, description, version, author) andplugins/<name>/commands/*.md. - Register it in the
pluginsarray of.claude-plugin/marketplace.json. - Add a row to the table in the root
README.md.
Workflow
- PR-based: branch, open a PR, self-merge. Branches auto-delete on merge.
Do not commit directly to
main. - Use the PR template at
.github/pull_request_template.mdfor the PR body: fill out Summary / Type of change / Checklist / Notes for reviewers. Do not substitute a freeform body. - Never push without asking.
- Prose: no em-dashes or en-dashes.
- After merging a plugin change, refresh the dogfooded install with
/plugin marketplace update cwakim-pluginsthen/plugin update <name>@cwakim-plugins.
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 · 46 lines · 504 tokens per session scan A d749c93646ee
claude-plugins CLAUDE.md is an instructions file published in the GitHub repository cwakim/claude-plugins (2 stars, last pushed 13d ago), licensed MIT. It adds 504 tokens to every session, about $0.0025 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.