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/vadimcomanescu/codex-skills/agents-mdgit clone --depth 1 https://github.com/vadimcomanescu/codex-skillsWrote 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/vadimcomanescu/codex-skills/agents-md)<a href="https://agentmods.dev/instructions/vadimcomanescu/codex-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/vadimcomanescu/codex-skills/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.00608 | $0.00608 |
| Opus 5 | $0.00304 | $0.00304 |
| Sonnet 5 | $0.00122 | $0.00122 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
codex-skills 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 5d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
This repository is a Codex skill catalog. Keep skills self-contained and organized under skills/:
skills/.experimental/<category>/<skill-name>/SKILL.md: entrypoint and workflow for a single skill (required).skills/.experimental/<category>/<skill-name>/references/: optional docs/links the skill relies on.skills/.experimental/<category>/<skill-name>/scripts/: optional helper scripts used by the skill.skills/.experimental/<category>/<skill-name>/assets/: optional templates, examples, or UI assets.
When a skill is stable, promote it to skills/.curated/<category>/<skill-name>/.
Keep each skill self-contained. If you introduce shared utilities, place them in shared/ and document the dependency in each skill’s SKILL.md.
Build, Test, and Development Commands
No build/test automation is configured yet. Until it exists, use lightweight checks:
git status: confirm only intended files changed.git diff: review the final patch before committing.python scripts/validate_skills.py: validate SKILL frontmatter, required files, and referenced paths.
If you add runnable code (Node/Python/etc.), add a single canonical entry point (e.g., package.json scripts or a Makefile) and update this section with commands like make lint, make test, and make fmt.
Coding Style & Naming Conventions
- Indentation: 2 spaces for Markdown lists; avoid hard tabs.
- Filenames: use
kebab-casefor skill directories (e.g.,skills/.curated/design/frontend-design/). - Skill docs: keep
SKILL.mdtask-focused, with numbered steps and short examples (commands and paths in backticks). - For long examples or tutorials, move content to
references/examples.mdand link it fromSKILL.md. - Scripts: prefer small, composable scripts with clear usage (
--helpor header comments) and deterministic output.
Testing Guidelines
When a skill includes executable scripts, add a minimal smoke test and document how to run it. Recommended patterns:
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.
- 5d ago First seen · 45 lines · 608 tokens per session scan A a74844d7bf16
codex-skills AGENTS.md is an instructions file published in the GitHub repository vadimcomanescu/codex-skills (24 stars, last pushed 7mo ago), licensed MIT. It adds 608 tokens to every session, about $0.0030 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
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.