Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/whystrohm/shotkitnpx agentmods add skills/whystrohm/shotkit/storyboard-architectWrote 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/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/whystrohm/shotkit/storyboard-architect"><img src="https://agentmods.dev/badge/skills/whystrohm/shotkit/storyboard-architect.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.00117 | $0.04087 |
| Opus 5.5 | $0.00047 | $0.01635 |
| Sonnet 5.5 | $0.00023 | $0.00817 |
| Haiku 4.5 | $0.00012 | $0.00409 |
Grade B, and why
storyboard-architect scanned grade B with 1 finding 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 27d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
head -n 1 ~/.claude/shotkit-tools/VERSION # from a repo clone: head -n 1 VERSION How it starts
The opening of the file, as written. The whole thing — 353 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:
- Asks for a storyboard or shot list for a video ("storyboard a 30-second explainer for...", "shot list for a TikTok ad about...")
- Asks to plan shots, break out beats, or 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, as the last step, after the other four files are final. Everything in run.json except rounds is written once and never edited. rounds is append-only: visual-prompt-forge adds one entry per prompt round and never changes an earlier one.
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.
What ships with it
20 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 29 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 31 KB
- examples/60s-founder-explainer/run.json 837 B
- examples/60s-founder-explainer/shots.json 5.8 KB
- examples/60s-founder-explainer/storyboard.md 4.8 KB
- examples/60s-founder-explainer/text-overlays.json 1.8 KB
- references/beat-frameworks.md 3.3 KB
- references/on-screen-text.md 3.8 KB
- references/shot-grammar.md 3.8 KB
- references/timing-rules.md 3.5 KB
- templates/run.schema.json 7.4 KB
- templates/shots.schema.json 9.1 KB
- templates/storyboard.md.tpl 1.5 KB
- templates/text-overlays.schema.json 3.5 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.
- 27d ago Changed · +47 lines · +13 tokens per session scan A → B b2bef905ef02
- 29d ago Changed 3ef7bd227272
- 1mo ago First seen · 306 lines · 104 tokens per session scan A dda758167fa5
storyboard-architect is a skill published in the GitHub repository whystrohm/shotkit (23 stars, last pushed 27d ago), licensed Apache-2.0. It adds 117 tokens to every session and 4,087 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
execute
Primary pipeline execution step after /prd-to-issues or for clearly scoped implementation work. Use to build, verify, and commit a concrete slice, delegating to /tdd for backend work and behavior-heavy frontend logic when red-green-refactor will reduce risk. Not for shaping or pre-merge review.
compound
Primary pipeline knowledge-capture step that closes the compounding loop. Capture a durable lesson in docs/solutions/ onto the open PR before /closeout merges (the default), or post-merge when the lesson only surfaces during/after merge. Use so future /research and /write-a-prd runs improve. Not for trivial edits with…
prd-to-issues
Primary pipeline decomposition step after /write-a-prd. Use when a shaped PRD is ready to become implementation-ready slices with boundary maps and dependency order. Not for unresolved scope, appetite, or solution direction.
research
Primary pipeline step after /shape and before /write-a-prd. Use to verify current docs, versions, repo patterns, and key unknowns before shaping. Invokes /api-design-review when API contract risk is high. Not for underdefined problems or implementation-ready work.
closeout
Primary pipeline tail step after /pre-merge, when a reviewed PR is ready to land and you want the workspace back to a clean base. Use to merge, switch off the worktree before removing it, prune the merged branch, pull base, and verify a clean end state. Triggers on 'close out', 'merge and clean up', 'get back to a…
improve-pipeline
Optional meta-skill for improving chrislacey89/skills from real-world friction or breakdowns discovered while using the pipeline in another repo. Use when the main lesson is about the pipeline itself, not the downstream project. Grounds proposals in established software-engineering guidance from /library. Produces a…