generate-voiceover

A command for creating spoken narration from a script for a Remotion video project, using ElevenLabs or Qwen3-TTS text-to-speech services. It checks the project and scene scripts before generating audio.

In plain words
What is it for?
Use it to generate voiceover for individual video scenes or a complete Remotion project after checking the scene review status and available scripts.
Why use it?
It helps avoid recording narration that no longer matches the visuals or timing, and can prevent wasted service credits when scenes still need review.

Command for Claude Code

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/digitalsamba/claude-code-video-toolkit/generate-voiceover
Clone the repo
git clone --depth 1 https://github.com/digitalsamba/claude-code-video-toolkit

Made for: Claude Code.

Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,025 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.00006 $0.03025
Opus 5 $0.00003 $0.01512
Sonnet 5 $0.00001 $0.00605
Haiku 4.5 $0.00001 $0.00302

Measured yesterday against content hash 460d8f807c47, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

generate-voiceover 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 yesterday.

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.

.claude/commands/generate-voiceover.md · 368 lines

How it starts

The opening of the file, as written. The whole thing — 368 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Generate Voiceover

Help me generate a voiceover for a Remotion video project using ElevenLabs or Qwen3-TTS.

Project Integration

Before gathering configuration, check if we're in a project context:

  1. Check for active project:

    • Look for project.json in current directory or parent projects/*/
    • If found, read it to understand project state
  2. Check review status: If project has phase: "review" or no reviewStatus on scenes:

    ⚠️  Scene review not complete.
    
    Generating voiceover before review risks:
    - Narration that doesn't match visuals
    - Timing mismatches
    - Wasted API credits if script needs changes
    
    Run `/scene-review` first to verify each scene in Remotion Studio.
    
    Options:
    1. Run /scene-review first (recommended)
    2. Generate voiceover anyway (not recommended)
    

    Only proceed if user explicitly chooses option 2.

  3. Check for per-scene scripts (preferred): Look for public/audio/scenes/*.txt files in the project directory.

    If found:

    I see you're working on: {project.name}
    
    Found per-scene scripts in public/audio/scenes/ (recommended):
      - 01-title.txt (estimate: ~3s)
      - 02-overview.txt (estimate: ~15s)
      - 03-demo.txt (estimate: ~20s)
      - 04-summary.txt (estimate: ~12s)
    
    Total estimated: ~50 seconds of narration
    
    Options:
    1. Generate per-scene audio (recommended)
    2. Generate single voiceover file (legacy)
    

    Default to option 1 (per-scene) when scene scripts exist.

  4. If no scene scripts but VOICEOVER-SCRIPT.md exists:

    I see you're working on: {project.name}
    
    Script: VOICEOVER-SCRIPT.md (ready)
    Audio status: ⬜ Not yet generated
    
    Options:
    1. Split into scene scripts first (recommended for iteration)
    2. Generate single voiceover file
    
  5. After generation completes:

    • Update project.json:
      • Set audio.voiceover.status: "present"
      • If per-scene, set audio.voiceover.mode: "per_scene"
      • Transition phase if appropriate (review → audio → editing)
    • Add session entry
    • Regenerate project CLAUDE.md

Read the full file on GitHub · 368 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. yesterday First seen · 368 lines · 6 tokens per session scan A 460d8f807c47

Subscribe to this mod's changes

generate-voiceover is a command published in the GitHub repository digitalsamba/claude-code-video-toolkit (2,027 stars, last pushed 4d ago), licensed MIT. It adds 6 tokens to every session and 3,025 once invoked, about $0.0000 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.