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/addgit 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.00948 |
| Opus 5 | $0.00008 | $0.00474 |
| Sonnet 5 | $0.00003 | $0.00190 |
| Haiku 4.5 | $0.00002 | $0.00095 |
Grade A, and why
slidev:add 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 2d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Slide Command
Insert a new slide at the specified slide number (from <!-- Slide N: ... --> comment). Existing slides at that number and higher shift forward.
IMPORTANT: Argument is SLIDE NUMBER (e.g., 6 for new Slide 6), NOT list position
IMPORTANT: Go DIRECTLY to asking for title and running script - do NOT read slides.md or display structure first
Execution
1. Parse Slide Number
Extract slide number from $ARGUMENTS. If missing, show: "Usage: /slidev:add <slide-number>"
2. Ask for Slide Title
{
"questions": [
{
"question": "Title for the new slide?",
"header": "Title",
"multiSelect": false,
"options": [
{
"label": "Enter custom title",
"description": "Provide a meaningful title"
},
{
"label": "Untitled Slide",
"description": "Add title later"
}
]
}
]
}
If "Enter custom title", use the "Other" text provided. If "Untitled Slide", use that as title.
3. Execute Script
IMMEDIATELY run the script - NO exploration before this:
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/manage-slides.py add [SLIDE_NUMBER] --title "[TITLE]" --renumber
The script handles everything:
- Validation (position >= 2)
- Creating the slide file
- Renumbering subsequent slides
- Updating slides.md
- Git operations
4. Show Results
Display the script output:
✅ Slide added at position [N]
[Script output]
Examples
Insert new Slide 2:
Current: Slide 2, 3, 4, 5
/slidev:add 2
→ NEW Slide 2 (file 02-xxx.md)
→ Shifts: old 2→3, old 3→4, old 4→5, old 5→6
→ Result: Slide 2 (NEW), 3, 4, 5, 6
Insert new Slide 4:
Current: Slide 2, 3, 4, 5
/slidev:add 4
→ NEW Slide 4 (file 04-xxx.md)
→ Shifts: old 4→5, old 5→6
→ Result: Slide 2, 3, 4 (NEW), 5, 6
Insert new Slide 6:
Current: Slide 2, 3, 4, 5
/slidev:add 6
→ NEW Slide 6 (file 06-xxx.md, becomes last)
→ No shifts needed
→ Result: Slide 2, 3, 4, 5, 6 (NEW)
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.
- 2d ago First seen · 127 lines · 16 tokens per session scan A 65d8286729cf
slidev:add 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 948 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.
constitution
Create or update the project constitution from interactive or provided principle inputs.