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-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/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-verification"><img src="https://agentmods.dev/badge/skills/nexu-io/codex-slides/codex-slides-verification.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.00066 | $0.00394 |
| Opus 5.5 | $0.00026 | $0.00158 |
| Sonnet 5.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 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.
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.
- 1mo 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 (951 stars, last pushed 3mo ago), licensed MIT. It adds 66 tokens to every session and 394 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
qa
Browser-based QA verification. Launches a real browser, navigates the app, clicks buttons, fills forms, and tests user flows. Works as a standalone skill or as a phase end condition in campaigns. Requires Playwright (optional dependency, graceful skip if not installed).
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.
test-gen
Generate and verify tests — happy path, edge cases, error paths — using the project's own framework and patterns.
verify
Self-test the Citadel hook pipeline from within a live session. Exercises real tool calls (Write, Edit, Bash, Read) and checks that hooks fired, telemetry accumulated, and no errors occurred. Reports HOOK HEALTH: PASS or HOOK HEALTH: FAIL with a per-hook breakdown.
execute
Dispatch and execute implementation plans with TDD and checkpoints. Use when plan is ready. Parallel by default for independent tasks.
smoke-check
Run the critical path smoke test gate before QA hand-off. Executes the automated test suite, verifies core functionality, and produces a PASS/FAIL report. Run after a sprint's stories are implemented and before manual QA begins. A failed smoke check means the build is not ready for QA.