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 imyousuf/storytelling-media-mcp --skill movie-production-pipelinegit clone --depth 1 https://github.com/imyousuf/storytelling-media-mcpWrote 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/imyousuf/storytelling-media-mcp/movie-production-pipeline)<a href="https://agentmods.dev/skills/imyousuf/storytelling-media-mcp/movie-production-pipeline"><img src="https://agentmods.dev/badge/skills/imyousuf/storytelling-media-mcp/movie-production-pipeline/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/imyousuf/storytelling-media-mcp/movie-production-pipeline"><img src="https://agentmods.dev/badge/skills/imyousuf/storytelling-media-mcp/movie-production-pipeline.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.00081 | $0.01221 |
| Opus 5 | $0.00041 | $0.00611 |
| Sonnet 5 | $0.00016 | $0.00244 |
| Haiku 4.5 | $0.00008 | $0.00122 |
Grade A, and why
movie-production-pipeline 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Movie Production Pipeline
Run a gated, multi-agent movie development workflow. The user owns creative approval. Do not move from one stage to the next until the user gives explicit approval such as "approved", "continue", "move on", or an equivalent instruction.
Operating Rules
- Start by locating the movie project directory and primary brief. If unclear, ask for the path.
- Create or reuse
production/inside the movie project for generated artifacts.- If an output file already exists, read it first and either update it intentionally or create a timestamped draft under the same stage directory. Never overwrite prior approved artifacts silently.
- If the user asks for planning only or says not to edit files, return the stage plan and proposed artifact contents in the response without writing files.
- Treat each stage as a review gate:
- run the stage,
- write artifacts,
- summarize decisions and open questions,
- ask for user feedback,
- iterate until approved.
- Use sub-agents for the first analytical pass of each stage when the user has explicitly asked for this skill or multi-agent execution and sub-agent tools are available. In Codex sessions with
spawn_agent, useexplorerfor analysis-only passes andworkeronly for disjoint file-writing assignments. If sub-agent tools are unavailable, state that limitation and perform the first-pass roles locally. - Do not duplicate sub-agent work locally. Integrate their outputs, resolve conflicts, and mark assumptions.
- Preserve rights and sensitivity concerns. Flag copyrighted source-universe issues, real-world political sensitivity, and procedural weaponization risk.
- Keep generated tactical material cinematic and non-instructional. Avoid step-by-step weapon construction, drone weaponization procedures, or operational evasion instructions.
- Prefer structured files over prose-only outputs.
Stage Gates
Use these stages in order unless the user explicitly jumps to a later stage:
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.
- 12d ago First seen · 103 lines · 81 tokens per session scan A 6746c066fd5c
movie-production-pipeline is a skill published in the GitHub repository imyousuf/storytelling-media-mcp (1 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 81 tokens to every session and 1,221 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-31.
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…