Borrowing it
Nothing to install: this file belongs to msshives-gif/claude-plugins. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/msshives-gif/claude-plugins/main/AGENTS.mdgit clone --depth 1 https://github.com/msshives-gif/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/msshives-gif/claude-plugins/agents-md)<a href="https://agentmods.dev/instructions/msshives-gif/claude-plugins/agents-md"><img src="https://agentmods.dev/badge/instructions/msshives-gif/claude-plugins/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/msshives-gif/claude-plugins/agents-md"><img src="https://agentmods.dev/badge/instructions/msshives-gif/claude-plugins/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00380 | $0.00380 |
| Opus 5.5 | $0.00152 | $0.00152 |
| Sonnet 5.5 | $0.00076 | $0.00076 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
claude-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 1mo 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 ("claude context tools")
Marketplace monorepo: every plugin lives under plugins/<name>/, one
marketplace at .claude-plugin/marketplace.json. Simple code and
simple documentation is best; complexity and big words are the enemy.
Prefer the boring obvious shape; build machinery only when real use
forces it.
- All plugins parse undocumented Claude Code internals (transcript JSONL, sessions registry, meta.json). Never make parsing stricter without keeping degrade-to-silence; when the observed format changes, update the affected plugins' fixtures TOGETHER — this shared surface is why the repo is a monorepo.
- Shared measurement core:
plugins/subagent-context/hooks/ subagent_context.py, vendored into send-guard bytools/sync-core.py(drift-guard test enforces sync). compact-manager owns its hand-ported copy outright. - Hooks MUST fail open (exit 0 on every path) and each plugin's
uninstall markers must match only its own hook paths — plugins
share the repo directory name (see each plugin's
tests/test_install_scripts.py). - Keep the repo system-agnostic: no machine-specific paths, hosts, or identities in tracked files; managed mode is Linux/WSL-only and says so rather than pretending otherwise.
- Per-plugin discipline lives in each plugin's own CLAUDE.md/README.
- Unit suites:
python3 -m unittest discover plugins/<name>/testsper plugin. compact-manager's managed mode additionally has a gated LIVE suite (tools/live-managed/run.sh— spawns a real claude session; run manually) that must pass before releasing changes to the watcher/ladder.
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.
- 1mo ago First seen · 31 lines · 380 tokens per session scan A 6c3462a2a4b3
claude-plugins AGENTS.md is an instructions file published in the GitHub repository msshives-gif/claude-plugins (2 stars, last pushed 7d ago), licensed MIT. It adds 380 tokens to every session, about $0.0015 per session on Opus 5.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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).