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/initgit 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.00013 | $0.03965 |
| Opus 5 | $0.00006 | $0.01982 |
| Sonnet 5 | $0.00003 | $0.00793 |
| Haiku 4.5 | $0.00001 | $0.00396 |
Grade A, and why
slidev:init 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 — 657 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initialize Presentation Project
Complete end-to-end workflow orchestrator that sets up a new presentation project and guides through all phases from brainstorming to final handout.
This is the "easy button" for new presentations - fully automated workflow with interactive decision points.
What it does:
- Creates project directory structure
- Initializes git repository
- Checks/installs Slidev dependencies
- Orchestrates full creation workflow by calling specialized commands
Use when: Starting a brand new presentation from scratch
Difference from individual commands: This orchestrates the entire workflow, while individual commands handle specific tasks.
Execution
1. Parse Arguments and Setup TODO Tracking
Extract topic from $ARGUMENTS if provided:
# User can invoke as:
# /slidev:init
# /slidev:init "Introduction to Kubernetes"
Create workflow TODO list:
Use TodoWrite tool:
{
"todos": [
{
"content": "Set up project directory and git",
"activeForm": "Setting up project directory and git",
"status": "pending"
},
{
"content": "Check Slidev installation",
"activeForm": "Checking Slidev installation",
"status": "pending"
},
{
"content": "Frame presentation scope",
"activeForm": "Framing presentation scope",
"status": "pending"
},
{
"content": "Brainstorm and research",
"activeForm": "Brainstorming and researching",
"status": "pending"
},
{
"content": "Create outline",
"activeForm": "Creating outline",
"status": "pending"
},
{
"content": "Generate slides",
"activeForm": "Generating slides",
"status": "pending"
},
{
"content": "Enhance visuals (optional)",
"activeForm": "Enhancing visuals",
"status": "pending"
},
{
"content": "Add presenter notes (optional)",
"activeForm": "Adding presenter notes",
"status": "pending"
},
{
"content": "Generate handout (optional)",
"activeForm": "Generating handout",
"status": "pending"
}
]
}
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 · 657 lines · 13 tokens per session scan A 0b385320a18f
slidev:init is a command published in the GitHub repository rhuss/cc-slidev (49 stars, last pushed 13d ago), licensed MIT. It adds 13 tokens to every session and 3,965 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.