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/apurvbazari/claude-plugins/claude-mdgit clone --depth 1 https://github.com/ApurvBazari/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/apurvbazari/claude-plugins/claude-md)<a href="https://agentmods.dev/instructions/apurvbazari/claude-plugins/claude-md"><img src="https://agentmods.dev/badge/instructions/apurvbazari/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.01792 | $0.01792 |
| Opus 5 | $0.00896 | $0.00896 |
| Sonnet 5 | $0.00358 | $0.00358 |
| Haiku 4.5 | $0.00179 | $0.00179 |
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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
claude-plugins
Claude Code plugin marketplace by Apurv Bazari. Five plugins — all markdown + shell + JSON, no compiled code. (onboard, notify, handoff, walkthrough, lens.)
Repository
- GitHub:
ApurvBazari/claude-plugins(public) - Marketplace:
apurvbazari-plugins(registered in.claude-plugin/marketplace.json)
Architecture
.claude-plugin/marketplace.json ← plugin registry
│
├──→ onboard/ ← codebase analyzer + tooling generator
│ ├── skills/ (start, adopt, generate, update, check, verify, evolve,
│ │ research, wizard, generation)
│ ├── agents/ (codebase-analyzer, config-generator, feature-evaluator,
│ │ research-specialist, research-verifier)
│ └── scripts/ (detect-{config,dep,structure}-changes, detect-{lsp,mcp}-signals, audit-tooling, install-plugins)
│
├──→ notify/ ← cross-platform system notifications
│ ├── skills/ (setup, check, uninstall, wizard)
│ └── scripts/ (notify, install-notifier)
│
├──→ handoff/ ← session handoff continuity
│ └── skills/ (save, pickup, check, discard)
│
├──→ walkthrough/ ← session → self-contained interactive HTML
│ └── skills/ (create, update, document, render)
│
└──→ lens/ ← intent-grounded review companion (brain; renders via walkthrough)
├── skills/ (review, engine, render-review, capability)
├── agents/ (spec-adherence, plan-adherence, correctness,
│ risk-classify, test-gaps, verifier)
└── schemas/ (review-findings)
(runtime: hands off to walkthrough:render; markdown fallback if absent)
Plugin Structure Convention
Every plugin must have:
.claude-plugin/plugin.json— manifest with name, version, description, author, license, keywordsREADME.md— user-facing documentation- At least one of:
skills/,agents/
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 · 118 lines · 1,792 tokens per session scan A 27326dd78ffc
claude-plugins CLAUDE.md is an instructions file published in the GitHub repository ApurvBazari/claude-plugins (0 stars, last pushed 28d ago), licensed MIT. It adds 1,792 tokens to every session, about $0.0090 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
agent-inbox CLAUDE.md
Instructions for Ideaplaces/agent-inbox, covering agent inbox: working notes, local development, gotchas already paid for, keep readme.md current and conventions.
cc-notifier CLAUDE.md
Claude Code instructions for trentmcnitt/cc-notifier, covering claude.md, project overview, context files, code philosophy and principles.
claude-code-notifier CLAUDE.md
Claude Code instructions for saiso/claude-code-notifier, covering claude-code-notifier, 概要, プロジェクト構成, 技術スタック and 運用ルール.
framework AGENTS.md
AGENTS.md instructions for ai-driven-dev/framework, covering agents.md, behavior, communication, action and memory management.
cctop AGENTS.md
AGENTS.md instructions for st0012/cctop, covering agents.md - development guide for cctop, scope and sources, required development rules, driver workflow and github and pr rules.
barkeep AGENTS.md
AGENTS.md instructions for iannuttall/barkeep, covering agent notes, product rules, repo map, commands and app structure.