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/deletegit 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.00015 | $0.00961 |
| Opus 5 | $0.00008 | $0.00481 |
| Sonnet 5 | $0.00003 | $0.00192 |
| Haiku 4.5 | $0.00002 | $0.00096 |
Grade A, and why
slidev:delete 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Delete Slide Command
Delete a slide by its slide number (from <!-- Slide N: ... --> comment). All subsequent slides are automatically renumbered to close gaps.
IMPORTANT: Argument is SLIDE NUMBER (e.g., 6 for Slide 6), NOT list position
IMPORTANT: Go DIRECTLY to the 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:delete <slide-number>"
2. Confirm Deletion
Ask for simple confirmation:
{
"questions": [
{
"question": "Delete Slide [N] and renumber subsequent slides?",
"header": "Confirm",
"multiSelect": false,
"options": [
{
"label": "Yes, delete",
"description": "Remove slide and renumber"
},
{
"label": "Cancel",
"description": "Keep unchanged"
}
]
}
]
}
If cancelled, exit with: "Cancelled."
3. Execute Script
IMMEDIATELY run the script - NO exploration before this:
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/manage-slides.py delete [SLIDE_NUMBER] --renumber
The script handles everything:
- Validation (position >= 2, cannot delete title)
- Deleting the file
- Renumbering subsequent slides
- Updating slides.md
- Git operations
4. Show Results
Display the script output:
✅ Slide deleted
[Script output]
Examples
Delete Slide 2 (first content slide):
Current: Slide 2, 3, 4, 5
/slidev:delete 2
→ Deletes Slide 2 (file 02-xxx.md)
→ Result: Slide 2, 3, 4 (renumbered from old 3, 4, 5)
Delete Slide 4:
Current: Slide 2, 3, 4, 5, 6
/slidev:delete 4
→ Deletes Slide 4 (file 04-xxx.md)
→ Result: Slide 2, 3, 4, 5 (renumbered from old 5, 6)
Delete Slide 5:
Current: Slide 2, 3, 4, 5
/slidev:delete 5
→ Deletes Slide 5 (file 05-xxx.md)
→ Result: Slide 2, 3, 4
Slide Numbering Convention
Important:
- Slide 1 = Title from
slides.mdfrontmatter (no file inslides/) - Slide 2+ = Files in
slides/directory starting at02-xxx.md - Cannot delete slide 1: It's the title, always present
- First deletable slide is position 2 (
slides/02-xxx.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 · 134 lines · 15 tokens per session scan A 6fa9c72fabea
slidev:delete is a command published in the GitHub repository rhuss/cc-slidev (49 stars, last pushed 14d ago), licensed MIT. It adds 15 tokens to every session and 961 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
compile_paper
Convert a SWARM paper from markdown to LaTeX (if needed), compile to PDF, and open it.
camera-ready
Convert an accepted anonymous-submission LaTeX paper (AAAI/AIES/ACM-style) to camera-ready and implement the accepted reviews. Use when a paper is accepted with no rebuttal and you need to de-anonymize, add copyright, turn on section numbering, implement each reviewer's minor revisions, optionally move proofs to a…
brand-generate
Generate an on-brand document from a saved Brand Profile.
tree
Show file tree with sync status indicators showing which files are indexed, modified, new, or deleted.
Draft SSP From Extraction
Draft a schema-valid OSCAL SSP from extracted legacy sections, optionally importing a real FedRAMP baseline profile.
cti-report
Render case deliverables — relationship graph (PNG/SVG/Mermaid) and a polished PDF/DOCX assessment. Usage: /cti-report [--graph|--pdf].