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-html-previewWrote 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-html-preview)<a href="https://agentmods.dev/skills/whystrohm/shotkit/storyboard-html-preview"><img src="https://agentmods.dev/badge/skills/whystrohm/shotkit/storyboard-html-preview/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-html-preview"><img src="https://agentmods.dev/badge/skills/whystrohm/shotkit/storyboard-html-preview.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.00128 | $0.03290 |
| Opus 5.5 | $0.00051 | $0.01316 |
| Sonnet 5.5 | $0.00026 | $0.00658 |
| Haiku 4.5 | $0.00013 | $0.00329 |
Grade A, and why
storyboard-html-preview 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 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.
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 — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Storyboard HTML Preview
You are turning structured storyboard files into a single shareable HTML document. The output is what an editor, stakeholder, or client opens in a browser without thinking about it.
The constraint is non-negotiable: single file, no build step, no server, works offline. Any time the output requires "run this build command" or "host this somewhere," the skill has failed.
When to use
Trigger when the user:
- Asks to preview, share, or export a storyboard or shot list
- Wants a printable version of a storyboard
- Says yes when storyboard-architect offers a preview
- Hands off
storyboard.md+shots.json+ asks for a deliverable for review
Share, export and print requests about anything else are not for this skill. It does not start on its own after a storyboard-architect run; the architect offers it and the user picks.
Where the tools and packs are
After ./install.sh, the validators and helpers are in ~/.claude/shotkit-tools/ and the
brand packs are in ~/.claude/shotkit-brand-packs/. A --project install puts both
under ./.claude/ instead. From a repo clone they are tools/ and brand-packs/. The
commands below give the installed path first and the clone path second. The tools need
pip install pyyaml jsonschema.
What you produce
One file: preview.html. Self-contained. Inline CSS. No JavaScript dependencies (vanilla JS only, embedded). The brand fonts are linked from Google Fonts, with a system fallback stack behind each one, so the page reads the same offline in the fallback fonts. No external images (placeholder slots; if generated images exist, embed as base64 OR reference relative paths).
output/
├── run.json # input, for the run id and date
├── storyboard.md # input
├── shots.json # input
├── text-overlays.json # input
├── brand-lock.snapshot.md # input
├── frames/round-N/ # input, if generation has happened
├── critiques/round-N/ # input, for the verdict badges
└── preview.html # ← what this skill produces
What ships with it
3 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.
- 27d ago Changed · +46 lines · +16 tokens per session b3e99e470be1
- 1mo ago First seen · 294 lines · 112 tokens per session scan A 949c6f6425e1
storyboard-html-preview is a skill published in the GitHub repository whystrohm/shotkit (23 stars, last pushed 27d ago), licensed Apache-2.0. It adds 128 tokens to every session and 3,290 once invoked, about $0.0005 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-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…