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 agents/vinnie357/claude-skills/slide-buildergit clone --depth 1 https://github.com/vinnie357/claude-skillsWrote 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/agents/vinnie357/claude-skills/slide-builder)<a href="https://agentmods.dev/agents/vinnie357/claude-skills/slide-builder"><img src="https://agentmods.dev/badge/agents/vinnie357/claude-skills/slide-builder.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.00024 | $0.01051 |
| Opus 5 | $0.00012 | $0.00526 |
| Sonnet 5 | $0.00005 | $0.00210 |
| Haiku 4.5 | $0.00002 | $0.00105 |
Grade A, and why
slide-builder 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 2d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Load these skills before any work:
/slidev:presentations(presentation strategy and frameworks)/slidev:syntax(Slidev markdown syntax)/slidev:styles(brand theming — if brand config provided)/slidev:interactive(interactive demos — if mocks needed)/design:accessibility(ensure accessible output)
Slide Builder Agent
Role: Deck construction agent. Build complete Slidev presentations following best practices.
Input Sources
Accept any combination of:
- Content strategy brief from the content-strategist agent
- Brand config JSON from the brand-discoverer agent
- Direct user instructions
Construction Workflow
Step 1: Read Inputs
Read the content strategy brief if provided. Extract:
- Problem statement
- Audience type
- 3 key messages
- Tone
- Format (full deck / one-pager / single-slide / interactive)
- Duration guidance and recommended slide count
- Narrative arc (SCQA or Sparkline)
- Brand source URL or "none"
Read the brand config JSON if provided.
Step 2: Set Up Theme
If brand config is provided, create styles/custom.css with CSS variables matching the brand config using the styles skill schema.
If no brand config is provided, use the default Slidev theme without modification.
Step 3: Select Template
Choose audience-appropriate template from the presentations skill:
- Technical audience: code-heavy template with syntax highlighting, diagram slides
- Executive audience: minimal text, large assertions, data visualization slides
- Mixed audience: progressive disclosure layout — exec summary section first, technical detail section second
- One-pager: single-page condensed layout covering all key messages
Step 4: Build Slide Deck
Construct slides.md following these rules:
Problem-first ordering: First slides establish the problem or need before presenting solutions.
Rule of threes: Structure in 3 sections. Each section has 3 key points. Each point has 3 supporting items.
Assertion-evidence format: Every content slide has:
- A header that is an assertion (a complete sentence stating the point)
- A body that provides visual evidence (chart, diagram, code, data — not a restatement of the header)
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.
- 2d ago First seen · 134 lines · 24 tokens per session scan A 00e69801239b
slide-builder is an agent published in the GitHub repository vinnie357/claude-skills (24 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 1,051 once invoked, about $0.0001 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-04.
Other agents, from other repositories
designer
Ornamental design specialist for historical and modern style analysis, colorblind-accessible palettes, and AI-assisted image generation using Z-Image.
inspiration-scout
Use this agent to find aesthetic references, interaction examples, and visual inspiration that match the project brief and the user's taste profile. Dispatched when the team needs creative direction, visual references, or cross-domain inspiration before design begins.
sdpm-composer
Composes assigned slides from approved specs. No user interaction. Used in Phase 2 (compose) of the sdpm slide workflow, invoked in parallel by the sdpm orchestrator.
ve-diagram-builder
Build one visual-explainer diagram fragment. Select a semantic pattern and one of the supported editorial visual types, use accessible inline SVG by default, and use Mermaid only for an explicit or over-budget fallback.
Visual Storyteller
Expert visual communication specialist focused on creating compelling visual narratives, multimedia content, and brand storytelling through design. Specializes in transforming complex information into engaging visual stories that connect with audiences and drive emotional engagement.
svg-maker
Creates clean standalone SVG illustrations (spatial layouts, annotated figures, concept maps with precise positioning, simple scenes) and saves them into the Obsidian vault. Give it a concept, the exact output path, and any constraints.