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 holoviz-dev/holoviz-skills --skill explanatory-videogit clone --depth 1 https://github.com/holoviz-dev/holoviz-skillsWrote 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/holoviz-dev/holoviz-skills/explanatory-video)<a href="https://agentmods.dev/skills/holoviz-dev/holoviz-skills/explanatory-video"><img src="https://agentmods.dev/badge/skills/holoviz-dev/holoviz-skills/explanatory-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/holoviz-dev/holoviz-skills/explanatory-video"><img src="https://agentmods.dev/badge/skills/holoviz-dev/holoviz-skills/explanatory-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.00089 | $0.01856 |
| Opus 5.5 | $0.00036 | $0.00742 |
| Sonnet 5.5 | $0.00018 | $0.00371 |
| Haiku 4.5 | $0.00009 | $0.00186 |
Grade A, and why
explanatory-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 yesterday.
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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explanatory Video
A codebase explainer for someone about to open their first PR. A demo sells an outcome; an explainer builds a mental map, so the viewer finishes knowing which directory to open for the change they have in mind. The video is an animated diagram, not a screen recording, and it follows the same deterministic HTML contract and MP4 export as a demo.
Contents
- References
- Workflow
- Scope: one layer, five boxes
- Verify against the source
- Story: follow one request
- Layout: a fixed stage
- Progressive disclosure
- Labels and captions
- Pacing
- Ending: where your code goes
References
- Making a Demo Video: the
window.seek(t)HTML contract, checking frames and exporting to MP4. An explainer uses all three unchanged; don't restate them here. - deslop: run every caption through it.
- Sound, if asked: the demo reference's "Generated sound effects" and "Generated music" sections. In an explainer, each box's first appearance is where its motif enters, so the score builds up with the diagram.
Workflow
- Read the repo's layout, then the base classes and the module that wires them together, before proposing anything.
- Reply with the one sentence the video teaches and a box table (name, one line for a new dev, path). Get agreement on scope here; it is the cheapest place to cut.
- Reply with a beat sheet (time range, what appears, what moves, caption) and the order boxes appear in. Flag any claim you inferred rather than read.
- Check the flagged claims in the source, then build the HTML.
Scope: one layer, five boxes
The common failure is a tour of every directory. A new contributor can't hold twenty boxes, and a tree of folders teaches names, not how they relate.
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.
- yesterday First seen · 156 lines · 89 tokens per session scan A a6dc02ef419c
explanatory-video is a skill published in the GitHub repository holoviz-dev/holoviz-skills (5 stars, last pushed 2d ago), licensed BSD-3-Clause. It adds 89 tokens to every session and 1,856 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-10-17.
Other skills, from other repositories
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
book-mirror
Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis. Each chapter is preserved in detail (The Chapter) and mirrored back to the reader's actual life (The Mirror) using brain context. The mirror observes and resonates — a friend pointing out parallels, NOT a consultant rearranging the reader's…
lean-formalize
Develop and verify a mathematical proof in Lean, continue an incomplete Lean project, or audit whether it proves the original statement. Connect actual inputs to intermediate lemmas, assemble the target theorem, check its transitive axioms, and provide a reproducible handoff. Use when Lean is requested or a specific…
exam-forecast
Analyze past exams from the same professor to surface patterns — subject weighting, recurring issue-spot traps, favored hypo types, policy-vs-doctrine mix — and forecast likely emphases for the upcoming exam. Use when the user says "what's on the exam", "analyze past exams", "predict the exam", or shares past exams.
miniapp
Build a tiny interactive HTML playground only when someone asks to see, play with, or step through a mechanism.
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.