Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add rhuss/cc-slidev/plugin install slidevWrote 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/commands/rhuss/cc-slidev/generate)<a href="https://agentmods.dev/commands/rhuss/cc-slidev/generate"><img src="https://agentmods.dev/badge/commands/rhuss/cc-slidev/generate/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/commands/rhuss/cc-slidev/generate"><img src="https://agentmods.dev/badge/commands/rhuss/cc-slidev/generate.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.00011 | $0.05647 |
| Opus 5.5 | $0.00004 | $0.02259 |
| Sonnet 5.5 | $0.00002 | $0.01129 |
| Haiku 4.5 | $0.00001 | $0.00565 |
Grade A, and why
slidev:generate 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 1mo 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 — 742 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Slide Generation
Generate clean, accessible Slidev slides from validated outline with enforced design limits.
Research Basis: These guidelines are based on cognitive load studies (Miller's Law), TED presentation research, and MIT Communication Lab recommendations. See references/presentation-best-practices.md for detailed research.
Default Timing: 90 seconds (1.5 minutes) per slide (configurable: 60s-180s)
Execution
1. Prerequisites
Check for required files:
outline.md- Must existpresentation-config.md- For style/theme preferences (optional)brainstorm.md- For additional context (optional)
If outline.md missing:
- Inform user outline is needed first
- Offer to run
/slidev:outline - Exit
2. Determine Project Directory
Extract topic from outline title and create directory name:
Title: "Introduction to Kubernetes"
→ Directory: "introduction-to-kubernetes"
Create project structure:
mkdir -p [topic-slug]/{slides,public/images,exports}
Note: The slides/ subdirectory will contain individual markdown files for each slide.
3. Generate Slidev Frontmatter (Accessibility-First)
Using slidev-mastery skill, create frontmatter with accessibility defaults:
Professional/Corporate (Default):
---
theme: default
background: '#ffffff'
class: text-center
highlighter: shiki
lineNumbers: false
transition: slide-left
title: [Title]
---
<style>
/* Accessibility defaults: 18pt+ fonts, 4.5:1+ contrast */
h1 { font-size: 3rem; } /* ~48pt - headings ≥24pt required */
h2 { font-size: 2rem; } /* ~32pt */
h3 { font-size: 1.5rem; } /* ~24pt */
p, li { font-size: 1.25rem; } /* ~20pt - body ≥18pt required */
body {
font-family: 'Helvetica Neue', Arial, sans-serif; /* Sans-serif for body */
}
/* Colorblind-safe default palette: Blue + Orange */
:root {
--primary: #3b82f6; /* Blue - 8.6:1 contrast on white */
--secondary: #f97316; /* Orange - 3.4:1 (headings only) */
--neutral: #6b7280; /* Gray */
--text: #1f2937; /* Dark gray - 16.1:1 contrast */
}
</style>
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.
- 1mo ago First seen · 742 lines · 11 tokens per session scan A 4b5683af5326
slidev:generate is a command published in the GitHub repository rhuss/cc-slidev (54 stars, last pushed 2mo ago), licensed MIT. It adds 11 tokens to every session and 5,647 once invoked, about $0.0000 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-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.