slidev:edit

A command for editing one slide in a Slidev presentation, a developer-made slideshow written in Markdown. It finds the slide file and provides its surrounding table-of-contents context before helping improve it.

In plain words
What is it for?
Use it when you know a slide number and want to inspect, discuss, or improve that specific slide.
Why use it?
It avoids editing the wrong slide or losing track of where that slide fits in the presentation.

Command

Install

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.

agentmods
npx agentmods add commands/rhuss/cc-slidev/edit
Clone the repo
git clone --depth 1 https://github.com/rhuss/cc-slidev
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,588 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What 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.

ModelPer sessionOnce 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

Measured 2d ago against content hash 8d8beedfd2ba, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

slidev/commands/edit.md · 205 lines

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:

  1. Locate and read the slide file
  2. Show the user context about the slide
  3. Ask what they want to do
  4. 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:

  1. Find the comment that matches: <!-- Slide {N}: {TITLE} --> where N is the EXACT slide number from $ARGUMENTS
  2. Look at the src: line IMMEDIATELY BEFORE that comment - that's your slide file path
  3. 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 structure
  • speaker-notes.md or notes.md - presenter notes
  • brainstorm.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:
    1. label: "Analyze quality" description: "Run evidence-based quality assessment and get improvement suggestions"
    2. label: "Edit content" description: "Modify text, bullets, or heading directly"
    3. label: "Change layout" description: "Switch Slidev layout (two-cols, image-right, center, etc.)"
    4. label: "Add visuals" description: "Add or improve diagrams, images, or code examples"
    5. label: "Update notes" description: "Edit presenter notes and timing guidance"
    6. label: "Delete this slide" description: "Remove slide and renumber remaining slides (uses Slide Management skill)"

Read the full file on GitHub · 205 lines

Changes

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.

  1. 2d ago First seen · 205 lines · 14 tokens per session scan A 8d8beedfd2ba

Subscribe to this mod's changes

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.