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 ailabs-393/ai-labs-claude-skills --skill storyboard-managergit clone --depth 1 https://github.com/ailabs-393/ai-labs-claude-skillsWrote 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/ailabs-393/ai-labs-claude-skills/storyboard-manager)<a href="https://agentmods.dev/skills/ailabs-393/ai-labs-claude-skills/storyboard-manager"><img src="https://agentmods.dev/badge/skills/ailabs-393/ai-labs-claude-skills/storyboard-manager/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/ailabs-393/ai-labs-claude-skills/storyboard-manager"><img src="https://agentmods.dev/badge/skills/ailabs-393/ai-labs-claude-skills/storyboard-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
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.00085 | $0.03783 |
| Opus 5 | $0.00043 | $0.01892 |
| Sonnet 5 | $0.00017 | $0.00757 |
| Haiku 4.5 | $0.00009 | $0.00378 |
Grade A, and why
storyboard-manager 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 12d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- storyboard-manager — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 533 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Storyboard Manager
Overview
The Storyboard Manager skill equips Claude with specialized knowledge and tools for creative writing workflows. It provides frameworks for character development, story structure patterns, automated timeline tracking, and consistency checking across narrative projects. This skill automatically adapts to various storyboard folder structures while maintaining best practices for novel, screenplay, and serialized fiction writing.
Core Capabilities
The skill provides four main capabilities:
1. Character Development & Management
Support creating deep, consistent character profiles with backstories, arcs, and relationships.
2. Story Planning & Structure
Guide plot development using established frameworks (Three-Act, Hero's Journey, Save the Cat, etc.) and help organize narrative elements.
3. Chapter & Scene Writing
Generate chapter content, scene breakdowns, and dialogue that maintains consistency with established characters and plot.
4. Timeline Tracking & Consistency Checking
Use automated tools to verify chronological consistency, character continuity, and world-building coherence.
Detecting Project Structure
The Storyboard Manager automatically detects and adapts to various folder organizations. Look for these common directory patterns:
Character folders: characters/, Characters/, cast/, Cast/
Chapter folders: chapters/, Chapters/, scenes/, Scenes/, story/
Planning folders: story-planning/, planning/, outline/, notes/
Summary files: summary.md, README.md, overview.md
When triggered, scan the project root to identify the structure and adjust workflows accordingly. If no standard structure exists, recommend organizing files using the pattern: characters/, chapters/, story-planning/, and summary.md.
Workflow Decision Tree
Use this decision tree to determine the appropriate workflow:
User Request
├─ Character-related? ("develop character," "create backstory," "character arc")
│ └─ → Character Development Workflow
│
├─ Planning/Plot? ("outline story," "plan act 2," "plot structure")
│ └─ → Story Planning Workflow
│
├─ Writing content? ("write chapter," "generate scene," "continue story")
│ └─ → Chapter/Scene Writing Workflow
│
└─ Checking/Analysis? ("check consistency," "track timeline," "find contradictions")
├─ Timeline? → Use timeline_tracker.py script
└─ Consistency? → Use consistency_checker.py script
What ships with it
6 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.
- 12d ago First seen · 533 lines · 85 tokens per session scan A 4f818c9718b9
storyboard-manager is a skill published in the GitHub repository ailabs-393/ai-labs-claude-skills (445 stars, last pushed 10mo ago), licensed MIT. It adds 85 tokens to every session and 3,783 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…