Borrowing it
Nothing to install: this file belongs to ric03uec/clawrium. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ric03uec/clawrium/main/.claude/skills/create-vhs/SKILL.mdgit clone --depth 1 https://github.com/ric03uec/clawriumWrote 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/ric03uec/clawrium/create-vhs)<a href="https://agentmods.dev/skills/ric03uec/clawrium/create-vhs"><img src="https://agentmods.dev/badge/skills/ric03uec/clawrium/create-vhs/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/ric03uec/clawrium/create-vhs"><img src="https://agentmods.dev/badge/skills/ric03uec/clawrium/create-vhs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 38 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 144 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 234 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00083 | $0.03593 |
| Opus 5.5 | $0.00033 | $0.01437 |
| Sonnet 5.5 | $0.00017 | $0.00719 |
| Haiku 4.5 | $0.00008 | $0.00359 |
Grade A, and why
create-vhs 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 2mo 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 — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Demo Recording with VHS — replay-first pipeline
Record CLI demos using charmbracelet/vhs. Each demo lives in its own dated-slug folder docs/demos/YYYYMMDD-<slug>/. The pipeline is replay-first: captured stdouts are saved once on a live host, then a YAML spec drives tape generation, recording, and narration. Iteration is fast and timing is deterministic.
Pipeline
(one-time, slow)
scenes.yaml + live host --> outputs/*.txt [capture phase]
|
(instant) v
scenes.yaml + outputs/*.txt --> compile.py --> tape.tape + helpers.sh + compiled.json
|
(~2 min) v
vhs tape.tape --> recording.mp4
|
(~30s, cached per text) v
narrate.py compiled.json --> voice/*.mp3 + recording-narrated.mp4
|
(manual) v
upload to YouTube
compile.py, vhs, and narrate.py are all idempotent and fast. The slow step is the initial capture; everything downstream re-runs in seconds.
Output Layout
| Path | Committed? | Purpose |
|---|---|---|
docs/demos/lib/cards.sh |
yes | Shared titlecard/outrocard/headline/progress ANSI functions |
docs/demos/lib/compile.py |
yes | scenes.yaml → tape.tape + helpers.sh + compiled.json |
docs/demos/lib/narrate.py |
yes | compiled.json + .env → voice/*.mp3 + recording-narrated.mp4 |
docs/demos/lib/.env.example |
yes | Template for ElevenLabs credentials |
docs/demos/lib/.env |
no (gitignored) | Real API key + voice/model IDs |
docs/demos/YYYYMMDD-<slug>/scenes.yaml |
yes | Single source of truth — scene structure, commands, narration |
docs/demos/YYYYMMDD-<slug>/outputs/NN-<slug>.txt |
yes | Per-scene captured stdouts (replayed by the tape) |
docs/demos/YYYYMMDD-<slug>/tape.tape |
yes | Generated by compile.py; do not hand-edit |
docs/demos/YYYYMMDD-<slug>/helpers.sh |
yes | Generated by compile.py; sources lib/cards.sh |
docs/demos/YYYYMMDD-<slug>/compiled.json |
yes | Generated by compile.py; absolute narration timestamps |
docs/demos/YYYYMMDD-<slug>/voice/*.mp3 |
no (gitignored) | Per-beat TTS clips, cached by sha1(voice_id + text) |
docs/demos/YYYYMMDD-<slug>/recording.mp4 |
no (gitignored) | Output of vhs tape.tape |
docs/demos/YYYYMMDD-<slug>/recording-narrated.mp4 |
no (gitignored) | Final video with voiceover muxed in |
What ships with it
2 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.
- 2mo ago First seen · 265 lines · 83 tokens per session scan A dc8a2d25ae9f
create-vhs is a skill published in the GitHub repository ric03uec/clawrium (67 stars, last pushed 13d ago), licensed Apache-2.0. It adds 83 tokens to every session and 3,593 once invoked, about $0.0003 per session on Opus 5.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 skills, from other repositories
python
Use when the task is Python itself, in any framework or none: PEP 695 generics, mypy --strict typing, dataclass/Protocol/TypedDict/Enum choices, asyncio.TaskGroup, stdlib idioms, src/ layout + pyproject.toml with uv, ruff+mypy+pytest gate. NOT a FastAPI/ASGI service (that is fastapi), NOT a deep pytest suite (that is…
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
telegram
Telegram Bot skill for sending and editing Telegram messages via Bot API. Use when Bub needs to: (1) Send a message to a Telegram user/group/channel, (2) Reply to a specific Telegram message with replytomessageid, (3) Edit an existing Telegram message, or (4) Push proactive Telegram notifications. Prefer rich…
gh
GitHub CLI skill for interacting with GitHub via the gh command line tool. Use when Bub needs to (1) Create, view, or manage GitHub repositories, (2) Work with issues and pull requests, (3) Create and manage releases, (4) Run and monitor GitHub Actions workflows, (5) Create and manage gists, (6) Install and manage…
modern-python-toolchain
Modern Python project setup with uv, ruff, and pyright. Use when initializing a new Python project, configuring the Python environment, setting up linting/formatting, or when a project needs uv (the fast Python package manager). Trigger on: 'set up Python', 'new Python project', 'configure uv', 'install uv', 'ruff'…
vexor-cli
Semantic file discovery via vexor. Use whenever locating where something is implemented/loaded/defined in a medium or large repo, or when the file location is unclear. Prefer this over manual browsing.