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/nexu-io/codex-slides/codex-slides-verificationnpx skills add nexu-io/codex-slides --skill codex-slides-verificationgit 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-verification)<a href="https://agentmods.dev/skills/nexu-io/codex-slides/codex-slides-verification"><img src="https://agentmods.dev/badge/skills/nexu-io/codex-slides/codex-slides-verification.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.1 | $0.00066 | $0.00394 |
| Opus 5 | $0.00033 | $0.00197 |
| Sonnet 5 | $0.00013 | $0.00079 |
| Haiku 4.5 | $0.00007 | $0.00039 |
Grade A, and why
codex-slides-verification 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 6d 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 Slides Verification
Use two signals before reporting a presentation task complete:
- Read canonical project state with
get_project, and read a named durable job withget_project_runorwait_project_runwhen arunIdwas returned. - Follow the returned
browserHandoffand inspect the exact visible result in the Codex in-editor Browser.
Verification sequence
- Confirm the project id rather than guessing from a similar title.
- For a durable run, require a terminal
completestatus. Treaterrorandcancelledas incomplete; a timed-out wait leaves the run active. - Confirm the expected page count, changed slide indexes, rendered images, transitions, speaker notes, current workflow stage, and current deck version.
- Open the exact handoff returned by the mutation. Preserve its
slide,panel,version,mode,conversation,checkpoint, andrunquery parameters. - In Browser, confirm the intended slide or panel is focused and the visible result matches the request. Do not treat a JSON response alone as visual QA.
- Export only after the current or explicitly selected version passes review.
If the in-editor Browser is unavailable, use the project state and persisted slide-image endpoints as structural evidence, return the exact handoff URL, and state that visible Browser verification remains outstanding.
For cross-surface changes, also verify that refreshing or reopening the same project preserves the run result and deep-link focus.
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.
- 6d ago First seen · 35 lines · 66 tokens per session scan A d53746fa3169
codex-slides-verification is a skill published in the GitHub repository nexu-io/codex-slides (869 stars, last pushed 1mo ago), licensed MIT. It adds 66 tokens to every session and 394 once invoked, about $0.0003 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-30.
Other skills, from other repositories
gpt-image2-ppt
Generate visually striking PPT slides via OpenAI's gpt-image-2 -- use any style in styles/ /STYLEID.md or mimic a user-supplied .pptx template; outputs high-res slide PNGs and a 16:9 .pptx. Use when the user asks to make a presentation, slides, deck, pitch deck, investor PPT, magazine-style PPT, or 做一份 PPT / 生成幻灯片 / 用…
high-quality-slides
Use this skill when the user asks for a "high-quality" / "professional" / "Genspark-style" / "投资人级别" / "演示级" deck, or when they reference Genspark, Gamma, beautiful HTML slides, or pixel-perfect presentations. Trigger on requests like "做一份PPT", "生成幻灯片", "pitch deck", "做汇报", or when the user uploads research material…
oh-my-ppt-chart
Must be read before adding or modifying Oh My PPT slide charts. Defines chart-selection rules, product-safe Chart.js usage, canvas layout constraints, axis label rules, and retry fixes.
watch
File sentinel that monitors the working directory for changes and marker comments, then auto-triggers appropriate skills. Poll-based via git diff against the last scan commit. Writes intake items for batch processing and routes marker actions through /do. Use for automatic reactions to file changes; do NOT use for…
review
5-pass structured code review — correctness, security, performance, readability, consistency.
live-preview
Mid-build visual verification loop. Takes screenshots of components during construction, not just after. Catches visual regressions and invisible features before they compound. Requires Playwright or similar screenshot tool.