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/pavelzw/skill-forge/presentation-designnpx skills add pavelzw/skill-forge --skill presentation-designgit clone --depth 1 https://github.com/pavelzw/skill-forgeWrote 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/pavelzw/skill-forge/presentation-design)<a href="https://agentmods.dev/skills/pavelzw/skill-forge/presentation-design"><img src="https://agentmods.dev/badge/skills/pavelzw/skill-forge/presentation-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.00055 | $0.01053 |
| Opus 5 | $0.00028 | $0.00526 |
| Sonnet 5 | $0.00011 | $0.00211 |
| Haiku 4.5 | $0.00006 | $0.00105 |
Grade A, and why
presentation-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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Presentation Slide Design Guidelines
These guidelines apply to all presentation tools and formats.
1. Outline First — Mandatory
You MUST draft a structured outline before creating any slides. Do NOT skip this step. A presentation is a narrative, not a document. Write a markdown outline that captures:
- The core message — one sentence the audience should remember
- The narrative arc — setup, tension/problem, resolution/insight, takeaway
- Key transitions between sections
Present this outline to the human and wait for approval before proceeding. Do not create slides until the human has reviewed and approved the outline. Adapt the structure to fit the topic — there is no single correct format. Example:
# Outline: [Presentation Title]
**Core message:** [One sentence]
## 1. Opening — Hook
- [Surprising fact, question, or story]
## 2. Problem / Context
- [What challenge are we addressing?]
## 3. Key Insight / Solution
- [Main idea, 2-3 sub-points]
## 4. Evidence / Demo
- [Data, examples, or demonstration]
## 5. Takeaway / Call to Action
- [What should the audience do or remember?]
2. Minimize Text — Ruthlessly
Slides are a visual aid, not a script. The presenter speaks; slides support.
Absolute maximum: 10 words per slide. The best slides have zero to three words. Headlines and short phrases only — never sentences. If you need full sentences, put them in speaker notes.
Use short headlines that state the takeaway, not a topic label.
- Weak: "Q3 Sales Results"
- Strong: "Sales up 40%"
Never put paragraphs or long bullet lists on slides. If a slide has more than two lines of text, rethink it.
One idea per slide. If a slide makes two points, split it.
3. Visuals Over Text
Show, don't tell. Images, diagrams, and charts communicate faster than words. When you can replace text with a visual, always do it.
Use full-bleed images. If a slide has one image, it should fill the entire slide. A small centered image with empty space looks unfinished. Use overlay text sparingly.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 99 lines · 55 tokens per session scan A 301f24f27c14
presentation-design is a skill published in the GitHub repository pavelzw/skill-forge (24 stars, last pushed today), licensed BSD-3-Clause. It adds 55 tokens to every session and 1,053 once invoked, about $0.0003 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…