agentmods.dev

claude-code-plugins AGENTS.md

Repository instructions for developing and validating the claude-code-plugins project, including its testing rules and conventions.

In plain words
What is it for?
Use them when changing plugin code, marketplace categories, hooks, Python files, or other covered areas, and when deciding which affected test suites to run.
Why use it?
They explain which checks to run for a change and which project rules apply when editing particular files, reducing missed tests and incorrect changes.

Instructions file for CodexOpenCode

12 yesterday C scan 360 tokens original MIT
View the source file melodic-software/claude-code-plugins
Install

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.

agentmods
npx agentmods add instructions/melodic-software/claude-code-plugins/agents-md
Clone the repo
git clone --depth 1 https://github.com/melodic-software/claude-code-plugins

Made for: Codex, OpenCode.

Per session 360 This file is loaded in full into every session.
When invoked 360 The same file — it is already loaded in full.
Security scan C 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00360 $0.00360
Opus 5 $0.00180 $0.00180
Sonnet 5 $0.00072 $0.00072
Haiku 4.5 $0.00036 $0.00036

Measured yesterday against content hash b3ee7036b899, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

claude-code-plugins AGENTS.md scanned grade C with 1 finding 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.

Hidden instructionshighPrompt injection

Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.

<!-- BEGIN GENERATED: instruction-placement rules index -->
AGENTS.md · 27 lines

What it actually says

claude-code-plugins

Validate a change

Validate with scripts/affected-tests.sh --run (add --explain to see why each suite was selected) instead of running every suite; CI still runs everything. A changed file that maps to zero suites is an error, never "nothing to run". Full contract, including the no-suite allowlist and the NOT RUN ecosystems: README.md, "Validate a change".

Conventions that load on demand

Each surface below enters context automatically when Claude reads a file it covers. That trigger does not fire inside subagents, and after a compaction it fires again only when a covered file is read again. When you are working on something an entry covers and its content is not already in context, read the file directly.

Surface Covers Topic
.claude/rules/catalog-taxonomy.md .claude-plugin/marketplace.json Where the marketplace category taxonomy lives; read before adding or changing a plugin's category
.claude/rules/hook-budget.md plugins/*/hooks/** Marketplace-wide latency budget for always-on hooks; read before adding or widening a hook
.claude/rules/ruff-pin.md **/*.py Python linting runs through the pinned ruff wrapper, never a bare ruff on PATH
plugins/machine-health/skills/audit/AGENTS.md plugins/machine-health/skills/audit/** machine-health audit skill: contributor conventions
Changes

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.

  1. yesterday First seen · 27 lines · 360 tokens per session scan C b3ee7036b899

Subscribe to this mod's changes

claude-code-plugins AGENTS.md is an instructions file published in the GitHub repository melodic-software/claude-code-plugins (12 stars, last pushed yesterday), licensed MIT. It adds 360 tokens to every session, about $0.0018 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

LanguagesTestingagentsai-toolsclaude-codemarketplacemcpplugins
Related

Other instructions, from other repositories

agentenv Development Guide

Development areas and conventions across the Rust CLI, core library, and VS Code extension.

eduardoarantes/agentenv · 2,213 tokens

agentenv AGENTS.md

Instructions for eduardoarantes/agentenv, a project described as: Project-scoped AI agent and plugin environment manager for Claude Code, Cursor, Codex, and other AI tools.

eduardoarantes/agentenv · 6 tokens

claude-code-marketplace CLAUDE.md

Claude Code instructions for NikiforovAll/claude-code-marketplace, covering project, commands, architecture, key concepts and linting.

NikiforovAll/claude-code-marketplace · 511 tokens

atlas CLAUDE.md

Instructions for atlas-php/atlas: BEFORE ANY TASK: Read and follow AGENTS.md completely.

atlas-php/atlas · 27 tokens

claude-plugins CLAUDE.md

Instructions for tomoking2004/claude-plugins: Claude Code プラグインのマーケットプレイス．構成・導入・開発規約は README.md，美の基準は plugins/refine/BEAUTY.md を参照し，全ての成果物に適用する．.

tomoking2004/claude-plugins · 163 tokens

forge-skills AGENTS.md

Instructions for aneja5/forge-skills, covering agents.md, core rules, intent → skill mapping, define & specify and design.

aneja5/forge-skills · 3,107 tokens