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/editgit 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.00014 | $0.01588 |
| Opus 5 | $0.00007 | $0.00794 |
| Sonnet 5 | $0.00003 | $0.00318 |
| Haiku 4.5 | $0.00001 | $0.00159 |
Grade A, and why
slidev:edit 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Edit Slide Command
This command helps you edit a specific slide by providing context and quality analysis.
Task
You are editing a specific slide in a Slidev presentation. Your job is to:
- Locate and read the slide file
- Show the user context about the slide
- Ask what they want to do
- Help them make improvements
Step 1: Get the Slide Number
The slide number is in $ARGUMENTS. If it's missing or not a number, ask the user: "Which slide number would you like to edit?"
CRITICAL: Use the EXACT slide number provided. Do NOT add 1 or modify it in any way.
Step 2: Find and Read slides.md
Use Bash to find slides.md:
find . -name "slides.md" -type f -not -path "*/node_modules/*" | head -1
Then use the Read tool on that file.
The slides.md file contains slide entries like:
---
src: ./slides/06-example-slide.md
---
<!-- Slide 6: Example Slide Title -->
Step 3: Extract the Slide Information
From the slides.md content you just read:
- Find the comment that matches:
<!-- Slide {N}: {TITLE} -->where N is the EXACT slide number from $ARGUMENTS - Look at the
src:line IMMEDIATELY BEFORE that comment - that's your slide file path - Count how many slide comments exist total
If the slide number is greater than the total slides, error: "Only {X} slides exist. Choose 1-{X}."
Step 4: Read the Slide File
Use the Read tool on the slide file path you extracted from the src: line.
Step 5: Read Context Files (Optional)
If these files exist, read them to gather context:
outline.md- presentation structurespeaker-notes.mdornotes.md- presenter notesbrainstorm.md- presentation goals
Step 6: Show Context and Menu
Display a concise summary:
Editing Slide {N}: {TITLE}
Position: {N} of {TOTAL} | Layout: {layout} | File: {path}
Context: {2-3 sentence summary combining info from outline, speaker notes, and slide position}
Then use AskUserQuestion with:
- question: "What would you like to do with this slide?"
- header: "Action"
- multiSelect: false
- options:
- label: "Analyze quality" description: "Run evidence-based quality assessment and get improvement suggestions"
- label: "Edit content" description: "Modify text, bullets, or heading directly"
- label: "Change layout" description: "Switch Slidev layout (two-cols, image-right, center, etc.)"
- label: "Add visuals" description: "Add or improve diagrams, images, or code examples"
- label: "Update notes" description: "Edit presenter notes and timing guidance"
- label: "Delete this slide" description: "Remove slide and renumber remaining slides (uses Slide Management skill)"
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 · 205 lines · 14 tokens per session scan A 8d8beedfd2ba
slidev:edit is a command published in the GitHub repository rhuss/cc-slidev (49 stars, last pushed 13d ago), licensed MIT. It adds 14 tokens to every session and 1,588 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
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.