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/digitalsamba/claude-code-video-toolkit/scene-reviewgit clone --depth 1 https://github.com/digitalsamba/claude-code-video-toolkitWhat 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.00014 | $0.01887 |
| Opus 5 | $0.00007 | $0.00944 |
| Sonnet 5 | $0.00003 | $0.00377 |
| Haiku 4.5 | $0.00001 | $0.00189 |
Grade A, and why
scene-review 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.
How it starts
The opening of the file, as written. The whole thing — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scene Review
Interactive scene-by-scene review using Remotion Studio. Critical quality gate before voiceover generation.
Quick Start
/scene-review # Review all scenes from beginning
/scene-review title # Jump to specific scene by type
/scene-review 3 # Jump to scene 3
Example Session
$ /scene-review
Remotion Studio running at http://localhost:3000
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Scene 1 of 6: title (4s, frame 0)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Navigate to frame 0 in Studio and watch the scene.
[1] Approve [2] Adjust [3] Refine [4] Flag [5] Skip
> 3 (Refine)
Invoking frontend-design skill...
Reading TitleSlide.tsx and adjacent scenes for context...
What aspect needs refinement?
- Color palette feels too flat
- Text animation needs more impact
- Background too static
> Background too static
[Makes changes to TitleSlide.tsx]
Check Remotion Studio - it hot-reloads automatically.
Better? [y/n/more changes]
> y
Scene 1 approved. Moving to Scene 2...
Iterative Feedback Loop
The review follows this cycle for each scene:
┌─────────────┐
│ View scene │◄──────────────────────┐
│ in Studio │ │
└──────┬──────┘ │
│ │
▼ │
┌─────────────┐ ┌─────────────┐ │
│ Evaluate │───►│ Adjust │────┤
│ │ │ (config) │ │
└──────┬──────┘ └─────────────┘ │
│ │
│ ┌─────────────┐ │
│──────────►│ Refine │────┘
│ │ (component) │
│ └─────────────┘
▼
┌─────────────┐
│ Approve │───► Next scene
└─────────────┘
- Adjust: Change config values (text, duration, asset paths) → hot-reload → verify
- Refine: Invoke frontend-design skill for visual improvements → edit component → hot-reload → verify
Repeat until the scene looks right, then approve and move on.
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.
- yesterday First seen · 311 lines · 14 tokens per session scan A 158a373dbabd
scene-review is a command published in the GitHub repository digitalsamba/claude-code-video-toolkit (2,027 stars, last pushed 4d ago), licensed MIT. It adds 14 tokens to every session and 1,887 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
qawolfCliRunResults.template
How to use what qawolf run get --run-id --json returns, and how to read the Playwright trace it links to.
qawolf-cli
Manage QA Wolf through the qawolf CLI. Use when asked to create, update, or list coverage requests, bug reports, or maintenance reports; start a run of flows or tags on the QA Wolf platform or read a run's results; list, set, or delete environment variables; manage environments, flows, or tags; request automation of…
cli-anything-web:validate
Validate a cli-anything-web CLI against the tiered quality checklist (Tier 1 critical / Tier 2 comprehensive). Reports per-category and per-tier results.
cli-anything-web:test
Run tests for a cli-anything-web CLI and update TEST.md with results.
cli-anything-web:list
List all available CLI-Anything-Web CLIs (installed and generated).
remove-bg
Remove background from an image.