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 thewolffish/wolffish-app --skill presentationgit clone --depth 1 https://github.com/thewolffish/wolffish-appWrote 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/thewolffish/wolffish-app/presentation)<a href="https://agentmods.dev/skills/thewolffish/wolffish-app/presentation"><img src="https://agentmods.dev/badge/skills/thewolffish/wolffish-app/presentation/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/thewolffish/wolffish-app/presentation"><img src="https://agentmods.dev/badge/skills/thewolffish/wolffish-app/presentation.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.00045 | $0.01696 |
| Opus 5.5 | $0.00018 | $0.00678 |
| Sonnet 5.5 | $0.00009 | $0.00339 |
| Haiku 4.5 | $0.00005 | $0.00170 |
Grade A, and why
presentation 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 29d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Presentation
Interface
- Tools:
deck_design,presentation_read,presentation_create,presentation_modify,presentation_validate,presentation_render. - Formats:
.pptxand.potxfor reading and editing;.pptxfor output. - All complex parameters are passed as JSON strings. All paths absolute.
The shape of this capability
Two halves that meet in the middle.
The layout engine (presentation_create) inverts the usual arrangement. Most pptx
tooling hands the model a canvas and lets it place shapes, which is how decks end up
with drifting margins, ten greys and text running off the slide — none of which the
model can see. Here the model picks a layout per slide and supplies content;
geometry, type scale and palette belong to the engine. The guardrails that matter live
in code, not in prose: colour is normalised (a leading # or an alpha channel corrupts
a pptx rather than erroring), the canvas is defined explicitly (the library's stock
16:9 is 10 inches wide and silently drops anything past the edge), and every option
object is rebuilt per call because the library mutates them in place.
The OOXML path (read/modify/validate) works on decks the engine did not make
— client decks, templates, anything already on disk. It edits the package as text and
touches nothing it did not mean to; round-tripping OOXML through a generic XML parser
rewrites namespace prefixes and produces a file PowerPoint refuses.
Palettes are the eight contrast-tested themes from pdf-design/themes.md, so a deck
and its companion report come out of one colour system.
Rules
- Call
deck_designbefore writing a spec. The manual is the difference between a deck and a bulleted dump. presentation_validateon every deck before it is sent — including ones the engine made.- Render and look before claiming a deck is done. If LibreOffice is missing, say in your reply that you verified structure and content but could not see the slides.
- Read a deck before editing it.
replace_textis exact-match and reports zero hits rather than guessing. - A deck the user will read alone, not present, is usually a document — offer
pdf_designinstead.
What ships with it
3 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.
- 29d ago First seen · 146 lines · 45 tokens per session scan A 98f867f021a0
presentation is a skill published in the GitHub repository thewolffish/wolffish-app (5 stars, last pushed 17d ago), licensed MIT. It adds 45 tokens to every session and 1,696 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-09-17.
Other skills, from other repositories
figma-generate-design
Use this skill alongside figma-use when the task involves translating an application page, view, or multi-section layout into Figma. Triggers: 'write to Figma', 'create in Figma from code', 'push page to Figma', 'take this app/page and build it in Figma', 'create a screen', 'build a landing page in Figma', 'update the…
figma-code-connect-components
Connects Figma design components to code components using Code Connect mapping tools. Use when user says "code connect", "connect this component to code", "map this component", "link component to code", "create code connect mapping", or wants to establish mappings between Figma designs and code implementations. For…
figma-create-design-system-rules
Generates custom design system rules for the user's codebase. Use when user says "create design system rules", "generate rules for my project", "set up design rules", "customize design system guidelines", or wants to establish project-specific conventions for Figma-to-code workflows. Requires Figma MCP server…
figma-generate-library
Build or update a professional-grade design system in Figma from a codebase. Use when the user wants to create variables/tokens, build component libraries, set up theming (light/dark modes), document foundations, or reconcile gaps between code and Figma. This skill teaches WHAT to build and in WHAT ORDER — it…
figma-implement-design
Translates Figma designs into production-ready application code with 1:1 visual fidelity. Use when implementing UI code from Figma files, when user mentions "implement design", "generate code", "implement component", provides Figma URLs, or asks to build components matching Figma specs. For Figma canvas writes via…
edit-figma-design
Create or update Figma designs directly from a written product or UI description using the Figma MCP authoring tools. Use when the user wants a mockup, wireframe, screen, component, flow, or concept designed in Figma from text, or wants to iterate on an existing Figma file from textual feedback. Despite the name, this…