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/anhnguyen0905/codex-mcp/exec-coding-standardsnpx skills add anhnguyen0905/codex-mcp --skill exec-coding-standardsgit clone --depth 1 https://github.com/anhnguyen0905/codex-mcpWrote 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/anhnguyen0905/codex-mcp/exec-coding-standards)<a href="https://agentmods.dev/skills/anhnguyen0905/codex-mcp/exec-coding-standards"><img src="https://agentmods.dev/badge/skills/anhnguyen0905/codex-mcp/exec-coding-standards.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.00048 | $0.00389 |
| Opus 5 | $0.00024 | $0.00195 |
| Sonnet 5 | $0.00010 | $0.00078 |
| Haiku 4.5 | $0.00005 | $0.00039 |
Grade A, and why
exec-coding-standards 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.
What it actually says
Coding Standards (embed into Codex prompts)
These rules go INTO the codex_execute prompt so Codex writes to senior standard. Include the block below (plus the matching language skill) in every execution task.
Standards block
Coding standards (mandatory):
- KISS: simplest solution that works; no premature optimization or speculative abstraction (YAGNI).
- DRY: extract repeated logic; but prefer a little duplication over the wrong abstraction.
- Immutability: return new values instead of mutating inputs/shared state.
- Errors: handle explicitly at every level; never swallow silently; user-facing messages friendly,
logs detailed; fail fast on programmer errors.
- Validation: validate ALL external input (user, API, file, env) at the boundary with clear failures.
- No hardcoded secrets/config — env vars or config files; validate presence at startup.
- Naming: descriptive; booleans read as predicates (is/has/can/should); constants UPPER_SNAKE_CASE.
- Structure: functions < 50 lines, files < 800, nesting < 4 (use early returns).
- Comments: only for constraints code can't express (the "why"); no narration of the obvious.
- Match the existing codebase's style, structure, and idioms over any personal preference.
- No debug prints (console.log/print) left in production code paths.
Why embedded, not assumed
Codex doesn't see Claude's skills or the user's global rules — the prompt is the only channel. A plan without embedded standards produces stylistically alien code that fails review round 1 on preventable findings.
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 · 31 lines · 48 tokens per session scan A 9aae80f46653
exec-coding-standards is a skill published in the GitHub repository anhnguyen0905/codex-mcp (3 stars, last pushed 12d ago), licensed MIT. It adds 48 tokens to every session and 389 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…