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 fanfan-de/anybox --skill faceless-explainergit clone --depth 1 https://github.com/fanfan-de/anyboxWrote 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/fanfan-de/anybox/faceless-explainer)<a href="https://agentmods.dev/skills/fanfan-de/anybox/faceless-explainer"><img src="https://agentmods.dev/badge/skills/fanfan-de/anybox/faceless-explainer/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/fanfan-de/anybox/faceless-explainer"><img src="https://agentmods.dev/badge/skills/fanfan-de/anybox/faceless-explainer.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.00098 | $0.06277 |
| Opus 5.5 | $0.00039 | $0.02511 |
| Sonnet 5.5 | $0.00020 | $0.01255 |
| Haiku 4.5 | $0.00010 | $0.00628 |
Grade A, and why
faceless-explainer 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- product-launch-video — 86% identical, 117 lines differ
- product-launch-video — 83% identical, 87 lines differ
How it starts
The opening of the file, as written. The whole thing — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
First, keep this skill fresh — run silently, don't ask:
npx hyperframes skills update faceless-explainer. A fast no-op when everything is current; otherwise it refreshes this skill plus the core domain skills it depends on before you rely on them.
media-use: Before sourcing audio/images/logos, call
/media-useto resolve BGM/SFX/images from the HeyGen catalog and brand logos from their official sources. Run--adoptfirst to register existing assets. See/media-useskill.
Faceless Explainer to HyperFrames
Use this skill to turn a body of text into an explainer video: pick a design system, plan a teaching story, and build it frame by frame in HyperFrames. Faceless means every visual is invented downstream — there is no capture step and no real asset inventory.
The front door is
/hyperframes. You are the orchestrator. Run each step, verify its gate, and only then continue. This skill is for explaining a topic from text, with no product and no website to capture. Any other intent, a bare "make a video", or any uncertainty → read/hyperframesfirst — the intent layer owns every route decision, and a fresh creation arriving here withoutBRIEF.mdgoes through it anyway (Setup's opening rule).
You are the orchestrator. Work in videos/<project>/. Run steps in order and pass each gate before continuing. User-gated steps are Step 0, Step 3, and Step 6. Read ../hyperframes-core/references/brief-contract.md before Step 0 — it defines the gate types and how BRIEF.md's flow/storyboard derive the mode that governs the Step 3/4/6 gates. Do every step yourself except Step 5, where you dispatch one sub-agent per frame. Do not put design or motion rules here; those live in the frame-worker sub-agent, this skill's local ../hyperframes-animation/rules/ + ../hyperframes-animation/blueprints/, and hyperframes-creative.
Workflow: Step 0 setup → hyperframes.json; Step 1 brief → capture/extracted/; Step 2 design system → frame.md; Step 3 storyboard/script → STORYBOARD.md and SCRIPT.md; Step 3.1 audio → audio_meta.json; Step 4 visual design → enriched STORYBOARD.md; Step 5 frames → compositions/frames/NN-*.html and index.html; Step 6 final render → renders/video.mp4.
What ships with it
23 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.
- references/cut-catalog.md 12 KB
- references/motion-language.md 15 KB
- references/story-design.md 20 KB
- references/visual-design.md 20 KB
- scripts/assemble-index.mjs 26 KB runs code
- scripts/assemble-index.test.mjs 2.9 KB runs code
- scripts/audio.mjs 13 KB runs code
- scripts/audio.test.mjs 7.8 KB runs code
- scripts/build-frame.mjs 25 KB runs code
- scripts/captions.mjs 23 KB runs code
- scripts/captions.test.mjs 1.7 KB runs code
- scripts/frame-packets.mjs 1.1 KB runs code
- scripts/frame-packets.test.mjs 3.0 KB runs code
- scripts/lib/assets.mjs 2.1 KB runs code
- scripts/lib/dimensions.mjs 2.2 KB runs code
- scripts/lib/pad-frame-duration.mjs 1.6 KB runs code
- scripts/lib/storyboard.mjs 8.1 KB runs code
- scripts/lib/tokens.mjs 9.7 KB runs code
- scripts/lib/transition-registry.mjs 1.6 KB runs code
- scripts/lib/transitions.json 3.8 KB
- scripts/transitions.mjs 15 KB runs code
- scripts/transitions.test.mjs 2.3 KB runs code
- sub-agents/frame-worker.md 2.0 KB
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 · 234 lines · 98 tokens per session scan A 9243ecde0ad2
faceless-explainer is a skill published in the GitHub repository fanfan-de/anybox (55 stars, last pushed 24d ago), licensed MIT. It adds 98 tokens to every session and 6,277 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-03.
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.
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.
deck-course-module
A course or workshop slide template with persistent learning goals, teaching pages, multiple-choice self-tests, and a wrap-up.