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.
git clone --depth 1 https://github.com/rhuss/cc-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/export)<a href="https://agentmods.dev/commands/rhuss/cc-slidev/export"><img src="https://agentmods.dev/badge/commands/rhuss/cc-slidev/export/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/export"><img src="https://agentmods.dev/badge/commands/rhuss/cc-slidev/export.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.00016 | $0.01006 |
| Opus 5.5 | $0.00006 | $0.00402 |
| Sonnet 5.5 | $0.00003 | $0.00201 |
| Haiku 4.5 | $0.00002 | $0.00101 |
Grade A, and why
slidev:export 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Export Presentation
Export Slidev presentation to various formats (PDF, PPTX, PNG).
Execution
1. Parse Format Argument
Extract from $ARGUMENTS:
- Valid formats: pdf, pptx, png
- Default: pdf (if not specified)
If invalid format:
- Error: "Supported formats: pdf, pptx, png"
- Ask which format they want
2. Find Presentation
Locate slides.md:
- Check current directory
- Check subdirectories
- If multiple, ask which one
3. Check Dependencies
Slidev export requires Playwright browsers:
# Check if playwright is available
npx playwright --version
If not installed:
Slidev export requires Playwright browsers for rendering.
**Install:**
```bash
npx playwright install chromium
This downloads Chromium browser for PDF/PPTX generation.
Should I install it now? (Y/n)
If user approves, install:
```bash
npx playwright install chromium
4. Export to Format
PDF Export:
cd [presentation-dir]
slidev export slides.md --output exports/slides.pdf
- Vector format (best quality)
- Suitable for printing
- Animations become static
- Interactive elements removed
PPTX Export:
cd [presentation-dir]
slidev export slides.md --format pptx --output exports/slides.pptx
- PowerPoint format
- Editable in PowerPoint/Keynote
- Some styling may change
- Good for sharing/editing
PNG Export:
cd [presentation-dir]
slidev export slides.md --output exports/slides --format png --per-slide
- Creates PNG for each slide
- Numbered files: slide-1.png, slide-2.png, etc.
- Useful for handouts, social media, thumbnails
- High resolution images
5. Monitor Progress
Slidev export can take time:
- Show progress if possible
- Inform user it's processing
- Typical time: 30-60 seconds
6. Verify Output
Check if export succeeded:
ls -lh exports/slides.*
If successful:
- Show file size
- Show location
- Offer to open
If failed:
- Check error output
- Common issues:
- Playwright not installed
- Syntax errors in slides
- Missing images
- Memory issues (large presentation)
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 · 209 lines · 16 tokens per session scan A 388037aafe22
slidev:export is a command published in the GitHub repository rhuss/cc-slidev (54 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 1,006 once invoked, about $0.0001 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
open
Open a PDF in the in-app viewer panel.
brief-compliance-check
Check a LaTeX coursework submission against the requirements in a supplied PDF assessment brief. Use when verifying format, required sections, word limits, or deliverables before submission. Not for general prose proofreading; use $proofread.
render-figures
Compile all .tex and .typ figure files in a directory.
docs
Document delivery with export to PPTX, DOCX, PDF formats.
pipeline-minutar-pdf
Pipeline completo de sentença judicial a partir de PDF (conversão, linha-tempo, relatório, análise, fundamentação, merge).
cti-report
Render case deliverables — relationship graph (PNG/SVG/Mermaid) and a polished PDF/DOCX assessment. Usage: /cti-report [--graph|--pdf].