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 Sateezg/codex-bridge --skill ask-codexgit clone --depth 1 https://github.com/Sateezg/codex-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/sateezg/codex-bridge/ask-codex)<a href="https://agentmods.dev/skills/sateezg/codex-bridge/ask-codex"><img src="https://agentmods.dev/badge/skills/sateezg/codex-bridge/ask-codex/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/sateezg/codex-bridge/ask-codex"><img src="https://agentmods.dev/badge/skills/sateezg/codex-bridge/ask-codex.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00080 | $0.00655 |
| Opus 5.5 | $0.00032 | $0.00262 |
| Sonnet 5.5 | $0.00016 | $0.00131 |
| Haiku 4.5 | $0.00008 | $0.00065 |
Grade A, and why
ask-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 1mo 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ask Codex a question
For a single question with a single answer. Anything multi-step or long-running
belongs to a subagent (codex-second-opinion, codex-reviewer, codex-debugger).
codex-run -C <repo-dir> "<self-contained question>"
codex-run prints only Codex's final answer on stdout (it captures the final
message via codex exec -o rather than dumping the whole event log). It defaults
to a read-only sandbox, so Codex can read the repo but cannot change anything.
Writing the question
Codex has zero knowledge of this conversation. Every question must stand alone:
- Name the files or directories it should look at.
- State what you already know or already tried.
- Say what shape of answer you want ("name the single most likely cause and the line to look at", "answer yes/no then justify in three sentences").
codex-run -C /path/to/repo \
"In src/auth/session.ts, refreshToken() occasionally returns a token that fails validation immediately. I suspect a clock-skew issue in the exp comparison. Read that file plus src/auth/jwt.ts and tell me the single most likely root cause and the exact line. Be concise."
Useful options
-s workspace-write let Codex modify files (only when the user asked for that)
-m gpt-5-codex model override
-r continue the previous codex session (follow-up question)
--timeout 1800 raise the 900s default for a big repo sweep
--raw also print Codex's full event log to stderr, for debugging
Use -r for a genuine follow-up — it keeps Codex's own context and avoids paying
to re-read the repo:
codex-run -C /path/to/repo -r "Now show me the minimal patch for that."
Rules
- Bash timeout ≥ 600000 ms (10 min) — Codex explores the repo before answering.
- Report its answer as Codex's, not as your own conclusion. Quote it, then add your own take separately if you disagree — the value here is having two independent opinions, and blending them destroys that.
- Sanity-check it. Codex can confidently cite files or lines that don't exist. Verify any specific claim against the repo before acting on it.
- Read-only unless told otherwise. Don't pass
-s workspace-writeon your own initiative. - Each call spends the user's ChatGPT plan quota. One question, one call.
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.
- 1mo ago First seen · 60 lines · 80 tokens per session scan A e0388d3de1e8
ask-codex is a skill published in the GitHub repository Sateezg/codex-bridge (247 stars, last pushed 2mo ago), licensed MIT. It adds 80 tokens to every session and 655 once invoked, about $0.0003 per session on Opus 5.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 skills, from other repositories
imagegen
Pre-flight check across ANY project type — websites, landing pages, marketing sites, homepages, portfolios, web/mobile/desktop apps, games (sprites/textures/tiles/character art/enemy rosters/environment art), CLI tools, libraries/SDKs, READMEs, docs, tutorials, blog posts, slide decks, brand/identity work, mockups…
pr-review
Comprehensive PR review across six dimensions — cost impact, environment drift, ownership gaps, SOC 2 compliance, deprecated API / version hygiene, and rollback feasibility. Each mode inspects the diff and current file state, reports findings with severity, and recommends concrete fixes. Use when preparing a PR for…
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
extract-resume
Parse a resume's uploaded PDF into structured JSON (basics, experience, projects, skills, education) and save it to the editor.
ensure-pipelines-host
Ensures the tenant has a usable Power Platform Pipelines host environment before any pipeline operation runs. Detects host state via the same resolution order as the Power Apps UI (org-db setting → BAP env metadata → default-custom-host setting); if any existing host (Platform or Custom) is found, uses it. If no host…
delegate
Let Claude Architect route a versioned implementation spec through the trusted MCP runtime, independently review the Candidate Artifact, record a decision, and integrate only accepted bytes. Use for implementation delegation, Producer selection, or commitment-boundary review.