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 ssmurfgg04-gif/context-m --skill storyboard-managergit clone --depth 1 https://github.com/ssmurfgg04-gif/context-mWrote 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/ssmurfgg04-gif/context-m/storyboard-manager)<a href="https://agentmods.dev/skills/ssmurfgg04-gif/context-m/storyboard-manager"><img src="https://agentmods.dev/badge/skills/ssmurfgg04-gif/context-m/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/ssmurfgg04-gif/context-m/storyboard-manager"><img src="https://agentmods.dev/badge/skills/ssmurfgg04-gif/context-m/storyboard-manager.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.00085 | $0.03783 |
| Opus 5.5 | $0.00034 | $0.01513 |
| Sonnet 5.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 1mo 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.
This is a copy
100% identical to storyboard-manager — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 1mo ago First seen · 533 lines · 85 tokens per session scan A 4f818c9718b9
storyboard-manager is a skill published in the GitHub repository ssmurfgg04-gif/context-m (2 stars, last pushed today), licensed Apache-2.0. It adds 85 tokens to every session and 3,783 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to storyboard-manager, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
agent-memory-discipline
Rules for when an agent should recall from long-term memory before acting and when it should save decisions, corrections and failures afterwards. Works with any memory backend.
context-engineering
A guide to organizing the instructions and information an AI agent receives at each step. It covers system prompts, tool descriptions, conversation history, on-demand skills, and protections against unsafe outside content.
kv-cache-design
A guide to arranging an AI agent's conversation so previously processed text can be reused. A KV cache stores intermediate results for earlier tokens, while a prompt cache reuses a stable beginning across requests.
agent-evaluation
A guide to measuring whether an AI agent works reliably on the tasks that matter. It covers repeatable test environments, program checks, human-like scoring rules, failure analysis, and experiments that separate model problems from system problems.
post-training-strategy
A guide to choosing and planning ways to improve an AI model after its initial training. It explains when to add knowledge, teach a response format, use trial-and-error training, or use a smaller model to learn from a larger one.
ai-style
A Chinese-language writing guide for producing or revising reader-facing text such as product announcements, public-account articles, emails, and README files. It focuses on reducing patterns that make writing sound machine-generated.