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-researchgit 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-research)<a href="https://agentmods.dev/skills/nexu-io/codex-slides/codex-slides-research"><img src="https://agentmods.dev/badge/skills/nexu-io/codex-slides/codex-slides-research.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.00062 | $0.00454 |
| Opus 5 | $0.00031 | $0.00227 |
| Sonnet 5 | $0.00012 | $0.00091 |
| Haiku 4.5 | $0.00006 | $0.00045 |
Grade A, and why
codex-slides-research 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 7d 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 Research
The canonical codex-slides sibling skill owns the complete workflow. Use
deep_research when MCP is available; otherwise run CLI command research at
../codex-slides/scripts/codex-slides.mjs. Preserve its Markdown and citations
so the user can review or edit the evidence before slide generation.
For the default interactive workflow, first open the Codex Slides home screen in the Codex Browser, submit the research request there, and keep the created project visible while its research, outline, style, and render checkpoints advance. Use the lower-level sequence below only for CLI automation, recovery, or a user-requested headless workflow:
- If a research workflow fits, call
list_scenarios/ CLIscenariosand pass the selectedscenarioIdintodeep_research/ CLIresearchwith one to four rounds. This carries the scenario's evidence contract into the search brief. - Call
create_outline/ CLIoutlinewithresearchDocset to the reviewed brief. - Revise the draft with
revise_outline/ CLIrevise-outlinewhen needed. - Call
render_deck/ CLIrenderonly after the outline is accepted. - Call
open_codex_slides/ CLIopenand navigate the returned project resource or URL in the in-editor Browser for visual verification.
For an explicitly requested unattended fast path, call create_deck with
research: true. Do not claim a brief is source-backed when its returned
Markdown has no source links.
For a durable outline revision or render that should survive navigation, use
start_project_run, then retain and track its runId while the Browser remains
on the matching checkpoint.
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.
- 7d ago First seen · 36 lines · 62 tokens per session scan A 439731f12b61
codex-slides-research is a skill published in the GitHub repository nexu-io/codex-slides (870 stars, last pushed 1mo ago), licensed MIT. It adds 62 tokens to every session and 454 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
A tool for creating presentation slides as high-resolution images and packaging them into a 16:9 PowerPoint file. It turns a Markdown outline or slide plan into a styled deck using OpenAI image generation.
high-quality-slides
A method for creating polished presentation slides, including HTML slide decks, with research, a clear story, chosen visuals, and fixed layouts.
oh-my-ppt-layout
Must be read before creating, relaying out, or repairing Oh My PPT slide layouts. Defines the per-page decision path, the named layout pattern catalog, canvas budgeting, collision avoidance, chart overpack guardrails, and title readability rules.
oh-my-ppt-data-anim
Must be read before adding or modifying Oh My PPT slide animations. Defines exportable data-anim usage, trigger decisions, and how to replace unsupported scripted/anime.js animation.
oh-my-ppt-source-reading
Source-document reading workflow for Oh My PPT. Read before generating slides from reference documents or retrieved snippets.
vertical-3-4-layout-skill
Must be read before creating, relaying out, or repairing 3:4 vertical Oh My PPT pages. Defines poster-card layout, focal hierarchy, vertical section planning, evidence grouping, compact two-column pockets, chart/list budgeting, plus catalog and checklist references for 1200x1600 canvases.