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/continuegit clone --depth 1 https://github.com/rhuss/cc-slidevWhat 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.00016 | $0.01672 |
| Opus 5 | $0.00008 | $0.00836 |
| Sonnet 5 | $0.00003 | $0.00334 |
| Haiku 4.5 | $0.00002 | $0.00167 |
Grade A, and why
slidev:continue 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 3d 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Continue Working on Presentation
Resume work on an existing slide deck by analyzing current state and providing contextual next steps.
Execution
1. Locate Presentation Files
Search for presentation files in current directory and subdirectories:
# Look for slides.md files
find . -name "slides.md" -type f
If no slides.md found:
- Inform user no presentation found
- Ask if they want to create a new one:
/slides:create - Exit
If multiple slides.md found:
- List all found with paths
- Ask user which one to work on
- Use selected path
If one slides.md found:
- Proceed with that file
2. Analyze Current State
Read the presentation files to understand status:
Read master slides.md directly:
Read the master slides.md file to extract slide information from comments:
The file contains comments like:
---
src: ./slides/01-title.md
---
<!-- Slide 1: Title -->
Analyze the content:
- Count total slides (count
<!-- Slide \d+:comments) - Extract presentation title (from first slide comment)
- Read individual slide files to identify visual placeholders (
<!-- TODO: Visual) - Count slides with existing diagrams/images (mermaid blocks, image references)
- Extract section structure from slide comment descriptions
Check for related files:
outline.md- Outline exists?brainstorm.md- Research notes?cfp-and-guidelines.md- CfP abstract?presentation-config.md- Configuration?handout.texorhandout.pdf- Handout generated?ai-image-prompts.md- AI prompts saved?public/images/- Images present?
3. Quality Assessment
Use presentation-design skill to assess current quality:
Quick analysis:
- Are titles meaningful assertions or generic labels?
- Do slides exceed 50 words body text?
- Do slides exceed 6 elements?
- How many slides need visuals?
- Are presenter notes present?
4. Present Status Summary
Show comprehensive status to user:
## 📊 Presentation Status
**Title:** [Presentation Title]
**Location:** [path/to/slides.md]
**Slides:** [X] total ([Y] content + [Z] backup)
### Current State
**Structure:**
- ✓ Outline exists ([sections count] sections)
- ✓ Brainstorm notes present
- ✓/✗ Handout generated
**Content Quality:**
- [X]/[Total] slides have meaningful assertion titles
- [Y] slides need visual enhancement
- [Z] slides exceed 50 word limit
- [W] slides missing presenter notes
**Visual Elements:**
- [N] diagrams/images included
- [M] visual placeholders remaining
- [P] AI image prompts saved
**Files Present:**
✓ slides.md
✓/✗ outline.md
✓/✗ brainstorm.md
✓/✗ handout.pdf
✓/✗ ai-image-prompts.md
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.
- 3d ago First seen · 253 lines · 16 tokens per session scan A 1d312d197874
slidev:continue is a command published in the GitHub repository rhuss/cc-slidev (49 stars, last pushed 14d ago), licensed MIT. It adds 16 tokens to every session and 1,672 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.