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/biggora/claude-plugins-registry/agents-mdgit clone --depth 1 https://github.com/biggora/claude-plugins-registryWrote 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/biggora/claude-plugins-registry/agents-md)<a href="https://agentmods.dev/instructions/biggora/claude-plugins-registry/agents-md"><img src="https://agentmods.dev/badge/instructions/biggora/claude-plugins-registry/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.00619 | $0.00619 |
| Opus 5 | $0.00309 | $0.00309 |
| Sonnet 5 | $0.00124 | $0.00124 |
| Haiku 4.5 | $0.00062 | $0.00062 |
Grade A, and why
claude-plugins-registry 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 4d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to Codex (Codex.ai/code) when working with code in this repository.
Project Overview
CLI marketplace for discovering, installing, and managing Codex plugins. Published as @biggora/Codex-plugins on npm. Plugins are git-cloned into ~/.Codex/plugins/ where Codex auto-discovers them.
Commands
# Run the CLI (no build step needed)
node bin/cli.js --help
# Test (currently just runs --help)
npm test
Architecture
Pure JavaScript ESM project ("type": "module") with no build/transpile step. Node.js >= 18 required.
Entry Points
bin/cli.js- CLI entry point using Commander.js. Defines all commands with lazyawait import()for each handler.package.jsonbinfield mapsCodex-pluginstobin/cli.js.
Core Modules
src/config.js- Constants and directory helpers. DefinesPLUGINS_DIR(~/.Codex/plugins),CACHE_DIR,CACHE_TTL(15 min), andREGISTRY_URL(GitHub raw URL).src/registry.js- Fetches registry with 3-tier fallback: remote -> local cache -> bundledregistry/registry.json. ProvidessearchPlugins()(keyword match across name/description/keywords/author) andfindPlugin()(exact name match).src/utils.js- Logging helpers (log.info/success/warn/error/dim),spinner()(ora),formatTable(),truncate().
Command Handlers (src/commands/)
Each file exports a single async function matching its command name:
search.js- Lists/filters plugins from registryinstall.js-git clonefrom plugin's repository URL into plugins diruninstall.js- Removes plugin directorylist.js- Reads installed plugins from~/.Codex/plugins/info.js- Shows detailed plugin metadataupdate.js-git pull --ff-onlyon installed pluginspublish.js- Validates plugin structure (.Codex-plugin/plugin.json+README.md) and generates registry JSON entry
Registry (registry/)
registry.json- Bundled fallback registry with plugin entriesschema.json- JSON schema for registry format
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.
- 4d ago First seen · 56 lines · 619 tokens per session scan A 3fb4228b337d
claude-plugins-registry AGENTS.md is an instructions file published in the GitHub repository biggora/claude-plugins-registry (2 stars, last pushed 6d ago), licensed MIT. It adds 619 tokens to every session, about $0.0031 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
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).
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.
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.
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.
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).
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.