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/bengous/claude-code-plugins/agents-mdgit clone --depth 1 https://github.com/bengous/claude-code-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.01075 | $0.01075 |
| Opus 5 | $0.00537 | $0.00537 |
| Sonnet 5 | $0.00215 | $0.00215 |
| Haiku 4.5 | $0.00108 | $0.00108 |
Grade A, and why
claude-code-plugins AGENTS.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 yesterday.
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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Plugin Marketplace
One directory per plugin, listed in .claude-plugin/marketplace.json.
Plugin Work
Do not reinvent plugin patterns. Delegate:
/plugin-dev:create-pluginand theplugin-devskills (structure, skills, hooks, agents, settings) to build or modify a pluginplugin-dev:plugin-validatoragent to validate oneclaude-code-guideagent for Claude Code behavior questions- Live doc search: the
claude-code-docsMCP server (user scope, https://code.claude.com/docs/mcp) - Official docs, the fallback when those are not installed: https://code.claude.com/docs/en/plugins
New plugin: add its marketplace.json entry and its README.md table row by hand; no check catches their absence. Version bumps: edit plugin.json only; pre-commit propagates to the existing entry and row.
Testing a plugin from source (launch flags, permission modes, transcript checks): docs/plugin-testing.md.
Commands
bun test # every suite outside dot directories
bun test ./.claude/hooks/*.test.ts # the repo's own hooks; `bun test` skips them
bun ./scripts/validate-marketplace.ts # versions + structure
bun ./scripts/validate-frontmatter.ts --all # frontmatter (default: staged only)
bun x tsgo --noEmit # types; fall back to ./node_modules/.bin/tsc --noEmit if tsgo rejects a flag
bun x oxlint # lint (correctness + suspicious + pedantic + anti-slop)
bun x oxfmt '**/*.ts' '**/*.js' '**/*.mjs' '**/*.cjs' # format; add --check to verify only
bun ./scripts/lint-shell.ts # shellcheck + shfmt; takes paths, else the whole repo
Everything above also runs in pre-commit and CI except bun test: lefthook.yml declares no test job, so run the tests yourself before pushing. Job list, order, and argument differences: docs/repo-ops.md.
Code Standards
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.
- yesterday First seen · 71 lines · 1,075 tokens per session scan A 1ce3155963f3
claude-code-plugins AGENTS.md is an instructions file published in the GitHub repository bengous/claude-code-plugins (4 stars, last pushed 2d ago), licensed MIT. It adds 1,075 tokens to every session, about $0.0054 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
workflowbuilder CLAUDE.md
Instructions for synergycodes/workflowbuilder, covering workflow builder, quick reference, agent signals, monorepo structure and per-workspace docs.
WorkFlowX CLAUDE.md
Instructions for TreeX-X/WorkFlowX, covering claude.md - workflowx instructions, routing, orchestrator workflow, constraints and file operations.
STAR AGENTS.md
Instructions for wanghao9610/STAR, covering agent instructions, 1. think before coding, 2. simplicity first, 3. surgical changes and 4. goal-driven execution.
airflow CLAUDE.md
Instructions for apache/airflow, a project described as: Apache Airflow - A platform to programmatically author, schedule, and monitor workflows.
usurahi CLAUDE.md
Instructions for usurahi-project/usurahi, covering 薄氷(うすらひ)— 共通ガイド, 薄氷とは, 共通原則, 会議状態の最小定義 and 起動時.
gza CLAUDE.md
Instructions for mhawthorne/gza: Read AGENTS.md for all project instructions.