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 vsladkov/claudex-stereo --skill codex-result-handlinggit clone --depth 1 https://github.com/vsladkov/claudex-stereoWrote 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/vsladkov/claudex-stereo/codex-result-handling)<a href="https://agentmods.dev/skills/vsladkov/claudex-stereo/codex-result-handling"><img src="https://agentmods.dev/badge/skills/vsladkov/claudex-stereo/codex-result-handling/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/vsladkov/claudex-stereo/codex-result-handling"><img src="https://agentmods.dev/badge/skills/vsladkov/claudex-stereo/codex-result-handling.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.00031 | $0.00399 |
| Opus 5.5 | $0.00012 | $0.00160 |
| Sonnet 5.5 | $0.00006 | $0.00080 |
| Haiku 4.5 | $0.00003 | $0.00040 |
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 28d 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.
This is a copy
94% identical to codex-result-handling — 20 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Codex Result Handling
When the helper returns companion output (Codex or Claude):
- Preserve the helper's verdict, summary, findings, and next steps structure.
- For review output, present findings first and keep them ordered by severity.
- Use the file paths and line numbers exactly as the helper reports them.
- Preserve evidence boundaries. If the model marked something as an inference, uncertainty, or follow-up question, keep that distinction.
- Preserve output sections when the prompt asked for them, such as observed facts, inferences, open questions, touched files, or next steps.
- Preserve any
Warnings:section and its file paths verbatim. - If there are no findings, say that explicitly and keep the residual-risk note brief.
- If the run made edits, say so explicitly and list the touched files when the helper provides them.
- For
stereo:codex-rescue, do not turn a failed or incomplete Codex run into a Claude-side implementation attempt. Report the failure and stop. - For
stereo:codex-rescue, if Codex was never successfully invoked, do not generate a substitute answer at all. - After presenting review findings, stop: a review reports, and the user chooses what gets fixed. Ask which issues to fix before touching a file, even when a fix looks obvious.
- If the helper reports malformed output (
The reviewer did not return valid structured JSON.,The run did not return a final message.) or a failed companion run, Codex or Claude, include the most actionable stderr lines and stop there instead of guessing. - If the helper reports that setup or authentication is required, direct the user to
/stereo:setupand do not improvise alternate auth flows.
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.
- 28d ago Changed · +13 tokens per session 1613b58e2eb0
- 1mo ago First seen · 24 lines · 18 tokens per session scan A 6f30b3fe29a6
codex-result-handling is a skill published in the GitHub repository vsladkov/claudex-stereo (5 stars, last pushed 28d ago), licensed Apache-2.0. It adds 31 tokens to every session and 399 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to codex-result-handling, differing in 20 lines, and is treated as a copy.
Other skills, from other repositories
goal-test
A local experiment for testing a goal command that keeps an AI coding session working until a stated condition is judged complete. It uses a separate language model to evaluate the conversation after each assistant turn.
loop-test
A local experiment for designing repeating checks with Claude Code’s loop command. It covers both fixed intervals and checks that schedule themselves again after each run.
commit
A guided process for committing code changes to Git. It checks the working tree, follows a conventional commit format, links a task when available, reviews the changes, and asks for approval.
create-task
This skill should be used when creating a task in the active tracker - "create task", "create issue", "bd create", "new task", "add task", "add issue". Ensures all required fields are provided, enforces English-only task content, and suggests epic labels. Triggers on any task creation in any context - commands…
session-boundary
Internal skill for commands. Resolve and VALIDATE this branch's session boundary - the ref a session's commit range is measured from - and report how much it can be trusted. Do not trigger on user conversation; only when a command needs the session range.
loop-gh-pr
A recipe for a scheduled GitHub pull-request watcher. It checks open pull requests for new activity and prepares read-only review drafts without posting comments or merging anything.