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/leonardsellem/codex-specialized-subagents/agents-mdgit clone --depth 1 https://github.com/leonardsellem/codex-specialized-subagentsWrote 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/leonardsellem/codex-specialized-subagents/agents-md)<a href="https://agentmods.dev/instructions/leonardsellem/codex-specialized-subagents/agents-md"><img src="https://agentmods.dev/badge/instructions/leonardsellem/codex-specialized-subagents/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.00916 | $0.00916 |
| Opus 5 | $0.00458 | $0.00458 |
| Sonnet 5 | $0.00183 | $0.00183 |
| Haiku 4.5 | $0.00092 | $0.00092 |
Grade A, and why
codex-specialized-subagents 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file is for AI coding agents.
Keep it short. Use hierarchical, nearest-wins AGENTS.md files:
- Root = global defaults + JIT map
- Subfolders = concrete commands + patterns for that scope
Project snapshot
- Name: codex-specialized-subagents
- What is this? MCP server that lets Codex delegate to isolated codex exec sub-agents, selecting repo+global skills automatically.
- Repo type: single project
- Primary stack: Node.js + TypeScript +
@modelcontextprotocol/sdk+zod
Root commands (verify these are real)
- Install:
npm install - Dev:
npm run dev - Build:
npm run build - Test:
npm test - Integration test (requires
codexCLI + auth):RUN_CODEX_INTEGRATION_TESTS=1 npm test - Lint/typecheck:
npm run lint
Universal conventions
- Default to small, finishable steps.
- State assumptions + open questions explicitly.
- Prefer pointers (paths + search commands) over long prose in AGENTS.
- Verify before claiming “done”.
Security & secrets
- Never commit secrets/tokens/keys.
- Put secrets in
.env/secret manager;.envis gitignored. - Avoid pasting secrets from
${CODEX_HOME:-~/.codex}(it may contain auth/config).
JIT directory map (nearest-wins)
.agent/→.agent/AGENTS.md(ExecPlans + artifacts workflow).codex/skills/→.codex/skills/AGENTS.md(repo-local skill authoring)docs/→ (human-facing docs; user + contributor guides)src/→src/AGENTS.md(MCP server + tool implementations)scripts/→scripts/AGENTS.md(helper scripts).githooks/→.githooks/AGENTS.md(optional git hooks)
As the repo grows:
apps/<name>/→apps/<name>/AGENTS.mdpackages/<name>/→packages/<name>/AGENTS.mdservices/<name>/→services/<name>/AGENTS.md- Add
docs/AGENTS.mdonly if docs need scope-specific agent rules.
Planning (ExecPlans)
- Rules live in:
.agent/PLANS.md - Create plans in:
.agent/execplans/ - Archive completed plans in:
.agent/execplans/archive/ - Debug journal:
.agent/DEBUG.md(local-only by default)
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 · 81 lines · 916 tokens per session scan A 136ad287a894
codex-specialized-subagents AGENTS.md is an instructions file published in the GitHub repository leonardsellem/codex-specialized-subagents (68 stars, last pushed 8mo ago), licensed MIT. It adds 916 tokens to every session, about $0.0046 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-30.
Other instructions, from other repositories
skrills AGENTS.md
AGENTS.md instructions for athola/skrills, covering ai agent development guidelines, guiding principles, development workflow, implementation cycle and when stuck.
agent-orchestrator AGENTS.md
AGENTS.md instructions for Untrivial-ai/agent-orchestrator, covering agents.md, repo layout, commands, where to look first and distribution.
agent-orchestrator CLAUDE.md
Claude Code instructions for Untrivial-ai/agent-orchestrator, covering claude.md, app state lives under /.ao only and design system.
ai-toolkit AGENTS.md
AGENTS.md instructions for pipefy/ai-toolkit, covering repository guidelines, documentation map, project structure, import namespace migration: pipefysdk → pipefy and src/pipefysdk/init.py (transitional shim).
agent-plugins copilot-instructions.md
Copilot instructions for dmgrok/agent-plugins, covering agent skills directory - ai agent instructions, project overview, architecture, core components and critical workflows.
NovelAI-Image-MCP AGENTS.md
Instructions for xinvxueyuan/NovelAI-Image-MCP, covering agents.md, 项目是什么, 仓库布局(uv + pnpm monorepo,turbo 编排), 常用命令 and 硬约束(不要触碰).