slidev:visuals

A command for improving the visual presentation of every slide with diagrams, images, and visual guidance. It supports Mermaid, PlantUML, and Excalidraw, which are different formats for creating diagrams.

In plain words
What is it for?
Use it to enhance Slidev presentations with flowcharts, architecture diagrams, sketches, images, AI image prompts, and accessible visual styling.
Why use it?
It helps make slide content clearer and more visually structured while following accessibility guidance. It also keeps Excalidraw diagram data in separate files and places rendered images where the presentation can use them.

Command

Install

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.

agentmods
npx agentmods add commands/rhuss/cc-slidev/visuals
Clone the repo
git clone --depth 1 https://github.com/rhuss/cc-slidev
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,022 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00013 $0.04022
Opus 5 $0.00006 $0.02011
Sonnet 5 $0.00003 $0.00804
Haiku 4.5 $0.00001 $0.00402

Measured 2d ago against content hash 45d5fb060748, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

slidev:visuals 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.

slidev/commands/visuals.md · 582 lines

How it starts

The opening of the file, as written. The whole thing — 582 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Visual Enhancement Workflow

Analyze all slides and provide interactive visual enhancement with multi-platform diagrams (Mermaid, PlantUML, Excalidraw), images, and AI prompts using evidence-based best practices.

Evidence Base: Visual enhancements follow research-based principles for cognitive load, accessibility, and effective communication. See references/presentation-best-practices.md for guidelines.

Multi-Platform: All diagrams are automatically generated in enabled formats (Mermaid + PlantUML + Excalidraw). Mermaid embedded inline, alternatives saved in organized directories for flexibility.

CRITICAL - Excalidraw Rule: NEVER embed Excalidraw JSON in markdown files. Always:

  1. Write JSON to diagrams/<slug>.excalidraw
  2. Convert to SVG using render-excalidraw.sh
  3. Put SVG in public/images/<slug>/diagram-excalidraw.svg
  4. Include only the SVG image reference in markdown

Execution

1. Read Slides

Find and parse slides.md with CORRECT Slidev numbering:

IMPORTANT: Generate accurate slide numbering first

CRITICAL: Slidev Slide Numbering Read master slides.md directly:

Read the master slides.md file containing slide comments:

---
src: ./slides/01-title.md
---
<!-- Slide 1: Title -->

---
src: ./slides/05-microservices-benefits.md
---
<!-- Slide 5: Microservices Benefits -->

Extract slide information by parsing comment pattern: <!-- Slide \d+: .* -->

Output Format for Analysis: Always reference slides as: "Slide X (Title)" Example: "Slide 21 (Device Plugins Turn GPUs Into Schedulable Resources)"

Analysis Tasks:

  • Read slides.md to extract all slide comments
  • Count total slides (count comments)
  • Extract slide titles from comment descriptions
  • Read individual slide files (from src: paths) to check for:
    • Existing visuals (mermaid blocks, image references)
    • Visual placeholders (<!-- TODO: Visual)
    • Content that needs visuals

2. Analyze Visual Opportunities (Evidence-Based)

Read the full file on GitHub · 582 lines

Changes

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.

  1. 2d ago First seen · 582 lines · 13 tokens per session scan A 45d5fb060748

Subscribe to this mod's changes

slidev:visuals is a command published in the GitHub repository rhuss/cc-slidev (49 stars, last pushed 14d ago), licensed MIT. It adds 13 tokens to every session and 4,022 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-08-30.