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 agentmods add skills/whystrohm/shotkit/storyboard-architectnpx skills add whystrohm/shotkit --skill storyboard-architectgit clone --depth 1 https://github.com/whystrohm/shotkitWrote 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/whystrohm/shotkit/storyboard-architect)<a href="https://agentmods.dev/skills/whystrohm/shotkit/storyboard-architect"><img src="https://agentmods.dev/badge/skills/whystrohm/shotkit/storyboard-architect.svg" alt="Measured on agentmods" 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 | $0.00104 | $0.03161 |
| Opus 5 | $0.00052 | $0.01580 |
| Sonnet 5 | $0.00021 | $0.00632 |
| Haiku 4.5 | $0.00010 | $0.00316 |
Grade A, and why
storyboard-architect 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 5d 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 — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Storyboard Architect
You are turning a creative brief into a deterministic storyboard. The output is a set of files an editor, agency, or developer can act on without asking follow-up questions.
This is not a creative-writing exercise. The output is a spec.
When to use
Trigger this skill when the user:
- Describes a video they want to make ("30-second explainer for...", "TikTok ad about...")
- Asks to storyboard, plan shots, break out beats, write a shot list
- Hands over a script, brief, or concept document expecting structured pre-production output
- Mentions a beat framework by name (Hero Trilogy, Pain-Proof-Promise, etc.)
- References an existing brand-lock file or pack
If the user only wants prompts for an image generator (no narrative structure), use visual-prompt-forge directly instead.
What you produce
For every storyboard run, create this exact set of files in the working output directory:
output/
├── run.json # Run identity + every input pinned by content hash
├── storyboard.md # Human-readable, structured per shot
├── shots.json # Machine-readable, schema in templates/shots.schema.json
├── text-overlays.json # On-screen text + timing
└── brand-lock.snapshot.md # Frozen copy of the brand-lock used (audit trail)
run.json is what makes the rest of the tree auditable later. A filename says nothing
about the bytes behind it, so the snapshot sitting next to a set of frames is not proof
that it is the snapshot they were built from. The hashes in run.json are that proof.
Write it once, at the end of the run, and never edit it.
If the user asks for image prompts or HTML preview, hand off to visual-prompt-forge or storyboard-html-preview, those skills consume shots.json directly. Don't try to do their job here.
Inputs
You need these. If any are missing, ask before drafting.
| Input | Required? | Default if absent |
|---|---|---|
| Brief (problem, audience, goal) | Yes | Ask |
| Total duration | Yes | Ask |
| Aspect ratio | Yes | Ask (16:9, 9:16, 1:1) |
| Beat framework | No | Suggest based on brief |
| Brand-lock file path | No | Use brand-packs/_template.md and flag the gap |
| Voiceover style (VO present, on-screen only, captions) | No | Ask if unclear |
| Target generator(s) for downstream prompts | No | Note as "to be specified" |
What ships with it
26 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.
- examples/30s-pain-proof-promise/brand-lock.snapshot.md 2.9 KB
- examples/30s-pain-proof-promise/preview.html 28 KB
- examples/30s-pain-proof-promise/run.json 843 B
- examples/30s-pain-proof-promise/shots.json 5.0 KB
- examples/30s-pain-proof-promise/storyboard.md 4.9 KB
- examples/30s-pain-proof-promise/text-overlays.json 2.2 KB
- examples/60s-founder-explainer/brand-lock.snapshot.md 2.9 KB
- examples/60s-founder-explainer/preview.html 29 KB
- examples/60s-founder-explainer/run.json 837 B
- examples/60s-founder-explainer/shots.json 5.7 KB
- examples/60s-founder-explainer/storyboard.md 4.8 KB
- examples/60s-founder-explainer/text-overlays.json 1.8 KB
- examples/shotkit-explainer/brand-lock.snapshot.md 4.0 KB
- examples/shotkit-explainer/preview.html 29 KB
- examples/shotkit-explainer/run.json 820 B
- examples/shotkit-explainer/shots.json 6.2 KB
- examples/shotkit-explainer/storyboard.md 6.2 KB
- examples/shotkit-explainer/text-overlays.json 2.7 KB
- references/beat-frameworks.md 2.7 KB
- references/on-screen-text.md 3.8 KB
- references/shot-grammar.md 3.5 KB
- references/timing-rules.md 3.2 KB
- templates/run.schema.json 6.8 KB
- templates/shots.schema.json 8.7 KB
- templates/storyboard.md.tpl 1.5 KB
- templates/text-overlays.schema.json 3.3 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.
- 5d ago First seen · 306 lines · 104 tokens per session scan A dda758167fa5
storyboard-architect is a skill published in the GitHub repository whystrohm/shotkit (19 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 104 tokens to every session and 3,161 once invoked, about $0.0005 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
shoot-outline-writer
Generates a structured shooting outline — organised by scene or sequence — listing locations, interviewees, interview topic areas, and B-roll requirements, so the director and crew know exactly what needs to be captured on each shoot day.
mood-board-brief
Writes a structured mood board brief for a visual project — a document that specifies visual references, tone, palette, texture, and the visual language a designer, photographer, or AI image generator should work within.
episode-concept-generator
Generates 6–8 fully developed episode concepts aligned to a podcast's format, theme, and audience — each with a title, premise, guest or source approach, and core listener question.
interview-question-builder
Builds a complete, staged interview question set for a podcast guest — organized from opening warm-up through core subject matter to closing reflection — with embedded follow-up prompts for each key question.
fact-sheet-writer
Produces a concise, structured fact sheet on any topic for production teams — covering key facts, essential terminology, background context, and common misconceptions — so crew and contributors arrive on set informed.
presenter-briefing-writer
Drafts a concise, production-ready briefing document that gives a presenter or on-screen moderator everything they need to walk into a shoot or live recording fully prepared.