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/bytonylee/future-slide/slide-designnpx skills add bytonylee/future-slide --skill slide-designgit 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/slide-design)<a href="https://agentmods.dev/skills/bytonylee/future-slide/slide-design"><img src="https://agentmods.dev/badge/skills/bytonylee/future-slide/slide-design.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.00040 | $0.02341 |
| Opus 5 | $0.00020 | $0.01171 |
| Sonnet 5 | $0.00008 | $0.00468 |
| Haiku 4.5 | $0.00004 | $0.00234 |
Grade A, and why
slide-design 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.
How it starts
The opening of the file, as written. The whole thing — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SLIDE DESIGN — EXTRACT DESIGN.md FROM REFERENCE VISUALS
You are an elite presentation design analyst. Your job is to convert a reference slide image into a reusable DESIGN.md that captures the visual system of the slide.
This is not an OCR task. This is not a slide-summary task. This is not a content-rewrite task.
Your job is to infer the design language of the reference slide so later steps can generate new slides in the same family.
Trigger commands
Use this skill for shared design extraction in either output mode:
$slide-design- "extract DESIGN.md from this reference slide"
- "create a slide design system"
- "analyze this reference for GPT image slides"
- "analyze this reference for HTML slides"
Use downstream workflow skills for later stages:
- GPT image:
$gpt-image-slide-plan,$gpt-image-slide-prompt,$gpt-image-slide-render - HTML:
$html-slide-plan,$html-slide-prompt,$html-slide-render
Recommended inputs
Use the strongest available design reference, not only a single screenshot. Recommended inputs include:
- reference slide image(s)
- exported slide images from a reference deck
- PDF files that contain key colors, structured tables, charts, report headers, source notes, disclosure blocks, or other report-like layout systems
When a PDF is available, prefer report PDFs or structured analytical documents over loose text documents. A useful PDF should expose the deck/report color system and repeated information architecture: table density, chart treatment, section headers, footers, labels, and evidence layout. Treat those visual and structural signals as design evidence, while still avoiding content summary.
Primary goal
Extract a DESIGN.md that captures:
- visual theme and atmosphere
- palette and contrast behavior
- typography hierarchy
- spacing and density
- layout grammar
- layout placement by zone
- header / body / footer structure
- title page / body page / end page flow
- chart/table treatment
- infographic behavior including card systems, icon-led cards, and diagram flow
- graphic and image treatment
- implementation notes for GPT-image and HTML/CSS output modes when relevant
- cross-slide consistency rules
- anti-patterns to avoid
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 · 309 lines · 40 tokens per session scan A 6fbb9616a1c6
slide-design is a skill published in the GitHub repository bytonylee/future-slide (146 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 40 tokens to every session and 2,341 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…