Claude Code Video Toolkit is a workspace that lets Claude Code create videos by producing scripts, voiceovers, music, visuals, and rendered MP4 files. It is for developers using AI-assisted, programmatic video production with tools such as Remotion and open-source media models. The catalogue entries provide commands, skills, instructions, and settings for this workflow.
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.
git clone --depth 1 https://github.com/digitalsamba/claude-code-video-toolkitWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/digitalsamba/claude-code-video-toolkit/design)<a href="https://agentmods.dev/commands/digitalsamba/claude-code-video-toolkit/design"><img src="https://agentmods.dev/badge/commands/digitalsamba/claude-code-video-toolkit/design/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/digitalsamba/claude-code-video-toolkit/design"><img src="https://agentmods.dev/badge/commands/digitalsamba/claude-code-video-toolkit/design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.01720 |
| Opus 5.5 | $0.00000 | $0.00688 |
| Sonnet 5.5 | $0.00000 | $0.00344 |
| Haiku 4.5 | $0.00000 | $0.00172 |
Grade A, and why
design 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 1mo 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Refinement
Focused design session for improving video scene visuals using the frontend-design skill.
Purpose
Deep-dive visual refinement for slides and components:
- Elevate generic aesthetics to distinctive, memorable visuals
- Ensure visual narrative coherence across scenes
- Iterate on typography, color, motion, and atmosphere
Usage
/design # Discover project, list scenes, choose one
/design [scene-id] # Jump directly to a specific scene
Step 1: Discover Project Context
First, find and understand the current project:
-
Locate the project
- Check if in a project directory (has
project.jsonor template config) - If not, scan
projects/for active projects - If multiple, ask user which project
- Check if in a project directory (has
-
Read project configuration
project.jsonif exists (scenes, phase, brand)- Or template config:
src/config/sprint-config.tsorsrc/config/demo-config.ts - Brand/theme:
src/config/theme.ts
-
Build scene inventory
- List all scenes from config
- Identify which are slide-type (designable) vs demo-type (video playback)
- Note each scene's purpose from config content
Step 2: Identify Target Scene
If no scene specified in command, show discovered scenes:
## Design Refinement
**Project:** {project_name}
**Template:** {template_type}
Which scene would you like to refine?
| # | Scene ID | Type | Description |
|---|----------|------|-------------|
{list slide-type scenes discovered from config}
(Demo/video scenes are not shown - they display recorded content)
Enter scene ID or number:
Step 3: Understand Scene Context
Before invoking frontend-design, gather specific context:
-
Read the target slide component
- Find component file from scene type mapping
- e.g.,
src/components/slides/{Type}Slide.tsx
-
Read scene content from config
- What text/data does this scene display?
- What's the intended message?
-
Understand position in sequence
- What scene comes before? What mood does it leave?
- What scene comes after? What mood should we set up?
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.
- 1mo ago First seen · 285 lines · 0 tokens per session scan A ea1e6e6ecdbd
design is a command published in the GitHub repository digitalsamba/claude-code-video-toolkit (2,360 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,720 tokens. 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
ui-evidence
Discover, configure, and run ui-evidence for before/after UI review in this repo.
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
design-audit
Audit the rendered design of live sites. Evidence capture first, then one critique per site. Argument is a URL, a repo name, or all.
4-generate
Run Stage 4 of the design system skill generation pipeline: parallel skill file generation.
mockups-generate
Generate dashboard mockups.
discover-diagrams
Load diagram skills (Mermaid flowcharts, sequence, ER, architecture).