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/okisdev/claude-code-fusion/codex-result-handlingnpx skills add okisdev/claude-code-fusion --skill codex-result-handlinggit clone --depth 1 https://github.com/okisdev/claude-code-fusionWrote 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/okisdev/claude-code-fusion/codex-result-handling)<a href="https://agentmods.dev/skills/okisdev/claude-code-fusion/codex-result-handling"><img src="https://agentmods.dev/badge/skills/okisdev/claude-code-fusion/codex-result-handling.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.00017 | $0.00288 |
| Opus 5 | $0.00009 | $0.00144 |
| Sonnet 5 | $0.00003 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
codex-result-handling 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 4d 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
Codex result handling
- Return companion stdout verbatim. Do not summarize, paraphrase, reformat, prefix, or suffix it.
- Preserve the complete result, file paths, line numbers, Codex thread identifier, job identifier, delivery mode, semantic status, and
state: done,state: error, orstate: cancelledfooter. Preserve the failure kind for error and cancelled outcomes. A transportstate: donewithsemantic: rejectedis not a successful deliverable. - Preserve
state: runningwhen an explicit background launch or bounded wait has not reached a terminal outcome. Do not present a receipt as completed work. - A timeout result whose body carries a
Resume Codex jobline authorizes exactly one scripted resume with the wind down prompt named by the agent contract; return the resumed companion output verbatim. No other state authorizes a second companion call, and a resume never repeats. - Do not inspect the repository, verify findings, apply edits, poll unrelated jobs, or continue the task after returning the companion output.
- Do not replace a failed, cancelled, malformed, or incomplete Codex run with a Claude-side answer.
- If the helper cannot be invoked, return the invocation failure exactly as reported and stop.
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.
- 4d ago First seen · 16 lines · 17 tokens per session scan A cd6c6cbc17d6
codex-result-handling is a skill published in the GitHub repository okisdev/claude-code-fusion (3 stars, last pushed 16d ago), licensed MIT. It adds 17 tokens to every session and 288 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
diagram-builder
Use when the user wants to build or extend a diagram deck of nested sections and components authored in plain YAML — an architecture map, a timeline diagram, a planner board, a process-flow diagram, a slide-style presentation, a side-by-side comparison, or a mind-map. Not for charts, plots, or numeric/data…
gaia-release
Use when testing, validating, or publishing Gaia releases -- "install local", "pre-release", "dry-run", "release", RC, stable, plugin dry-run.
gaia-planner
Use when planning features or decomposing work into tasks from a brief.
gmail-policy
Use when managing Gmail messages, labels, or email workflows via gws CLI or Gmail MCP tools.
brief-spec
Use when the user wants to create a brief or spec for a feature before planning.
skill-creation
Use when creating a new skill, improving an existing skill, or deciding what a skill should contain and how it should be structured.