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/record-demogit 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/record-demo)<a href="https://agentmods.dev/commands/digitalsamba/claude-code-video-toolkit/record-demo"><img src="https://agentmods.dev/badge/commands/digitalsamba/claude-code-video-toolkit/record-demo.svg" alt="Measured on agentmods" 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 | $0.00006 | $0.01319 |
| Opus 5 | $0.00003 | $0.00660 |
| Sonnet 5 | $0.00001 | $0.00264 |
| Haiku 4.5 | $0.00001 | $0.00132 |
Grade A, and why
record-demo 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 4d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Record Browser Demo
Help me record a browser demo for a Remotion video project.
Project Integration
Before gathering configuration, check if we're in a project context:
-
Check for active project:
- Look for
project.jsonin current directory or parentprojects/*/ - If found, read it to understand:
- Which scenes need demo recordings
- Expected asset paths
- Scene instructions
- Look for
-
If project context found:
I see you're working on: {project.name} Scenes needing recordings: ⬜ Scene 3: Dark mode demo → demos/dark-mode.mp4 Instructions: Navigate to Settings → Toggle dark mode ⬜ Scene 5: Login flow → demos/login.mp4 Instructions: Show login → enter credentials → redirect Which scene would you like to record? (or enter a new recording) -
After recording completes:
- Update
project.jsonscene status to"asset-present" - Add session entry
- Regenerate project CLAUDE.md
- Update
Your Tasks
-
Gather Recording Configuration Use the AskUserQuestion tool to collect the following information:
Question 1 - Basic Setup:
- URL to record (e.g., "https://myapp.com/dashboard")
- Output filename (without extension, e.g., "dashboard-walkthrough")
Question 2 - Output Location: Ask where to save the recording. Options:
./output(default, local to playwright folder)- Detect from current project (look for nearest
public/demos/folder) - Custom path (let user specify)
Question 3 - Viewport:
- 1080p (1920x1080) - Default, matches Remotion
- 720p (1280x720) - Smaller files
- Mobile (390x844) - iPhone 14 size
- Custom dimensions
Question 4 - Recording Mode:
- Interactive - Opens a visible browser window. User manually performs actions while it records. Good for exploring or one-off recordings.
- Script Template - Generates a TypeScript file in
playwright/scripts/flows/with boilerplate. User edits the script to add specific actions, then runs it. Good for repeatable recordings.
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.
- 4d ago First seen · 146 lines · 6 tokens per session scan A 9fab1f9f0348
record-demo is a command published in the GitHub repository digitalsamba/claude-code-video-toolkit (2,041 stars, last pushed 3d ago), licensed MIT. It adds 6 tokens to every session and 1,319 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.
Other commands, from other repositories
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
Generate a complete agent-native CLI for any web app by recording and analyzing network traffic via playwright-cli. Runs the full pipeline with site assessment, capture, implementation, testing, and verification.
cli-anything-web:refine
Refine an existing cli-anything-web CLI by recording additional traffic and expanding command coverage. Invokes the gap-analyzer skill as its first step, then implements missing endpoints.
cli-anything-web:record
Record network traffic from a web app without generating a CLI. Useful for initial exploration or adding more coverage data.
setup-elevenlabs.en
Command "setup-elevenlabs.en" from minicoohei/ai-agent-camp, covering elevenlabs api setup, step 0: check setup progress, what you'll do in this session, readiness check and step 1: open elevenlabs in the browser.
screenshot
Take full page screenshots at 1280x720 viewport.