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/n24q02m/claude-plugins/agents-mdgit clone --depth 1 https://github.com/n24q02m/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/n24q02m/claude-plugins/agents-md)<a href="https://agentmods.dev/instructions/n24q02m/claude-plugins/agents-md"><img src="https://agentmods.dev/badge/instructions/n24q02m/claude-plugins/agents-md.svg" alt="Measured on agentmods" 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 | $0.01209 | $0.01209 |
| Opus 5 | $0.00605 | $0.00605 |
| Sonnet 5 | $0.00242 | $0.00242 |
| Haiku 4.5 | $0.00121 | $0.00121 |
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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Collaboration
Quick reference
- Repo:
n24q02m/claude-plugins - Description: 9 MCP servers for Claude Code, Codex, and other AI coding agents.
- License: Apache-2.0
Build & Test
See README.md for end-user install. For development:
mise run setup # First-time dev environment
mise run lint # Read-only lint + format check + type check
mise run test # Run tests
mise run fix # Auto-fix lint + format
Release
Releases triggered manually via workflow_dispatch on cd.yml. Choose beta or stable. python-semantic-release handles version bump, CHANGELOG, tag, and GitHub Release.
Conventions
- Commits: only
feat:andfix:prefixes (enforced by pre-commitcommit-msghook) - Test coverage: ≥ 95% on internal modules
- No secrets in code, commits, or memory — use skret for secret retrieval
plugins/<repo>/is generated.scripts/sync-plugins.shreplacesplugin.json,gemini-extension.json,skills/,hooks/,commands/andchat.pyfrom the source repository on every release, so a patch to those paths is erased at that plugin's next release — open it against the source repo instead. The setup prose alongside them is not generated and is edited here.- Decisions on proposals, accepted and rejected, are recorded in
.jules/bolt.md,.jules/palette.mdand.jules/sentinel.md. Read the relevant one before proposing a change, so a settled question is not reopened.
Renaming a tool in a server
plugins/<repo>/tools.md is the only place a tool name is written down for the
public. The marketplace listing and mcp.n24q02m.com/servers/<repo>/tools/ both
read it, and nothing generates it: plugin.json carries no tool list, and the
sync described above never copies .md files. A rename in a server is therefore
invisible here until somebody types it, and until they do, the docs name tools
the server no longer answers to.
Who starts the update
The server repo, not this one. Every server already notifies this repo on
release (repository_dispatch: plugin-sync), and the session that renames a
tool opens the companion tools.md pull request here. This repo does not scrape
server repos for prose — it verifies what it was handed, and sweeps weekly so a
rename that nobody reported still surfaces.
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.
- 3d ago First seen · 97 lines · 1,209 tokens per session scan A f76767372ecd
claude-plugins AGENTS.md is an instructions file published in the GitHub repository n24q02m/claude-plugins (3 stars, last pushed 3d ago), licensed Apache-2.0. It adds 1,209 tokens to every session, about $0.0060 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
runecho CLAUDE.md
Claude Code instructions for inth3shadows/runecho, covering runecho workflow, release tags and git hooks — there are five, from two different installers.
mcp-walmart-marketplace AGENTS.md
AGENTS.md instructions for alyiox/mcp-walmart-marketplace, covering agent instructions, commit messages, header, body and release tags.
chatgpt-cli CLAUDE.md
Instructions for kardolus/chatgpt-cli, covering chatgpt-cli — release runbook, prerequisites, 1. cut the release, 2. publish the github release + binaries and 3. update the homebrew tap.
mumei CLAUDE.md
Instructions for iroha924/mumei, covering mumei development guide, what mumei is, language policy, bash + jq conventions (essentials) and schemas/ conventions (essentials).
kleosrules AGENTS.md
Instructions for kleosr/kleosrules, a project described as: Cursor harness pack: user rules, skills, Bash hooks, local HANDOFF memory. macOS, Linux, Windows (WSL).
living-manual CLAUDE.md
Instructions for dougstanford/living-manual, covering living-manual, start of every session, how work lands — non-negotiable, user's manual (living-manual) and releasing.