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.
npx agentmods add commands/rhuss/cc-slidev/framegit 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/frame)<a href="https://agentmods.dev/commands/rhuss/cc-slidev/frame"><img src="https://agentmods.dev/badge/commands/rhuss/cc-slidev/frame.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 | $0.00015 | $0.03241 |
| Opus 5 | $0.00008 | $0.01621 |
| Sonnet 5 | $0.00003 | $0.00648 |
| Haiku 4.5 | $0.00002 | $0.00324 |
Grade A, and why
slidev:frame 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 4d 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 — 451 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frame Presentation Scope
Define presentation parameters: duration, slide count targets, audience, and style preferences.
Use when:
- After brainstorming, before creating outline
- Want to establish scope constraints
- Need to calculate target slide count from duration
- Setting presentation parameters
Inputs: Brainstorm findings (optional), user preferences
Outputs: presentation-config.md with framing parameters
Execution
1. Check for Brainstorm Context
If brainstorm.md exists:
- Read it to extract:
- Presentation title
- Audience (if specified)
- Duration (if specified in brainstorm)
- Context (conference, meetup, etc.)
If no brainstorm.md:
- Start fresh
- Will ask for all parameters
2. Gather Presentation Parameters
Use AskUserQuestion for efficient gathering:
Question 1: Duration
Ask user:
question: "How long should the presentation be?"
header: "Duration"
options:
- label: "5-10 minutes (Lightning talk)"
description: "Quick talks: ~10-15 slides at 30-45 sec/slide"
- label: "15-20 minutes (Standard)"
description: "Standard talks: ~15-20 slides at 1-2 min/slide"
- label: "30-45 minutes (Conference talk)"
description: "Conference talks: ~20-25 slides at 2 min/slide"
- label: "60+ minutes (Deep dive)"
description: "Deep dives: ~25-30 slides at 2-3 min/slide"
- label: "Custom duration"
description: "Specify exact duration in minutes"
If "Custom duration" selected:
- Ask: "What is the exact duration in minutes?"
- Validate: Must be positive integer
Extract duration value:
"5-10 minutes" → 7.5 minutes (midpoint)
"15-20 minutes" → 17.5 minutes
"30-45 minutes" → 37.5 minutes
"60+ minutes" → 60 minutes
"Custom: 25" → 25 minutes
Question 2: Time Per Slide (Optional)
Ask user:
question: "How much time per slide?"
header: "Pacing"
options:
- label: "Use recommended (based on duration)"
description: "Auto-calculate from research-based defaults"
- label: "30-45 seconds (Lightning pace)"
description: "Very fast, minimal explanation per slide"
- label: "60-90 seconds (Standard pace)"
description: "Comfortable pace for technical content"
- label: "2-3 minutes (Detailed pace)"
description: "Deep explanations, complex content"
- label: "Custom timing"
description: "Specify exact seconds per slide"
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.
- 4d ago First seen · 451 lines · 15 tokens per session scan A 92af15127114
slidev:frame is a command published in the GitHub repository rhuss/cc-slidev (50 stars, last pushed 16d ago), licensed MIT. It adds 15 tokens to every session and 3,241 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
brand-generate
Generate an on-brand document from a saved Brand Profile.
stt
Transcribe a local audio file or remote audio URL into text.
audition-voices
Generate voice audition samples for a character using Venice TTS.
music-suno-prompt
Grounded Suno prompt synthesis from local knowledge corpus + persona canon + label canon. No vibes-prompting.
tag
Add or remove free-form tags on photos, then find them with search --tag.
review-video
Make a " Reviews" video — a fast, faceless VO montage of REAL, verified competitor reviews that names the recurring complaints and positions YOUR business as the alternative, then hands off to your own customer testimonials.