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 bytonylee/future-slide --skill html-slide-plangit clone --depth 1 https://github.com/bytonylee/future-slideWrote 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/bytonylee/future-slide/html-slide-plan)<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/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/bytonylee/future-slide/html-slide-plan"><img src="https://agentmods.dev/badge/skills/bytonylee/future-slide/html-slide-plan.svg" alt="Reviewed on agentmods" width="80" 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.00035 | $0.00257 |
| Opus 5.5 | $0.00014 | $0.00103 |
| Sonnet 5.5 | $0.00007 | $0.00051 |
| Haiku 4.5 | $0.00003 | $0.00026 |
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 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
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.mdas visual constraints. - Prefer layouts that can be built cleanly with semantic HTML and CSS.
- Stop after
slide_plan.jsonunless the user explicitly asks to continue.
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 · 43 lines · 35 tokens per session scan A 1bb843d11bdb
html-slide-plan is a skill published in the GitHub repository bytonylee/future-slide (146 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 35 tokens to every session and 257 once invoked, about $0.0001 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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.