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 sutchan/Agent-Skills-Hub --skill scripting-and-storyboardinggit clone --depth 1 https://github.com/sutchan/Agent-Skills-HubWrote 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/sutchan/agent-skills-hub/scripting-and-storyboarding)<a href="https://agentmods.dev/skills/sutchan/agent-skills-hub/scripting-and-storyboarding"><img src="https://agentmods.dev/badge/skills/sutchan/agent-skills-hub/scripting-and-storyboarding/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/sutchan/agent-skills-hub/scripting-and-storyboarding"><img src="https://agentmods.dev/badge/skills/sutchan/agent-skills-hub/scripting-and-storyboarding.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.00105 | $0.01986 |
| Opus 5 | $0.00053 | $0.00993 |
| Sonnet 5 | $0.00021 | $0.00397 |
| Haiku 4.5 | $0.00011 | $0.00199 |
Grade A, and why
scripting-and-storyboarding 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 8d 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.
This is a copy
91% identical to scripting-and-storyboarding — 19 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
scripting-and-storyboarding
The pre-production system — start from the spine, write both columns, envision every beat, number the shots, and edit on paper first. The agent writes the plan; the human shoots and judges; WoopSocial publishes the finished video. (Craft skill — no tool file.)
The POV: videos are won in pre-production — the cheapest edit is on paper
Chaotic shoots and endless edits are a pre-production deficit, not a talent deficit: the plan is "where you catch problems before they become expensive fixes on set or in post." Four truths carry this skill. (1) A words-only script plans half the video — the visual half gets improvised, and improvisation defaults to a static talking face; the two-column AV script (audio | visual) writes what's seen, beat by beat, so the change-every-few-seconds rhythm is planned, not hoped for. (2) The storyboard is a decision document, not art — its only question is "what's on screen at this beat?", answered by a shot table, stick figures, or AI previz frames (2026 pipelines make character-consistent boards in minutes — the tested benchmark: 12 frames from ~3 hours to 40–60 minutes, with explicit camera intent and a character bible as the craft rules). (3) The shot list regrouped BY SETUP is the batching trick — two weeks of content in one afternoon comes from sorting shots by location/framing/outfit, never by video. (4) Runtime math doesn't negotiate — ~130–150 wpm means a 300-word script is a 2-minute video; the stopwatch pass and the paper cut happen before the shoot. And the 2026 twist: AI video sequences need more pre-production, not less — every panel becomes a generation's shot brief, and previz frames cost cents where generations cost credits.
Read these first
- idea-generation-and-ideation — the idea being productionized.
- short-form-video-script (or the long-form skill) — the retention spine this turns into production.
- brand-profile + design-and-templates — visual language, end cards.
What ships with it
5 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.
- 8d ago First seen · 101 lines · 105 tokens per session scan A 774df6088d9a
scripting-and-storyboarding is a skill published in the GitHub repository sutchan/Agent-Skills-Hub (2 stars, last pushed yesterday), licensed MIT. It adds 105 tokens to every session and 1,986 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to scripting-and-storyboarding, differing in 19 lines, and is treated as a copy.
Other skills, from other repositories
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment.
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code.
skill-authoring
Author SKILL.md skills: frontmatter, validator limits, structure.
skill-creator
Create, improve, evaluate, benchmark skills. Use when authoring a new skill, updating an existing one, running evals, or optimizing a skill's description for triggering. Don't use for invoking skills, writing prose, or scaffolding Python projects.
iflytek-hyper-tts
A text-to-speech tool that turns written text into an MP3 recording. It can use an authorized voice and adjust speaking speed, volume, and pitch.