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/claude-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.00813 | $0.00813 |
| Opus 5 | $0.00407 | $0.00407 |
| Sonnet 5 | $0.00163 | $0.00163 |
| Haiku 4.5 | $0.00081 | $0.00081 |
Grade C, and why
Claude-Code-Plugins CLAUDE.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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Session startup: Agent Handoff injects state through the shared repo-local SessionStart hook.
Branch workflow: Direct commit to main. No testing branch. Plugin releases are manual — bump plugins/<name>/.claude-plugin/plugin.json and its matching .claude-plugin/marketplace.json entry, then commit, tag <name>/vX.Y.Z, push, and gh release create. See BRANCH_PROTECTION.md for full rules.
Document layout (read on demand):
docs/handoff/state.md— live state + active incidents (auto-injected, do not read directly)docs/handoff/deployed.md— deployment truth + what-remainsdocs/handoff/architecture.md— repo structure + plugin design principles + full CLAUDE.md detaildocs/handoff/credentials.md— credential surfacesdocs/handoff/conventions.md— pattern library (Phase 5 deferred)docs/handoff/sessions/— monthly session logs (grep by date)docs/handoff/bugs/— per-file bug KB (grep by service or tag)docs/handoff/specs-plans.md— pointer intodocs/plans/- per-plugin tests:
plugins/<plugin>/tests/(frameworks by language perdocs/handoff/conventions.mdTEST-001)
Agent Handoff
Use the repo-local agent-handoff skill at session startup and closeout. Do not reread state already injected by SessionStart. Keep project knowledge inside this repository and store credential references only, never values.
Markdown and structured-text tooling
Prettier owns physical formatting and markdownlint owns Markdown structure. Do not add overlapping tools.
Enabled checks: format, lint.
Markdown scope: **/*.md.
Structured-config scope: **/*.json, **/*.jsonc, **/*.yml, **/*.yaml.
Lint additionally skips generated directories: .pytest_cache/**, .ruff_cache/**, .venv/**, node_modules/**.
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 · 71 lines · 813 tokens per session scan C 6f65a4b4cf3b
Claude-Code-Plugins CLAUDE.md is an instructions file published in the GitHub repository L3DigitalNet/Claude-Code-Plugins (6 stars, last pushed 2d ago), licensed MIT. It adds 813 tokens to every session, about $0.0041 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.
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
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
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
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.