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/notes)<a href="https://agentmods.dev/commands/rhuss/cc-slidev/notes"><img src="https://agentmods.dev/badge/commands/rhuss/cc-slidev/notes/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/notes"><img src="https://agentmods.dev/badge/commands/rhuss/cc-slidev/notes.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.00013 | $0.02049 |
| Opus 5.5 | $0.00005 | $0.00820 |
| Sonnet 5.5 | $0.00003 | $0.00410 |
| Haiku 4.5 | $0.00001 | $0.00205 |
Grade A, and why
slidev:notes 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Presenter Notes Generation
Generate comprehensive presenter notes for all slides or enhance existing notes, applying the evidence-based principle that detailed explanations belong in notes, not on slides.
Evidence Base: MIT Communication Lab research shows audiences cannot read and listen simultaneously. Detailed text, full explanations, and supporting data should be in presenter notes, not on slides. See references/presentation-best-practices.md for guidelines.
Execution
1. Read Current Slides
Find and read slides.md:
- Parse all slides
- Check which slides already have notes
- Identify slides missing notes
2. Generate/Enhance Notes
For each slide, create presenter notes with:
Structure:
<!--
PRESENTER NOTES:
[Slide title/number for reference]
KEY POINTS:
- [Main point to emphasize]
- [Supporting detail]
- [Example or analogy to share]
TIMING: [X] seconds (default: 90s per slide, adjust for complexity)
DELIVERY TIPS:
- [How to present this slide]
- [Voice, pace, emphasis guidance]
TRANSITIONS:
- FROM previous: [How you arrived here]
- TO next: [How to transition out]
LIKELY QUESTIONS:
- Q: [Question audience might ask]
A: [How to answer]
ADDITIONAL CONTEXT:
- [Background information]
- [Technical details not on slide]
- [References or sources]
-->
Content Guidelines:
Key Points (MIT CommLab Principle - Detail Goes Here):
- Expand terse slide bullets into full explanations (slide has phrases, notes have sentences)
- Add details NOT shown on slide (slide is minimal, notes are comprehensive)
- Include specific numbers, dates, names (slide has trends, notes have data)
- Provide examples and stories (slide has assertion, notes have supporting narrative)
- Full context and background (slide is concise, notes have depth)
Research basis: Audiences cannot read and listen simultaneously. Slide shows key point (visual channel), notes contain what you say (auditory channel).
Timing (Evidence-Based - Default 90s/slide):
- Default: 90 seconds (1.5 minutes) per slide (configurable)
- Title slides: 30 seconds
- Simple content slides: 60-90 seconds
- Complex/data slides: 90-120 seconds
- Deep technical slides: 120-180 seconds
- Transition slides: 15-30 seconds
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 · 285 lines · 13 tokens per session scan A 6bd5b7184c71
slidev:notes is a command published in the GitHub repository rhuss/cc-slidev (54 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 2,049 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
brand-generate
Generate an on-brand document from a saved Brand Profile.
render-figures
Compile all .tex and .typ figure files in a directory.
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.
harness-onboarding
Generate a human-readable onboarding document from HARNESS.md, AGENTS.md, and REFLECTIONLOG.md — a friendly guide for new team members.
publish-api-docs
Generate interactive API documentation from blueprint specs (Swagger UI, Redoc, AsyncAPI).