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/qte77/claude-code-plugins/agents-mdgit clone --depth 1 https://github.com/qte77/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.00903 | $0.00903 |
| Opus 5 | $0.00451 | $0.00451 |
| Sonnet 5 | $0.00181 | $0.00181 |
| Haiku 4.5 | $0.00090 | $0.00090 |
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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
Behavioral rules, compliance requirements, and decision frameworks for AI coding agents. For technical workflows and coding standards, see CONTRIBUTING.md. For project overview, see README.md.
External References:
- @CONTRIBUTING.md - Command reference, testing guidelines, code style patterns
- @AGENT_REQUESTS.md - Escalation and human collaboration
- @AGENT_LEARNINGS.md - Pattern discovery and knowledge sharing
Claude Code Infrastructure
Rules (.claude/rules/): Session-loaded constraints (always active)
Skills (.claude/skills/): Modular capabilities with progressive disclosure
Core Rules & AI Behavior
- Follow SDLC principles: maintainability, modularity, reusability, adaptability
- Never assume missing context - Ask questions if uncertain about requirements
- Never hallucinate libraries - Only use packages verified in project dependencies
- Always confirm file paths exist before referencing in code or tests
- Never delete existing code unless explicitly instructed or documented refactoring
- Document new patterns in AGENT_LEARNINGS.md (concise, laser-focused, streamlined)
- Request human feedback in AGENT_REQUESTS.md (concise, laser-focused, streamlined)
Decision Framework
Priority Order: User instructions > AGENTS.md compliance > Documentation hierarchy > Project patterns > General best practices
Anti-Scope-Creep Rules:
- NEVER implement features without requirement validation
- Always validate implementation decisions against project scope boundaries
Anti-Redundancy Rules:
- NEVER duplicate information across documents - reference authoritative sources
- Update authoritative document, then remove duplicates elsewhere
When to Escalate to AGENT_REQUESTS.md:
- User instructions conflict with safety/security practices
- AGENTS.md rules contradict each other
- Required information completely missing
- Actions would significantly change project architecture
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 · 111 lines · 903 tokens per session scan A 8e4b1495d4df
claude-code-plugins AGENTS.md is an instructions file published in the GitHub repository qte77/claude-code-plugins (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 903 tokens to every session, about $0.0045 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
dot-claude-plugins CLAUDE.md
Instructions for and3r817/dot-claude-plugins, covering claude.md, repository overview, core architecture principles, testing commands and run all test suites (master runner).
claude-code-plugins AGENTS.md
Instructions for DropFan/claude-code-plugins, covering claude code plugins collection, repository structure, plugin management, development guidelines and adding a self-developed plugin.
claude-plugins AGENTS.md
Instructions for jontsai/claude-plugins, covering agent guidelines, project overview, key constraints, plugin structure and validation.
Product-Marketing-Skills CLAUDE.md
Instructions for stefanoskarakasis/Product-Marketing-Skills, covering claude.md, versioning & releases, release procedure (manual, until ci enforcement exists) and after any repo change.
PM-Copilot-by-Product-Faculty CLAUDE.md
Claude Code instructions for Productfculty-aipm/PM-Copilot-by-Product-Faculty, covering pm copilot — global instructions, session start protocol, memory update protocol, context loading (all pm operations) and framework defaults.
claude-code-plugins CLAUDE.md
Instructions for DropFan/claude-code-plugins, covering claude code plugins collection, repository structure, plugin management, development guidelines and adding a self-developed plugin.