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 nexu-io/codex-slides --skill codex-slides-known-errorsgit clone --depth 1 https://github.com/nexu-io/codex-slidesWrote 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/nexu-io/codex-slides/codex-slides-known-errors)<a href="https://agentmods.dev/skills/nexu-io/codex-slides/codex-slides-known-errors"><img src="https://agentmods.dev/badge/skills/nexu-io/codex-slides/codex-slides-known-errors/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/nexu-io/codex-slides/codex-slides-known-errors"><img src="https://agentmods.dev/badge/skills/nexu-io/codex-slides/codex-slides-known-errors.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.00067 | $0.00630 |
| Opus 5.5 | $0.00027 | $0.00252 |
| Sonnet 5.5 | $0.00013 | $0.00126 |
| Haiku 4.5 | $0.00007 | $0.00063 |
Grade A, and why
codex-slides-known-errors 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Slides Known Errors
Classify the failure before retrying. Preserve the same project id and run id; do not recreate a deck merely because a Browser tab closed or a wait timed out.
Runtime and installation
- Plugin version contract fails:
.codex-plugin/plugin.jsonmust start with the exact rootpackage.jsonversion plus+codex.. The desktop package must use the same product version. - App is unreachable: inspect
CODEX_SLIDES_URLandCODEX_SLIDES_LOG. The local MCP launcher may need to prepare dependencies or a standalone build. - Installed skill or tool inventory looks stale: reinstall/upgrade the plugin and start a new Codex task so the versioned plugin cache is refreshed.
Durable runs
- Another run is active: inspect it with
get_project_run. Wait, cancel it explicitly, or allow a Deck Agent request to remain in the visible queue. - Wait timed out: the run was not cancelled. Continue with
wait_project_runor reopen itsbrowserHandoff. - Run id is missing after completion: this indicates an old runtime without
terminal
runHistory; refresh the plugin/runtime before retrying the task. - Run is stopping: do not start a conflicting render. Poll until it becomes
cancelled, then continue.
Browser handoff and project resume
- Use the exact returned
browserHandoff.url; do not reconstruct a project URL. - Keep all focus parameters:
slide,panel,version,mode,checkpoint,conversation, andrun. - A clarify/research project may route through
/?resume=<id>. The continuation query must survive that redirect. - Presenter mode needs a user gesture for its second window. A presenter deep link opens the Play menu at the correct slide instead of bypassing popup protection.
Rendering and project state
- A partially rendered or paused deck is resumable. Read the project and start
a durable
renderrun for the existing project. - If Codex state and Browser state differ, read
/runs/get_projectas the canonical snapshot, then reload the same Browser handoff. - Do not report success for slides whose status is
erroror whose persisted image cannot be loaded.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 58 lines · 67 tokens per session scan A 9914adcac0d8
codex-slides-known-errors is a skill published in the GitHub repository nexu-io/codex-slides (951 stars, last pushed 3mo ago), licensed MIT. It adds 67 tokens to every session and 630 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
postmortem
Auto-generates a structured postmortem from a completed campaign. Reads the campaign file, telemetry logs, and feature ledger. Produces a documented analysis of what broke, what the safety systems caught, and what patterns emerged. Can also be invoked manually for any incident.
systematic-debugging
4-phase root cause analysis: observe, hypothesize, verify, fix. Enforces investigation before any code changes. Emergency stop after 2 failed fixes. Prevents shotgun debugging and fix cascades.
superloopy-doctor
Use when diagnosing Superloopy doctor, install, wrapper, plugin cache, hook bootstrap, bundled agents, marketplace, Codex, Claude Code, stale-version, evidence-floor, or host-wiring health problems.
ambient-project
Quietly maintain a useful project view from meaningful work in the current Codex session. Use when work creates a task, bug, decision, idea, risk, milestone, plan, progress update, or explicit completion.
zapier-status
Check the health of your Zapier MCP setup. Three modes — health check (dashboard view), audit (find waste and duplicates), diagnose (systematic troubleshooting). Use when asking "is my MCP working?", "check my tools", "audit my setup", "what's broken?", or "zapier status".
serena
Serena code intelligence — LSP-powered symbol navigation, diagnostics, and targeted code surgery. Activate before complex refactors, cross-file analysis, or when graph tools need symbol-level depth.