Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add mrieck/demoday-claude-plugin/plugin install demodayWrote 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/mrieck/demoday-claude-plugin/create-demo-video)<a href="https://agentmods.dev/commands/mrieck/demoday-claude-plugin/create-demo-video"><img src="https://agentmods.dev/badge/commands/mrieck/demoday-claude-plugin/create-demo-video/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/mrieck/demoday-claude-plugin/create-demo-video"><img src="https://agentmods.dev/badge/commands/mrieck/demoday-claude-plugin/create-demo-video.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.00015 | $0.00386 |
| Opus 5 | $0.00008 | $0.00193 |
| Sonnet 5 | $0.00003 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
create-demo-video 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 9d 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.
What it actually says
Use the demo-video skill to fulfil this request.
$ARGUMENTS
Run from the repository of the software being demoed, or point at one with a path.
Before anything else:
- Check the environment:
node "$CLAUDE_PLUGIN_ROOT/scripts/doctor.mjs". Fix any failing required check, or tell the user exactly what to install or grant. - Read the codebase to work out what the software does and what is worth showing.
- Ask the user about goal, audience, length — and which named style from the catalog in the demo-video skill their video is most like (launch, anchor, tutorial, explainer for 16:9; listicle, cohost, flashcard, glide for 9:16 Shorts) — before writing the script. Those answers change the whole video.
- Show the cost estimate from
scripts/plan.mjsand get an explicit yes before generating anything.
Then follow the skill: script → narration → rehearse → perform → presenter and b-roll → render → QA. While rehearsing, tell the user which parts of the application you are exercising and what you find.
When the demo is done, offer a vertical Short for YouTube Shorts / Reels /
TikTok — a 15–45s cut from the same project (the demo-shorts skill). If the
user asked for shorts or vertical video up front, use that skill directly; it
still needs a landscape demo's captures to cut from, or its own capture pass.
Every Short gets a cover hook card as frame 0 (its thumbnail) — preview it
with render.mjs --cover-only and show the PNG before the full render.
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.
- 9d ago First seen · 34 lines · 15 tokens per session scan A 81bb46b4e105
create-demo-video is a command published in the GitHub repository mrieck/demoday-claude-plugin (2 stars, last pushed 6d ago), licensed MIT. It adds 15 tokens to every session and 386 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-31.
Other commands, from other repositories
setup
Set up PromptCut - installs deps (pip, ffmpeg), checks keys, CapCut folder.
video
Make a full video from an idea or a script - storyboard, voiceover, images, music, subtitles, render.
premiere
Hand the video to Adobe Premiere Pro - editable sequence with motion keyframes, voiceover, music, titles, SRT subtitles.
resolve
Hand the video to DaVinci Resolve - editable timeline with zoom/position keyframes, voiceover, music, titles, SRT subtitles.
shorts
Cut vertical shorts or reels - from a topic, a script, or an existing long video.
vegas
Hand the video to VEGAS Pro - a script builds the project with pan/crop keyframes, voiceover, ducked music, titles, markers.