html-slide-plan

html-slide-plan is a skill for Claude Code, Codex from bytonylee/future-slide. It costs 35 tokens per session (257 once invoked), scanned A, original, Apache-2.0.

A planning step for deciding the story, order, content, and layout of each slide in an HTML deck. HTML slides are presentations built with web-page files that can be edited like a website.

In plain words
What is it for?
Use it to create a slide_plan.json file containing deck metadata, content mapping, the story arc, and implementation guidance for every slide.
Why use it?
It settles the structure before coding, helping prevent missing evidence, weak slide order, or layouts that are difficult to build with HTML and CSS.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/bytonylee/future-slide/html-slide-plan
Any agent
npx skills add bytonylee/future-slide --skill html-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 html-slide-plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/bytonylee/future-slide/html-slide-plan.svg)](https://agentmods.dev/skills/bytonylee/future-slide/html-slide-plan)
Your own site
<a href="https://agentmods.dev/skills/bytonylee/future-slide/html-slide-plan"><img src="https://agentmods.dev/badge/skills/bytonylee/future-slide/html-slide-plan.svg" alt="Measured on agentmods" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 257 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00035 $0.00257
Opus 5 $0.00017 $0.00129
Sonnet 5 $0.00007 $0.00051
Haiku 4.5 $0.00003 $0.00026

Measured 5d ago against content hash 1bb843d11bdb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

html-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 5d 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/html-slide-plan/SKILL.md · 43 lines

What it actually says

HTML Slide Plan

Use this skill for commands like:

  • $html-slide-plan
  • "plan the HTML slide deck"
  • "create slide_plan.json for web slides"
  • "decide slide order before implementation"

Goal

Create slide_plan.json: the deck story, slide order, content mapping, and HTML-friendly layout direction for each page.

Inputs

  • DESIGN.md
  • user files or source material
  • user deck goal, audience, language, and constraints

Required Output

Return valid JSON only. Include:

  • deck metadata
  • design dependency
  • content inventory
  • story arc
  • ordered slides
  • per-slide role, page family, core message, evidence, recommended HTML layout, and header/body/footer plan

Hard Rules

  • Do not write HTML yet.
  • Do not create image-generation prompts.
  • Use DESIGN.md as visual constraints.
  • Prefer layouts that can be built cleanly with semantic HTML and CSS.
  • Stop after slide_plan.json unless the user explicitly asks to continue.
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. 5d ago First seen · 43 lines · 35 tokens per session scan A 1bb843d11bdb

Subscribe to this mod's changes

html-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 35 tokens to every session and 257 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens