gpt-image-slide-plan

gpt-image-slide-plan is a skill for Claude Code, Codex from bytonylee/future-slide. It costs 44 tokens per session (2,261 once invoked), scanned A, original, Apache-2.0.

A presentation-planning workflow that decides a deck’s page order, length, evidence placement, and narrative flow before slide prompts are written.

In plain words
What is it for?
Use it to turn a design guide, user files, and a presentation objective into a structured slide plan in JSON.
Why use it?
It prevents a presentation from becoming a collection of disconnected slides and keeps the content aligned with the audience and goal.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to turn a design guide, user files, and a presentation objective into a structured slide plan in JSON.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/bytonylee/future-slide/gpt-image-slide-plan
Install

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.

Any agent
npx skills add bytonylee/future-slide --skill gpt-image-slide-plan
Clone the repo
git clone --depth 1 https://github.com/bytonylee/future-slide

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for gpt-image-slide-plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/bytonylee/future-slide/gpt-image-slide-plan/github.svg)](https://agentmods.dev/skills/bytonylee/future-slide/gpt-image-slide-plan)
Your own site
<a href="https://agentmods.dev/skills/bytonylee/future-slide/gpt-image-slide-plan"><img src="https://agentmods.dev/badge/skills/bytonylee/future-slide/gpt-image-slide-plan/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.

agentmods 80×15 button for gpt-image-slide-plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/bytonylee/future-slide/gpt-image-slide-plan"><img src="https://agentmods.dev/badge/skills/bytonylee/future-slide/gpt-image-slide-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,261 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00044 $0.02261
Opus 5 $0.00022 $0.01130
Sonnet 5 $0.00009 $0.00452
Haiku 4.5 $0.00004 $0.00226

Measured 10d ago against content hash 6688d27f565b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

gpt-image-slide-plan 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 10d 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.

skills/gpt-image-slide-plan/SKILL.md · 277 lines

How it starts

The opening of the file, as written. The whole thing — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GPT IMAGE SLIDE PLAN — BUILD THE DECK LOGIC BEFORE WRITING SLIDE PROMPTS

You are a presentation strategist. Your job is to decide what the deck should say, in what order, and why.

You must use:

  • the extracted DESIGN.md as the visual constraint system
  • the user prompt as the objective and audience
  • the user's files as the evidence and content pool

You are forbidden from jumping straight to page-level slide prompts. First decide the deck structure.

Planning objective

Create a slide sequence that is:

  • natural
  • persuasive
  • logically progressive
  • audience-aware
  • evidence-backed
  • compatible with the extracted design system

The quality of this step determines whether the final PPT feels coherent or random.

What this step is NOT

  • not a visual design extraction step
  • not a detailed slide-rendering step
  • not a file dump
  • not a summary of every uploaded document

This is a story architecture step.

It is also a page-system architecture step. You are deciding not only what the deck says, but how the deck should distribute information across title pages, body pages, and end pages using the layout rules extracted in DESIGN.md.

Decision rules for ordering

Build the deck using persuasive narrative logic, not file upload order.

Use a sequence like this when appropriate:

  1. context / framing
  2. problem or opportunity
  3. key insight
  4. supporting evidence
  5. implications
  6. options / solution / recommendation
  7. roadmap / next steps
  8. closing ask or summary

Adapt the sequence to the deck type:

  • investor deck
  • strategy deck
  • research summary
  • sales deck
  • internal update
  • proposal
  • workshop recap
  • board deck
  • educational deck

Also plan the page-family rhythm:

  • title / opener page
  • body pages
  • end / summary / CTA page

Do not treat every page as an interchangeable body slide. The opener, interior slides, and end page should each have a distinct job in the narrative.

Content clustering rules

When many files are given:

  • cluster them by theme, not by filename
  • identify overlaps, contradictions, and priority evidence
  • choose only the strongest evidence for each slide
  • merge weak adjacent slides if they dilute the story

Read the full file on GitHub · 277 lines

Changes

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.

  1. 10d ago First seen · 277 lines · 44 tokens per session scan A 6688d27f565b

Subscribe to this mod's changes

gpt-image-slide-plan is a skill published in the GitHub repository bytonylee/future-slide (146 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 44 tokens to every session and 2,261 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

webgl-holographic-foil

A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.

nexu-io/open-design · 41 tokens

general-video

Author or edit a custom HyperFrames composition when no specialized workflow fits, or when BRIEF.md sets flow: companion. Use for longer or multi-scene pieces, brand and sizzle reels, montages, static loops, static title cards, footage remixes, and freeform builds. Use motion-graphics instead for a short unnarrated…

heygen-com/hyperframes · 92 tokens

html-ppt-hermes-cyber-terminal

OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.

nexu-io/open-design · 53 tokens

html-ppt-taste-brutalist

16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).

nexu-io/open-design · 78 tokens

diagnostic-stem-delivery

Audio production with diagnostic analysis, timecode parsing from documents, and verified export workflow.

HKUDS/OpenSpace · 23 tokens

chengfeng-check-updates

An environment manager for a video-editing system. It checks whether its skills and runtime—the software needed to run them—are installed and compatible.

Agentchengfeng/chengfeng-videocut-skills · 120 tokens