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-rendergit 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-render)<a href="https://agentmods.dev/skills/bytonylee/future-slide/html-slide-render"><img src="https://agentmods.dev/badge/skills/bytonylee/future-slide/html-slide-render/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-render"><img src="https://agentmods.dev/badge/skills/bytonylee/future-slide/html-slide-render.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.00038 | $0.00330 |
| Opus 5.5 | $0.00015 | $0.00132 |
| Sonnet 5.5 | $0.00008 | $0.00066 |
| Haiku 4.5 | $0.00004 | $0.00033 |
Grade A, and why
html-slide-render 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 Render
Use this skill for commands like:
$html-slide-render- "build the HTML deck"
- "render the slides as HTML"
- "implement html_slide_prompts.json"
Goal
Build an editable browser-rendered slide deck from the planned design and prompts.
Inputs
DESIGN.mdslide_plan.jsonhtml_slide_prompts.json
Default Output
Create a project-local folder such as:
slides-html/
├── index.html
├── styles.css
├── slides.js
└── assets/
Use a simpler single-file index.html only when the user asks for a portable standalone artifact.
Implementation Rules
- Build actual slides as the first screen, not a landing page.
- Preserve the extracted design system.
- Use stable 16:9 slide dimensions unless the user specifies another format.
- Use semantic HTML for slide content.
- Keep CSS tokens readable and centralized.
- Use SVG, CSS, or chart libraries only when they improve the slide content.
- Keep text legible and prevent overflow.
- Verify in a browser when possible.
Hard Rules
- Do not use Codex native image generation as the primary renderer.
- Do not collapse dense analytical slides into generic card grids.
- Do not leave generated assets outside the workspace.
- Report the final HTML entry path and any verification performed.
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 · 56 lines · 38 tokens per session scan A 5bbc1ad2f6ff
html-slide-render is a skill published in the GitHub repository bytonylee/future-slide (146 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 38 tokens to every session and 330 once invoked, about $0.0002 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.