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 skills add LFTPadilla/agent-dev-kit --skill explainer-videogit clone --depth 1 https://github.com/LFTPadilla/agent-dev-kitWrote 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/lftpadilla/agent-dev-kit/explainer-video)<a href="https://agentmods.dev/skills/lftpadilla/agent-dev-kit/explainer-video"><img src="https://agentmods.dev/badge/skills/lftpadilla/agent-dev-kit/explainer-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/skills/lftpadilla/agent-dev-kit/explainer-video"><img src="https://agentmods.dev/badge/skills/lftpadilla/agent-dev-kit/explainer-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.00101 | $0.00654 |
| Opus 5.5 | $0.00040 | $0.00262 |
| Sonnet 5.5 | $0.00020 | $0.00131 |
| Haiku 4.5 | $0.00010 | $0.00065 |
Grade A, and why
explainer-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 1mo 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explainer Video 🎬
Turns a written concept into renders/video.mp4. Thin wrapper: HyperFrames owns
the rendering, this skill owns the pipeline order, the video direction, and the
voice step.
When to use
- The explanation is a sequence in time: a race condition, a retry loop, a migration, an onboarding flow.
- The audience will not read code and will not open a diagram tool.
- Somebody must watch it later, without you present.
Do not use it for a single static picture. Route to diagram-render instead.
Requirements
| Need | How |
|---|---|
| HyperFrames | npx hyperframes installs on demand. Pin nothing. |
| Voice (preferred) | DEEPGRAM_API_KEY in env, or KEY=VALUE in ~/.config/deepgram.env |
| Voice (fallback) | No key → HyperFrames local Kokoro TTS: npx hyperframes tts |
| Media | ffmpeg and ffprobe on PATH |
Node 20 or later. The voice script has zero npm dependencies and uses fetch.
Quick start
npx hyperframes init videos/<slug> --non-interactive --example=blank --skill=faceless-explainer, then writeBRIEF.md.- Write
STORYBOARD.md(8–10 frames, one## Video directionblock) andSCRIPT.md, then get the frame table approved. node <skill_folder>/scripts/deepgram-voice.mjs --script SCRIPT.md --out audio_meta.json, thenaudio.mjs sync-durations.- Dispatch one worker per frame in parallel with the packet, the video direction, the word cues, and the real duration.
npx hyperframes render --skill=faceless-explainer --quality high --output renders/video.mp4.
Full commands, in order, live in references/pipeline.md.
The look and the negative list live in references/video-direction.md.
Output contract
- File:
videos/<slug>/renders/video.mp4 - Report the duration in seconds, measured with
ffprobe, not the planned duration. - Report the frame count and any frame that failed
npx hyperframes check.
Iteration rule
After every video, append what you learned to
references/lessons.md as one dated line. The pipeline
is only as good as the last failure somebody wrote down.
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.
- 1mo ago First seen · 55 lines · 101 tokens per session scan A 89186d431cd7
explainer-video is a skill published in the GitHub repository LFTPadilla/agent-dev-kit (2 stars, last pushed 27d ago), licensed MIT. It adds 101 tokens to every session and 654 once invoked, about $0.0004 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-09-12.
Other skills, from other repositories
mindos
MindOS: local knowledge assistant & shared KB. Keeps decisions, notes, SOPs, debugging lessons, research findings, preferences across sessions/agents. Core: save notes, search KB, organize files, run workflows, review, append CSV, hand off context, distill lessons. NOT for app source or paths outside KB. Triggers…
coding-standards
Applies language-neutral engineering standards when writing or reviewing code, especially around boundaries, failures, domain models, dependencies, tests, and type safety.
flashcards
Turn notes or a topic into a set of question/answer study flashcards. Use when the user wants to revise or memorise material.
code-review
Review a code snippet for bugs, security issues, and style, with concrete fixes. Use when the user shares code and asks for feedback or a review.
explain-simply
Explain a complex topic in plain language with an everyday analogy. Use when the user wants something demystified or "explained simply".
pr-learning
Extract actionable learnings from merged PRs by comparing initial submission vs final merged state. Analyzes review cycles to capture what changed and why. Use when the user says "learn from PR", "extract PR learnings", "what did we learn from this PR", or wants to build a knowledge base from merged PRs.