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 dante01yoon/codex-mcp-bridge --skill codex-reviewgit clone --depth 1 https://github.com/dante01yoon/codex-mcp-bridgeWrote 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/dante01yoon/codex-mcp-bridge/codex-review)<a href="https://agentmods.dev/skills/dante01yoon/codex-mcp-bridge/codex-review"><img src="https://agentmods.dev/badge/skills/dante01yoon/codex-mcp-bridge/codex-review.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.1 | $0.00031 | $0.00257 |
| Opus 5 | $0.00015 | $0.00129 |
| Sonnet 5 | $0.00006 | $0.00051 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
Codex Review 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 8d 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
Review the code specified below using Codex as a sub-agent.
Steps
- Read the target file(s) specified in the arguments. If no file is specified, ask the user.
- Call
mcp__codex-bridge__consult_codex_with_stdinwith:stdin_content: the full content of the target file(s)prompt: "Review this code. Focus on: bugs, security issues, performance problems, and readability. Return a structured list of findings with severity (critical/warning/info), location, and suggested fix."format: "json"timeout: 180sandbox: "read-only"
- Summarize findings, highlighting the most critical issues first.
$ARGUMENTS
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.
- 8d ago First seen · 28 lines · 31 tokens per session scan A 7f955a12dad3
Codex Review is a skill published in the GitHub repository dante01yoon/codex-mcp-bridge (2 stars, last pushed 6mo ago), licensed MIT. It adds 31 tokens to every session and 257 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
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…