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/greglas75/zuvo/presentationnpx skills add greglas75/zuvo --skill presentationgit clone --depth 1 https://github.com/greglas75/zuvoWrote 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/greglas75/zuvo/presentation)<a href="https://agentmods.dev/skills/greglas75/zuvo/presentation"><img src="https://agentmods.dev/badge/skills/greglas75/zuvo/presentation.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 | $0.00080 | $0.02262 |
| Opus 5 | $0.00040 | $0.01131 |
| Sonnet 5 | $0.00016 | $0.00452 |
| Haiku 4.5 | $0.00008 | $0.00226 |
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 yesterday.
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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
zuvo:presentation — PowerPoint Generator
Generate professional PPTX presentations from a topic description, outline, or existing content file. Uses python-pptx to produce slides with consistent design, speaker notes, and visual variety.
Requires: python-pptx (pip install python-pptx)
Scope: Generating slide decks from topics or content files. Out of scope: Editing existing PPTX files, complex data visualizations (charts, graphs), image generation.
Run Logging
Read ../../shared/includes/run-logger.md for log format and file path resolution.
Read ../../shared/includes/retrospective.md for log format and file path resolution.
Argument Parsing
| Argument | Behavior |
|---|---|
[topic] |
Plan outline from scratch, generate slides |
from [file] |
Build slides from existing markdown or text file |
--slides N |
Target slide count (default: 10) |
--theme dark|light|corporate |
Color theme (default: corporate) |
--out [path] |
Output path (default: ./[topic-slug].pptx) |
--outline-only |
Generate outline for approval, do not create PPTX |
--lang [code] |
Content language (default: same as topic input) |
Examples:
zuvo:presentation "Q1 2026 Product Review"
zuvo:presentation from docs/architecture.md --slides 8
zuvo:presentation "Security Audit Results" --outline-only
zuvo:presentation "Quarterly Report" --lang pl --theme dark
Phase 1: Content Planning
1.1 Determine Source
| Input | Action |
|---|---|
| Topic string | Plan outline from scratch (1.2) |
from [file] |
Read file, extract sections as slide candidates (1.3) |
1.2 Plan from Topic
Generate a structured outline. Each slide needs:
Slide [N]: [Type]
Title: [slide title]
Content: [bullets or description]
Speaker notes: [optional context]
Slide types:
| Type | Use for |
|---|---|
| TITLE | Opening -- presentation title, subtitle, date |
| SECTION | Section divider -- large title, minimal content |
| CONTENT | Standard -- title + bullet points (max 6 bullets) |
| TWO_COLUMN | Comparison, before/after, pros/cons |
| QUOTE | Key insight, important statement |
| METRICS | Numbers, KPIs, statistics (2-4 big numbers) |
| TIMELINE | Process steps, roadmap, milestones (3-6 items) |
| IMAGE_PLACEHOLDER | Slide with image area + caption (user fills later) |
| SUMMARY | Key takeaways (3-5 points) |
| CLOSING | Thank you, Q&A, contact info |
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.
- yesterday First seen · 255 lines · 80 tokens per session scan A 74dc022bb6e9
presentation is a skill published in the GitHub repository greglas75/zuvo (6 stars, last pushed yesterday), licensed MIT. It adds 80 tokens to every session and 2,262 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
ring:creating-handoffs
Creating a handoff document that captures session state (completed work, decisions, open items, next steps) and delivering it via Plan Mode so the user gets the native 'clear context and continue implementing' resume option. Use when ending a session, when context grows large, or the user says 'handoff', 'save…
test-map
/test-map — Test Cases Documentation Generator.
init
Write or refresh the ## Tech debt operations section in CLAUDE.md so a team shares one source of truth for debt-ops disciplines and cached quality commands. Idempotent. Only the managed section changes; other sections are untouched. Invoked explicitly via /debt-ops:init (solo users get the same content from the…
debt-ops-init
Write or refresh a "Tech debt operations" section in the project's AGENTS.md so the team shares one source of truth for debt-ops disciplines. Run ONLY when the user explicitly asks to set up, install, or initialize debt-ops disciplines — never auto-invoke. Idempotent; only the managed section changes, other sections…
add
Register a deferred decision in the debt registry. Trigger by judgment, not a marker scan, whenever a future reader would ask "why this way?": an unmade decision, stub, loosened type, bypassed check, swallowed error, a default picked "for now", or a TODO/FIXME/HACK/XXX marker. Trigger immediately whenever you defer…
metrics
Print a debt-ops health summary from the metrics log, covering registration rate, hook feedback action rate, ADR creation, and AI-authored share. Use when the user asks for "debt-ops metrics", "debt health", "registry stats", or invokes /debt-ops:metrics. Read-only, never writes the log.