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 getcrew44/crew44 --skill storyboardgit clone --depth 1 https://github.com/getcrew44/crew44Wrote 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/getcrew44/crew44/storyboard)<a href="https://agentmods.dev/skills/getcrew44/crew44/storyboard"><img src="https://agentmods.dev/badge/skills/getcrew44/crew44/storyboard.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.1 | $0.00034 | $0.02550 |
| Opus 5 | $0.00017 | $0.01275 |
| Sonnet 5 | $0.00007 | $0.00510 |
| Haiku 4.5 | $0.00003 | $0.00255 |
Grade A, and why
storyboard 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 7d 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Create a 6-frame visual narrative that tells the story of a user's journey from problem to solution, using the classic storytelling arc to build empathy, illustrate value, and make abstract product concepts concrete. Use this to align stakeholders, pitch features, communicate vision, or test if your solution resonates emotionally before building it.
This is not a UI mockup—it's a storytelling tool that brings the human side of your product to life.
Key Concepts
The 6-Frame Storyboard Structure
Based on classic narrative arcs, the 6-frame format follows this pattern:
- Frame 1: Main Character — Introduce the persona and their context
- Frame 2: The Problem Emerges — Show the challenge or obstacle they face
- Frame 3: The "Oh Crap" Moment — Escalate the problem to create urgency
- Frame 4: The Solution Appears — Introduce your product/feature
- Frame 5: The "Aha" Moment — Show the user experiencing the breakthrough
- Frame 6: Life After the Solution — Illustrate the improved state
Why This Works
- Emotional engagement: Stories create empathy in ways specs can't
- Concrete over abstract: Visual narrative makes vague concepts tangible
- Memorable: People remember stories better than feature lists
- Alignment tool: Stakeholders can react to a story and give feedback
- Low-fidelity: Doesn't require polished design—sketches work great
Anti-Patterns (What This Is NOT)
- Not a user flow diagram: This is emotional storytelling, not process documentation
- Not a feature demo: Focus on user outcomes, not product capabilities
- Not marketing copy: Authentic narrative, not hype
When to Use This
- Pitching a new product or feature to stakeholders
- Aligning teams on user value (product, design, engineering, execs)
- Testing if a product idea resonates emotionally
- Communicating vision at all-hands or investor meetings
- Validating problem/solution fit before building
When NOT to Use This
- For technical implementation details (use architecture diagrams instead)
- When the user problem is trivial or well-understood
- As a replacement for user research (storyboards illustrate insights, don't create them)
What ships with it
2 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.
- 7d ago First seen · 253 lines · 34 tokens per session scan A c8582383226a
storyboard is a skill published in the GitHub repository getcrew44/crew44 (359 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 2,550 once invoked, about $0.0002 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
brand-visual-quality
A quality-review workflow for brand visual assets such as logos, icons, theme variants, small-size optical adjustments, and monochrome masters.
tavern-management
Use when the user asks to import or translate an Lfcode Tavern or SillyTavern character card or worldbook, including PNG image cards, or manage the Tavern plugin lifecycle.
ai-video-generation
Generate AI videos with Google Veo, Seedance, Wan, Grok and 40+ models via inference.sh CLI. Models: Veo 3.1, Veo 3, Seedance 1.5 Pro, Wan 2.5, Grok Imagine Video, OmniHuman, Fabric, HunyuanVideo. ...
brandkit
Premium brand-kit image generation skill for creating high-end brand-guidelines boards, logo systems, identity decks, and visual-world presentations. Trained for minimalist, cinematic, editorial, dark-tech, luxury, cultural, security, gaming, developer-tool, and consumer-app brand systems. Optimized for intentional…
slide-deck-builder
Use when the user asks to create, revise, restructure, or quality-check a presentation or slide deck. Inspect the source deck, template, assets, audience, and available rendering tools first, then validate slide structure and rendered layout before claiming completion.
imagemaker
Use when the user asks to generate, revise, configure, manage, insert, or export images with the Lfcode ImageMaker plugin or its supported image-generation APIs.