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 skills add anhnguyen0905/codex-mcp --skill review-securitygit 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/review-security)<a href="https://agentmods.dev/skills/anhnguyen0905/codex-mcp/review-security"><img src="https://agentmods.dev/badge/skills/anhnguyen0905/codex-mcp/review-security/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/anhnguyen0905/codex-mcp/review-security"><img src="https://agentmods.dev/badge/skills/anhnguyen0905/codex-mcp/review-security.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00028 | $0.00434 |
| Opus 5 | $0.00014 | $0.00217 |
| Sonnet 5 | $0.00006 | $0.00087 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
review-security 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 10d 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
Security Review
Mandatory triggers (never skip when the diff touches these)
Auth/session logic · user input handling · database queries · file system paths from input · external API calls · crypto · payments · anything reading env/config secrets · a non-code deliverable that could embed secrets, credentials, PII, or internal data that must not leave the workspace (check the content, not just code).
Checklist
- Secrets: no hardcoded API keys/passwords/tokens in code or tests; secrets come from env/config; nothing secret in log output or error messages. Grep the diff for
key|token|secret|passwordliterals. - Injection: SQL via parameterized queries only (no string concatenation); shell commands via arg arrays, never interpolated strings; HTML output escaped or sanitized (XSS); path traversal — user input never joined into file paths without normalization + allowlist.
- Validation at trust boundaries: every external input (HTTP body/params, file content, env, third-party API responses) validated before use; server-side validation present even when the client validates.
- AuthN/AuthZ: protected routes actually check permissions; object-level access control (user A can't fetch user B's resource by ID); no auth decisions from client-supplied fields.
- Unsafe patterns:
eval/dynamic code execution, pickle/unsafe deserialization of external data, disabled TLS verification, permissive CORS (*with credentials), weak or home-rolled crypto. - Dependencies: any dependency Codex added — check it's the package intended (typosquats), reasonably maintained, and actually needed.
- Error leakage: stack traces, internal paths, or query details never sent to end users.
Severity default
A confirmed vulnerability in these categories is CRITICAL or HIGH — it blocks completion and goes back to Codex in the current round, never "noted for later".
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.
- 10d ago First seen · 25 lines · 28 tokens per session scan A 504517ae44b7
review-security is a skill published in the GitHub repository anhnguyen0905/codex-mcp (3 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 434 once invoked, about $0.0001 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…