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/outlinegit 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/outline)<a href="https://agentmods.dev/commands/rhuss/cc-slidev/outline"><img src="https://agentmods.dev/badge/commands/rhuss/cc-slidev/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 | $0.00012 | $0.01431 |
| Opus 5 | $0.00006 | $0.00715 |
| Sonnet 5 | $0.00002 | $0.00286 |
| Haiku 4.5 | $0.00001 | $0.00143 |
Grade A, and why
slidev: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 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 — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Outline Creation & Revision
Create evidence-based, timed presentation outline or revise existing outline based on feedback.
Evidence Base: Outlines validated using research-based timing (default 90s/slide) from PLOS Computational Biology. See references/presentation-best-practices.md.
Execution
1. Check for Existing Materials
Look for:
brainstorm.md- Source materialoutline.md- Existing outline to revisepresentation-config.md- Framing decisions
If creating new outline without brainstorming:
- Ask user for topic and key points
- Gather framing information (duration, audience, style)
2. Calculate Target Slide Count (Evidence-Based)
Default timing: 90 seconds (1.5 minutes) per slide
Formula:
Expected slides = (duration_minutes × 60) / seconds_per_slide
Acceptable range = expected ± 20%
Pacing options (configurable):
- Fast (60s/slide): Brief updates, high-level overviews
- Moderate (90s/slide): DEFAULT - technical content, balanced detail
- Detailed (120s/slide): Complex topics, deep dives
- Deep dive (180s/slide): Research talks, comprehensive analysis
Examples:
- 15-min talk @ 90s/slide = 10 slides (acceptable: 8-12)
- 20-min talk @ 90s/slide = 13 slides (acceptable: 10-16)
- 30-min talk @ 90s/slide = 20 slides (acceptable: 16-24)
- 45-min talk @ 90s/slide = 30 slides (acceptable: 24-36)
Include Q&A time if needed (typically 15-20% of total).
3. Apply Presentation Structure Principles
Use presentation-design skill principles:
Three-Act Structure:
-
Act 1 (Setup): 15-20% of slides
- Hook to grab attention
- Problem/opportunity statement
- Agenda preview
-
Act 2 (Confrontation): 60-70% of slides
- Main content sections
- Build complexity progressively
- Evidence and examples
-
Act 3 (Resolution): 15-20% of slides
- Synthesize key points
- Clear takeaways
- Call to action
Rule of Three:
- 3-5 main sections (ideally 3)
- 3 key takeaways
- 3 supporting points per section
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 · 247 lines · 12 tokens per session scan A 9ea146271433
slidev:outline is a command published in the GitHub repository rhuss/cc-slidev (50 stars, last pushed 15d ago), licensed MIT. It adds 12 tokens to every session and 1,431 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.