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 skills/mturac/everything-openai-codex/everything-openai-codexnpx skills add mturac/everything-openai-codex --skill everything-openai-codexgit clone --depth 1 https://github.com/mturac/everything-openai-codexWrote 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/skills/mturac/everything-openai-codex/everything-openai-codex)<a href="https://agentmods.dev/skills/mturac/everything-openai-codex/everything-openai-codex"><img src="https://agentmods.dev/badge/skills/mturac/everything-openai-codex/everything-openai-codex.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.00025 | $0.02784 |
| Opus 5 | $0.00013 | $0.01392 |
| Sonnet 5 | $0.00005 | $0.00557 |
| Haiku 4.5 | $0.00003 | $0.00278 |
Grade A, and why
everything-openai-codex 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.
This is a copy
89% identical to everything-claude-code — 24 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 451 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Everything OpenAI Codex Conventions
Generated from mehmet-turac/everything-openai-codex on 2026-03-20
Responsibility Contract
- Role: senior maintainer for the Everything OpenAI Codex repository.
- Owned surface: repository files explicitly required by the task; avoid unrelated refactors.
- Preservation: keep public install identifiers, catalog counts, hook contracts, and release evidence consistent.
- Verification: run the narrowest relevant tests first, then broader CI checks when shared surfaces change.
- Report: changed surfaces, verification commands, unresolved risks, and any skipped checks.
Overview
This skill teaches Codex the development patterns and conventions used in Everything OpenAI Codex.
Tech Stack
- Primary Language: JavaScript
- Architecture: hybrid module organization
- Test Location: separate
When to Use This Skill
Activate this skill when:
- Making changes to this repository
- Adding new features following established patterns
- Writing tests that match project conventions
- Creating commits with proper message format
Commit Conventions
Follow these commit message conventions based on 500 analyzed commits.
Commit Style: Conventional Commits
Prefixes Used
fixtestfeatdocs
Message Guidelines
- Average message length: ~65 characters
- Keep first line concise and descriptive
- Use imperative mood ("Add feature" not "Added feature")
Commit message example
feat(rules): add C# language support
Commit message example
chore(deps-dev): bump flatted (#675)
Commit message example
fix: auto-detect ecc root from plugin cache when CODEX_PLUGIN_ROOT is unset (#547) (#691)
Commit message example
docs: add Antigravity setup and usage guide (#552)
Commit message example
merge: PR #529 — feat(skills): add documentation-lookup, bun-runtime, nextjs-turbopack; feat(agents): add rust-reviewer
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 451 lines · 25 tokens per session scan A b73a07dfdaac
everything-openai-codex is a skill published in the GitHub repository mturac/everything-openai-codex (89 stars, last pushed 11d ago), licensed MIT. It adds 25 tokens to every session and 2,784 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to everything-claude-code, differing in 24 lines, and is treated as a copy.
Other skills, from other repositories
architecture-diagram
Dark-themed SVG architecture/cloud/infra diagrams as HTML.
browser_cdp
通过 Chrome DevTools Protocol (CDP) 连接已运行的浏览器，或扫描本机 CDP 端口，用于远程调试与多工具共享浏览器实例。.
validate-harness
Release-readiness umbrella check for a scaffolded harness — runs doctor, witness verify, hardcoded-path scan, MCP server config, and GCP Secret Manager validation in one shot. Exits non-zero if any sub-check fails.
debug
Interactive debugging workflow with hypothesis-driven probe loop. Use when: unknown bugs, script errors, silent failures, troubleshooting. Not for: known bugs (use bug-fix), GitHub issue analysis (use issue-analyze), code understanding (use code-explore). Output: debug report with probe journal + root cause + fix.
deep-review
Parallel competency-based code review. Launches independent Agent reviewers per competency (security, performance, architecture, database, concurrency, error-handling, frontend, testing), each with a focused checklist and isolated context. Synthesizes findings into unified report with FIX/DEFER/ACCEPT triage. Use…
simplify
Wrap-up refactoring — simplify code, eliminate duplication, preserve behavior.