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/legacybridge-tech/claude-plugins/claude-mdgit clone --depth 1 https://github.com/legacybridge-tech/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/legacybridge-tech/claude-plugins/claude-md)<a href="https://agentmods.dev/instructions/legacybridge-tech/claude-plugins/claude-md"><img src="https://agentmods.dev/badge/instructions/legacybridge-tech/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.00351 | $0.00351 |
| 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 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 Code Development Guide
Adding a New Plugin
When adding a new plugin, follow these steps:
1. Create Plugin Structure
<plugin-name>/
├── .claude-plugin/
│ └── plugin.json # Plugin metadata
├── README.md # Plugin documentation
└── skills/
└── <skill-name>/
└── SKILL.md # Skill definition and commands
2. Create plugin.json
{
"name": "<plugin-name>",
"description": "Plugin description",
"version": "1.0.0",
"author": {
"name": "Frank Wang"
},
"keywords": ["keyword1", "keyword2"],
"license": "MIT"
}
3. Create SKILL.md
---
name: <skill-name>
description: Skill description for Claude to know when to use this skill.
---
# Skill Title
## Commands
...
4. Update marketplace.json (IMPORTANT!)
After adding a new plugin, you MUST update .claude-plugin/marketplace.json:
- Add the new plugin to the
pluginsarray - Bump the marketplace
versionnumber
{
"name": "<plugin-name>",
"source": "./<plugin-name>",
"description": "Plugin description",
"version": "1.0.0",
"keywords": ["keyword1", "keyword2"]
}
5. Commit Changes
Ensure the commit includes:
- All files for the new plugin
- Updated
marketplace.json
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 · 70 lines · 351 tokens per session scan A 526ac4be3f6e
claude-plugins CLAUDE.md is an instructions file published in the GitHub repository legacybridge-tech/claude-plugins (6 stars, last pushed 3mo ago), licensed MIT. It adds 351 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.
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.