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/lsantosweb/codex-agents-skills-kit/agents-mdgit clone --depth 1 https://github.com/lsantosweb/codex-agents-skills-kitWrote 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/lsantosweb/codex-agents-skills-kit/agents-md)<a href="https://agentmods.dev/instructions/lsantosweb/codex-agents-skills-kit/agents-md"><img src="https://agentmods.dev/badge/instructions/lsantosweb/codex-agents-skills-kit/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.01010 | $0.01010 |
| Opus 5 | $0.00505 | $0.00505 |
| Sonnet 5 | $0.00202 | $0.00202 |
| Haiku 4.5 | $0.00101 | $0.00101 |
Grade A, and why
codex-agents-skills-kit 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Project Orchestrator
This repository uses Codex with a router pattern:
AGENTS.mddefines the global operating rules..codex/skills/*/SKILL.mddefines specialist capabilities.- Codex should prefer the narrowest skill that matches the task.
- If a task spans multiple domains, Codex should sequence specialists instead of mixing responsibilities loosely.
Author
Public starter kit organized by Leandro Santos
Website: https://leandrosantos.net.br
Routing rules
1) Planning and discovery
Use project-planner first when:
- the request is broad, greenfield, or multi-step
- the team needs a task plan, folder structure, or dependency graph
- the work needs specialist assignment before implementation
Use code-archaeologist first when:
- the codebase is unfamiliar
- the request mentions legacy code, refactor, brownfield, reverse engineering, or hidden coupling
- the change would be risky without understanding the current behavior
2) Product and interface work
Use frontend-specialist for:
- React, Next.js, components, Tailwind, responsive UI, accessibility, web UI bugs
Use mobile-developer for:
- React Native, Expo, Flutter, iOS, Android, mobile UX, offline flows, device capabilities
Use designer-specialist for:
- visual hierarchy, spacing, typography, CTA visibility, layout cleanup, responsive polish
Use marketing-specialist for:
- landing page copy, positioning, CTA improvements, benefit framing, proof sections, message clarity
Use ptbr-language-reviewer for:
- PT-BR microcopy, grammar, UX writing, UI labels, landing page review, tone consistency in Brazilian Portuguese
3) Search and discoverability
Use seo-specialist for:
- technical SEO, schema, metadata, sitemap, robots, Core Web Vitals from search perspective, GEO/AI visibility
4) Application and data work
Use backend-specialist for:
- API design, auth, services, integrations, queues, validation, server-side debugging
Use database-architect for:
- schema design, migrations, indexing, SQL review, query optimization, vector search
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 · 115 lines · 1,010 tokens per session scan A 22198aeb2119
codex-agents-skills-kit AGENTS.md is an instructions file published in the GitHub repository lsantosweb/codex-agents-skills-kit (2 stars, last pushed 5mo ago), licensed MIT. It adds 1,010 tokens to every session, about $0.0051 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.