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-structured-intakenpx skills add nexu-io/codex-slides --skill codex-slides-structured-intakegit 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-structured-intake)<a href="https://agentmods.dev/skills/nexu-io/codex-slides/codex-slides-structured-intake"><img src="https://agentmods.dev/badge/skills/nexu-io/codex-slides/codex-slides-structured-intake.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.00059 | $0.00431 |
| Opus 5 | $0.00030 | $0.00216 |
| Sonnet 5 | $0.00012 | $0.00086 |
| Haiku 4.5 | $0.00006 | $0.00043 |
Grade A, and why
codex-slides-structured-intake 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 Structured Intake
The Codex Slides Browser owns the canonical intake form. Structured intake must produce one durable project and one shared clarification state, not a separate chat-only questionnaire.
Flow
- Call
open_codex_slideswithout a project id and follow itsbrowserHandoffto the home/create workspace. - When a workflow preset fits, call
list_scenarios, then open the selected scenario deep link. Use product-owned defaults and source slots. - Submit the user's topic and available files in the Browser. Assign every uploaded file its scenario role; do not flatten datasets, source decks, brand assets, and visual references into one undifferentiated list.
- Let the product create the durable project before clarification. Keep the clarification checkpoint visible and persist answers in project workflow state.
- Ask only questions that materially change the result: audience, purpose, page count, language, aspect, research depth, evidence constraints, and visual direction. Use recommendations already present in the form.
- Continue through outline and inspiration checkpoints in the same Browser
project. Do not call the unattended
create_deckpath unless the user asked for a headless run.
If Browser submission is unavailable, use start_project as the deterministic
fallback, immediately follow its clarification handoff, and keep later choices
attached to that same project id. get_onboarding_questions may help formulate
the intake, but its output is not a second source of truth.
When a durable outline or render job is useful, call start_project_run, keep
its runId, and use wait_project_run or cancel_project_run without closing
the Browser workspace.
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 · 39 lines · 59 tokens per session scan A 54cb0a911e63
codex-slides-structured-intake is a skill published in the GitHub repository nexu-io/codex-slides (869 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 431 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.
marshal
Meta-orchestrator that takes any direction — broad, specific, or vague — and autonomously chains skills and context into actionable work. Gathers context from codebase, docs, and memory. Only asks the user when it genuinely cannot proceed. Single-session orchestrator.