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/movegit 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.01415 |
| Opus 5 | $0.00008 | $0.00707 |
| Sonnet 5 | $0.00003 | $0.00283 |
| Haiku 4.5 | $0.00002 | $0.00142 |
Grade A, and why
slidev:move 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Move Slide Command
Move a slide to a new position by specifying which slide to move and which slide it should come after. All slides are automatically renumbered sequentially.
IMPORTANT: Arguments are SLIDE NUMBERS (e.g., 6 for Slide 6), NOT list positions
IMPORTANT: Go DIRECTLY to the script - do NOT read slides.md or display structure first
Execution
1. Parse Arguments
Extract FROM and AFTER from $ARGUMENTS. Expected format: <from> --after <to>
If missing, show: "Usage: /slidev:move <from-slide-number> --after <to-slide-number>"
2. Confirm Move
Ask for simple confirmation:
{
"questions": [
{
"question": "Move Slide [FROM] to position after Slide [AFTER]?",
"header": "Confirm",
"multiSelect": false,
"options": [
{
"label": "Yes, move",
"description": "Move slide and renumber all slides"
},
{
"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 move [FROM] --after [AFTER]
The script handles everything:
- Validation (can't move slide 1, both slides must exist)
- Moving the slide to new position
- Renumbering all slides sequentially
- Updating slides.md
- Git operations
4. Show Results
Display the script output:
✅ Slide moved
[Script output]
Examples
Move slide 6 to after slide 3 (becomes slide 4):
Current: Slide 2, 3, 4, 5, 6, 7
/slidev:move 6 --after 3
→ Moves Slide 6 to position 4
→ Result: Slide 2, 3, 4 (was 6), 5 (was 4), 6 (was 5), 7
Move slide 3 to after slide 6 (becomes slide 7):
Current: Slide 2, 3, 4, 5, 6, 7
/slidev:move 3 --after 6
→ Moves Slide 3 to position 7
→ Result: Slide 2, 3 (was 4), 4 (was 5), 5 (was 6), 6 (was 7), 7 (was 3)
Move slide 5 to beginning (after title):
Current: Slide 2, 3, 4, 5, 6
/slidev:move 5 --after 1
→ Moves Slide 5 to position 2 (first content slide)
→ Result: Slide 2 (was 5), 3 (was 2), 4 (was 3), 5 (was 4), 6
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 · 185 lines · 15 tokens per session scan A 7cdc191cc273
slidev:move is a command published in the GitHub repository rhuss/cc-slidev (49 stars, last pushed 13d ago), licensed MIT. It adds 15 tokens to every session and 1,415 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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.