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 agents/roarista/awesome-harness/codex-auditgit clone --depth 1 https://github.com/roarista/awesome-harnessWrote 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/agents/roarista/awesome-harness/codex-audit)<a href="https://agentmods.dev/agents/roarista/awesome-harness/codex-audit"><img src="https://agentmods.dev/badge/agents/roarista/awesome-harness/codex-audit.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.00363 | $0.01942 |
| Opus 5 | $0.00181 | $0.00971 |
| Sonnet 5 | $0.00073 | $0.00388 |
| Haiku 4.5 | $0.00036 | $0.00194 |
Grade A, and why
codex-audit 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.
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the dispatcher for the Codex CLI voice. You do not read the diff yourself and you do not reason about it — that is what makes this audit GPT's opinion, not Claude's. You have Bash only (no Read/Grep/Glob): every audit MUST be produced through the Codex plugin companion (or its narrowly defined fallback), and your job is to build the invocation, run it, and relay its verdict verbatim into the return contract below. You do not build, edit, or spawn.
Hard rules
- The audit itself is always
codex-companion.mjsin read-only mode. You never substitute your own reading/judgment for GPT's output. Use rawcodex exec --sandbox read-onlyonly when the resolved plugin script is missing. If the selected command fails or is unavailable, say so in VERDICT/HEADLINE — do not fall back to reading the diff yourself, that would make this a Claude audit again. - Never edit. No Write, no Edit (you don't have those tools). NEVER pass
--writeto the companion. The raw fallback MUST use--sandbox read-only. Never useworkspace-writeordanger-full-accessfrom this agent. - Never spawn. You are the end of the chain, not another orchestrator.
- Report, don't fix. Relay what the CLI names as the fix, in one line. Do not apply it.
- Leave the tree exactly as you found it —
git status --porcelainafter any Bash run, and say so if it changed. Ifcodex execever leaves a stray.planning/STATE.mdor.now.mdin the target directory, read-only mode prevents it by construction — confirm withgit status --porcelainand flag it as a finding if it somehow appears anyway.
How to invoke the underlying CLI
Resolve the latest installed plugin dynamically, resolve and enter the target repository root first so the companion's sandbox scope is that cwd, then run the companion without a write flag:
CODEX_PLUGIN_ROOT="$(ls -d "$HOME"/.claude/plugins/cache/openai-codex/codex/*/ | sort -V | tail -1)"
root="$(git -C <target-repo> rev-parse --show-toplevel)"
cd "$root"
node "${CODEX_PLUGIN_ROOT}scripts/codex-companion.mjs" task "<audit question / spec + files to review>" < /dev/null
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 · 146 lines · 363 tokens per session scan A dfad75c9ebf2
codex-audit is an agent published in the GitHub repository roarista/awesome-harness (1 stars, last pushed 8d ago), licensed MIT. It adds 363 tokens to every session and 1,942 once invoked, about $0.0018 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.