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 sugarforever/boring-video-studio --skill to-narrationgit clone --depth 1 https://github.com/sugarforever/boring-video-studioWrote 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/sugarforever/boring-video-studio/to-narration)<a href="https://agentmods.dev/skills/sugarforever/boring-video-studio/to-narration"><img src="https://agentmods.dev/badge/skills/sugarforever/boring-video-studio/to-narration/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/sugarforever/boring-video-studio/to-narration"><img src="https://agentmods.dev/badge/skills/sugarforever/boring-video-studio/to-narration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00029 | $0.00340 |
| Opus 5 | $0.00015 | $0.00170 |
| Sonnet 5 | $0.00006 | $0.00068 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
to-narration 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 12d 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.
What it actually says
To narration
Turn BEATS.md into NARRATION.md: a production-ready draft whose wording can still be revised by scene direction and the selected HyperFrames workflow.
Process
- Read
BEATS.md, its cited sources, and the user's voice conventions. Preserve each beat's job, claim, and handoff. - Write for the ear: one thought per sentence, concrete subjects and verbs, spoken transitions, and terminology explained at first use.
- Let visuals carry visible structure, comparison, and transformation. The narration supplies meaning the image cannot communicate alone.
- Mark paragraph-to-beat boundaries without adding visual instructions. Put unresolved pronunciation or factual questions in an
Open checkssection. - Write
NARRATION.md:
---
source: BEATS.md
status: draft
target_duration: ...
---
## B01 — Title
<a id="b01-p01"></a>
Spoken paragraph.
- Give every paragraph a stable
<beat-id>-pNNanchor. Preserve anchors when rewriting that paragraph; assign a new anchor when inserting one. - Read it aloud or estimate at the user's known speaking rate. Revise until every beat fits its budget and the full draft fits the target.
The draft is complete when it is ready for visual planning, every sentence traces to a beat, and no later visual has been prematurely prescribed. The selected HyperFrames workflow owns review timing and the voice-ready narration version after handoff.
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.
- 12d ago First seen · 35 lines · 29 tokens per session scan A d2be44d437e3
to-narration is a skill published in the GitHub repository sugarforever/boring-video-studio (83 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 340 once invoked, about $0.0001 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…