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 iSerter/claude-feature-recon/plugin install feature-reconWrote 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/skills/iserter/claude-feature-recon/create-demo-videos)<a href="https://agentmods.dev/skills/iserter/claude-feature-recon/create-demo-videos"><img src="https://agentmods.dev/badge/skills/iserter/claude-feature-recon/create-demo-videos/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/skills/iserter/claude-feature-recon/create-demo-videos"><img src="https://agentmods.dev/badge/skills/iserter/claude-feature-recon/create-demo-videos.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.00097 | $0.01707 |
| Opus 5 | $0.00048 | $0.00853 |
| Sonnet 5 | $0.00019 | $0.00341 |
| Haiku 4.5 | $0.00010 | $0.00171 |
Grade A, and why
create-demo-videos 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 11d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Demo Videos
Films the flows that work. Reads the recipes /identify-user-flows wrote, records the real UI,
narrates it, and cuts one mp4 per feature:
user-flows.json + flows/*.json → demo-videos.json → capture → tts → build
clips/ voiceover/ videos/demo/*.mp4
Deliberately not a motion-graphics piece: hard cuts, a calm voice, one video per feature, 30–120 seconds each. It records the product as it actually is — which is the whole point of it living in a recon plugin rather than a marketing one.
Bundled files live beside this SKILL.md (${CLAUDE_PLUGIN_ROOT}/skills/create-demo-videos/):
capture.mjs, tts.mjs, build.mjs, templates/demo-videos.example.json. The narration agent is
at ${CLAUDE_PLUGIN_ROOT}/agents/recon-feature-explainer.md. Always pass absolute paths.
Requires Node 20+, Playwright and ffmpeg, plus GOOGLE_GENAI_API_KEY (or GEMINI_API_KEY) for
narration. Without the key everything still works and the videos come out silent.
sh ${CLAUDE_PLUGIN_ROOT}/scripts/install-deps.sh reports what is missing.
When not to use
- The app cannot run locally, or the screens are still mocks. Record nothing rather than record a fake UI.
- The flows have never been tested. Run
/test-user-flowsfirst — see step 2.
Procedure
1. Resolve arguments
<recon-dir>— defaultdocs/recon, or--dir <path>.--feature <slug>— film one feature only.- Everything else (voice, pacing, music) is a field in
demo-videos.json.
demo-videos.json holds only what filming needs — voice, pacing, music, scenes. baseUrl, auth
and viewports are read from user-flows.json, so a changed login selector stays a one-line edit.
2. Film only what passes
Read <recon-dir>/e2e-test-results.json and exclude every flow that is not passed. A demo of a
broken flow is the one output this must never produce: it is a recording of a bug, presented as a
feature.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 142 lines · 97 tokens per session scan A bfe315b9f5af
create-demo-videos is a skill published in the GitHub repository iSerter/claude-feature-recon (6 stars, last pushed 1mo ago), licensed MIT. It adds 97 tokens to every session and 1,707 once invoked, about $0.0005 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 skills, from other repositories
feature-demo-recording
Record a demo video of a web feature from a real browser. Two modes -- a NARRATED film where measured voiceover drives the timeline (designed slides, subtitles, punch-in camera, rendered from an HTML timeline), and a SILENT evidence clip for a PR or a QA pass. Use when the user asks to record a video, demo, or screen…
html-to-video-pipeline
Reliable HTML-to-MP4 rendering via headless browser recording (Playwright/Puppeteer) + ffmpeg — the ordering, gotchas, and verification steps you MUST get right or the output silently rots. Trigger whenever the user is building or debugging any pipeline that turns an HTML/CSS/JS page (single-file, multi-composition…
browser-video-recording
Create polished 60 fps 4:3 4K browser screen-recording style videos from Codex in-app browser captures, with browser-only crop, natural macOS cursor styling, deliberate click choreography, zoom-follow framing, ffprobe/thumbnail verification, and optional native recording compatibility checks. Use when the user asks to…
record-video
Record and upload a short browser interaction video artifact.
playwright-recording
Record browser interactions as video using Playwright. Use for capturing demo videos, app walkthroughs, and UI flows for Remotion videos. Triggers include recording a demo, capturing browser video, screen recording a website, or creating walkthrough footage.
demo-video
Agent-recorded product demo videos — choreograph a real browser flow with a cursor overlay and camera zooms, encode from raw frames, and package for PR evidence or social posts. Project specifics come from .demo-video.yaml.