What is process-storyboard-tasks?

A workflow for processing pending Codex Storyboard image and video generation tasks. A storyboard is a shot-by-shot plan for a visual project.

Use it to process all pending shots, one storyboard row, or image, HyperFrames, and Remotion outputs.

It turns queued storyboard requests into generated assets and keeps the local storyboard updated. It also checks whether the required generation tools are available before starting.

process-storyboard-tasks — Skill for Claude Code and Codex by Yuuhann1

Install

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.

Any agent

npx skills add Yuuhann1999/codex-storyboard --skill process-storyboard-tasks

Clone the repo

git clone --depth 1 https://github.com/Yuuhann1999/codex-storyboard

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/yuuhann1999/codex-storyboard/process-storyboard-tasks/github.svg)](https://agentmods.dev/skills/yuuhann1999/codex-storyboard/process-storyboard-tasks)

Your own site

<a href="https://agentmods.dev/skills/yuuhann1999/codex-storyboard/process-storyboard-tasks"><img src="https://agentmods.dev/badge/skills/yuuhann1999/codex-storyboard/process-storyboard-tasks/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/yuuhann1999/codex-storyboard/process-storyboard-tasks"><img src="https://agentmods.dev/badge/skills/yuuhann1999/codex-storyboard/process-storyboard-tasks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,224 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

medium MCP Rug Pull · line 31
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.

Fix: Pin the version: npx @scope/[email protected]

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00060	$0.01224
Opus 5	$0.00030	$0.00612
Sonnet 5	$0.00012	$0.00245
Haiku 4.5	$0.00006	$0.00122

Measured 12d ago against content hash 7cafe01abddd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

process-storyboard-tasks 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.

plugins/codex-storyboard/skills/process-storyboard-tasks/SKILL.md · 68 lines

How it starts

The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Process Codex Storyboard Tasks

Process the local storyboard queue. The MCP tools start the bundled local app automatically when needed and default to http://127.0.0.1:43218.

If the current Codex session does not expose Storyboard MCP tools such as list_storyboard_generation_tasks, claim_storyboard_generation_task, or complete_storyboard_generation_task, first use tool_search to search for codex storyboard and load the deferred tools. Only if tool_search is unavailable or cannot find them, tell the user to start a new Codex conversation or restart Codex so plugin tools are reloaded.

Workflow

Call list_storyboard_generation_tasks with status pending.
Inspect the generators used by the pending tasks and verify the matching local capabilities before claiming anything:
- image-gen requires the built-in imagegen skill and image generation tool.
- hyperframes requires the HyperFrames and HyperFrames CLI skills.
- remotion requires the Remotion skill and its local rendering toolchain.
If a required capability is unavailable, do not claim affected tasks. Report the exact missing capability and continue with tasks whose generators are available.
Probe the local environment with read-only checks before deciding to install anything:
- Check Node.js, npm, and pnpm availability and versions.
- Check whether the task outputDir, active workspace, or chosen render directory already has package.json, a lockfile, and node_modules.
- Check for local CLIs with existing project commands such as pnpm exec ..., npm run ..., or executable files under node_modules/.bin.
- Check for global CLIs only with non-installing commands such as command -v, where, or direct --version after the command is found.
- Check whether Chromium, FFmpeg, or tool-specific render caches already exist when the selected renderer needs them.
Do not use commands that can implicitly download packages as probes. Do not run npx remotion, pnpm dlx, or package-manager exec forms that will install missing packages merely to test availability.

Read the full file on GitHub · 68 lines

Changes

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 · 68 lines · 60 tokens per session scan A 7cafe01abddd

Subscribe to this mod's changes

process-storyboard-tasks is a skill published in the GitHub repository Yuuhann1999/codex-storyboard (327 stars, last pushed 2mo ago), licensed MIT. It adds 60 tokens to every session and 1,224 once invoked, about $0.0003 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.

Creative and media ai-video codex mcp openai storyboard

process-storyboard-tasks

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Process Codex Storyboard Tasks

Workflow

What this file has done since we first saw it

Other skills, from other repositories

video-prompt-engineer

video-storyboard-gen

storyboard-designer

image-generation

powerpoint

gifgrep