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/extract-outline)<a href="https://agentmods.dev/commands/rhuss/cc-slidev/extract-outline"><img src="https://agentmods.dev/badge/commands/rhuss/cc-slidev/extract-outline.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.00012 | $0.03184 |
| Opus 5 | $0.00006 | $0.01592 |
| Sonnet 5 | $0.00002 | $0.00637 |
| Haiku 4.5 | $0.00001 | $0.00318 |
Grade A, and why
slidev:extract-outline 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 6d 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 — 492 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Extract Outline from Existing Slides
Reverse engineer a structured outline from an existing Slidev presentation by analyzing slide structure, titles, and content.
Use cases:
- Legacy presentations needing structure documentation
- Received slides from collaborators, need outline for context
- Made extensive slide edits, want updated outline
- Creating handout outline from presentation
- Refactoring presentation structure
Execution
1. Locate Presentation
Search for slides.md files:
# Find all slides.md in current directory and subdirectories
find . -name "slides.md" -type f -not -path "*/node_modules/*"
If no slides.md found:
- Inform user: "No presentation found in current directory"
- Suggest: "Create a new presentation with
/slidev:initor/slidev:generate" - Exit
If multiple slides.md found:
- List all with paths and brief descriptions
- Ask user which one to analyze
- Use selected path
If exactly one found:
- Proceed with that file
- Show path to user: "Analyzing presentation at: [path]"
2. Read Master Slides File
Read slides.md to extract structure:
The master file contains slide includes with comments:
---
src: ./slides/01-title.md
---
<!-- Slide 1: Title -->
---
src: ./slides/02-hook.md
---
<!-- Slide 2: Hook - Opening question -->
Parse master file:
- Extract all
src:paths to individual slide files - Extract slide numbers and descriptions from comments (format:
<!-- Slide N: Description -->) - Build slide mapping: slide number → file path → description
Expected data structure:
Slides:
1: ./slides/01-title.md → "Title"
2: ./slides/02-hook.md → "Hook - Opening question"
3: ./slides/03-problem.md → "Problem Statement"
...
18: ./slides/18-conclusion.md → "Conclusion - Key Takeaways"
19: ./slides/19-questions.md → "Questions"
20: ./slides/20-backup-methodology.md → "Backup - Detailed Methodology"
3. Read Individual Slide Files
For each slide file, extract:
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.
- 6d ago First seen · 492 lines · 12 tokens per session scan A 43f6b20258e3
slidev:extract-outline is a command published in the GitHub repository rhuss/cc-slidev (51 stars, last pushed 17d ago), licensed MIT. It adds 12 tokens to every session and 3,184 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.
Other commands, from other repositories
organize-files
Organize and rename files based on content analysis.
tree
Show file tree with sync status indicators showing which files are indexed, modified, new, or deleted.
prose-review-docs
Reviews markdown documentation files or directories against the active prose style rules — the plugin's vendor-neutral baseline plus your organization's overlay when one is configured. Accepts a file path or directory (recursive). Runs prose-style-checker and optionally Vale. Supports --fix to auto-apply safe…
cti-report
Render case deliverables — relationship graph (PNG/SVG/Mermaid) and a polished PDF/DOCX assessment. Usage: /cti-report [--graph|--pdf].
ppt-image2-editable-rebuild
Rebuild image2 or imagegen reference slides as editable PowerPoint decks.
convert
Convert a file to Markdown using markitdown.