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/l3digitalnet/claude-code-plugins/agents-mdgit clone --depth 1 https://github.com/L3DigitalNet/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.01255 | $0.01255 |
| Opus 5 | $0.00628 | $0.00628 |
| Sonnet 5 | $0.00251 | $0.00251 |
| Haiku 4.5 | $0.00126 | $0.00126 |
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 2d 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.
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.
<!-- prettier-ignore-start --> How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Instructions for Claude-Code-Plugins
Session state: Agent Handoff SessionStart injects docs/handoff/state.md; do not reread it when injected. Then use this file and docs/handoff/conventions.md.
Full conventions reference: docs/handoff/conventions.md - LLM-targeted pattern library. Every convention follows the six-field schema (Applies-when / Rule / Code / Why / Sources / Related) with a Quick Reference table at the top for O(1) lookup. Do not introduce new patterns without checking conventions first.
Detailed review workflows: AGENTS.reviews.md - read this only for review-related tasks (review planning, review sweeps, code/security/test/etc. reviews). The verbose per-review routing, defaults, and orchestrator notes live there.
Repo Purpose
Plugin authoring and release workspace for Claude Code / Codex plugins.
Key Rules
- Treat the design specs indexed in
docs/handoff/specs-plans.md(stored underdocs/plans/,docs/research/, anddocs/superpowers/{specs,plans}/) as the architectural source of truth for plugin behavior; the marketplace schema lives indocs/handoff/architecture.md. - Keep
.claude-plugin/plugin.json, plugin folders, command wiring, and marketplace metadata in sync. - Validate substantive plugin changes with the plugin test harness before wrapping up.
- Preserve documented enforcement layers, hooks, and release expectations when refactoring.
- Branch workflow: direct commit to
main. Notestingbranch — that convention was retired 2026-05-07. Plugin releases are manual: bumpplugin.jsonand the matching.claude-plugin/marketplace.jsonentry, commit, tag<name>/vX.Y.Z, push, andgh release create. See BRANCH_PROTECTION.md.
Markdown & Structured-Text Tooling
This repository follows the Markdown Tooling Standard (project-standards v3.0.0). Prettier formats the structured-text it supports (md/json/jsonc/yaml/code-workspace); markdownlint lints Markdown structure only. JS/TS source is excluded from Prettier via .prettierignore. MD060 is enabled at {style: "leading_and_trailing", aligned_delimiter: false} (Prettier-compatible; the standard's {style: "any"} conflicts with Prettier's empty-cell rendering). Both deviations recorded in docs/decisions/adr-0001-prettier-jsts-scope.md. Do not introduce a competing formatter or linter.
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.
- 2d ago First seen · 103 lines · 1,255 tokens per session scan C f3b2d21627ae
Claude-Code-Plugins AGENTS.md is an instructions file published in the GitHub repository L3DigitalNet/Claude-Code-Plugins (6 stars, last pushed 2d ago), licensed MIT. It adds 1,255 tokens to every session, about $0.0063 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-31.
Other instructions, from other repositories
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.
buildNext
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
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, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit 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.
langchain 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.