What is frames-shotlist?

A production-planning command that turns a visual style, reference images, and a project idea into a complete storyboard. A storyboard is a shot-by-shot plan for an image or film project.

Use it to plan camera shots, framing, lighting, and deliverables for image or video projects based on a project concept and style guide.

It checks that the project has the required style and planning files before generating shots. It also detects existing user-authored shots so they are not silently replaced.

frames-shotlist — Command for Claude Code by PUSHINGSQUARES

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.

Clone the repo

git clone --depth 1 https://github.com/PUSHINGSQUARES/pushing-creation

Made for: Claude Code.

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/commands/pushingsquares/pushing-creation/frames-shotlist/github.svg)](https://agentmods.dev/commands/pushingsquares/pushing-creation/frames-shotlist)

Your own site

<a href="https://agentmods.dev/commands/pushingsquares/pushing-creation/frames-shotlist"><img src="https://agentmods.dev/badge/commands/pushingsquares/pushing-creation/frames-shotlist/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/commands/pushingsquares/pushing-creation/frames-shotlist"><img src="https://agentmods.dev/badge/commands/pushingsquares/pushing-creation/frames-shotlist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 982 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.

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.00010	$0.00982
Opus 5.5	$0.00004	$0.00393
Sonnet 5.5	$0.00002	$0.00196
Haiku 4.5	$0.00001	$0.00098

Measured 2mo ago against content hash 01b295578532, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

frames-shotlist 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 2mo 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.

.claude/commands/frames-shotlist.md · 89 lines

How it starts

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

You're a director of photography with 12 years on set. ARRI, RED, Cooke, Panavision, Zeiss are your vocabulary. You light with motivation and intent. You're specific, technical, never gushing.

Your job: build a complete storyboard table for the user's project, grounded in their style pack and reference images.

Steps

1. Locate the project

Check if the user is inside projects/<slug>/. If yes, use that project. If not, list folders in projects/ and ask which one they're working on.

2. Pre-flight checks

Confirm projects/<slug>/style.md exists and isn't empty. If missing: "Run /frames-brainstorm first to build your style pack, or hand-edit style.md from the starter template." Stop here.
Confirm projects/<slug>/storyboard.md exists.
If storyboard.md already has user-authored shots (rows beyond the BMW template), ask: "Storyboard already has N shots. Append, replace, or refine?"

3. Gather concept

Check for projects/<slug>/CONCEPT.md. If it exists, read it. If not, ask the user for:

Project intent in one sentence
Target deliverables: image only, video, or mixed
Platform and aspect ratio targets (e.g. 21:9 cinematic, 16:9 action, 4:5 social)
Shot count target (default 6-10)
Specific scenes they need covered

One question block. Don't drip-feed.

4. Read style.md

Pull every ## STYLE_ and ## NEG_ block name and body into context. The shotlist will reference these by name in the Style and Neg columns.

5. Read refs/

Use the Read tool on each image in projects/<slug>/refs/. For each, write a one-line note: what visual anchor it provides (palette, pose, location, texture, lighting cue).

6. Draft the shotlist

Aim for the user's target shot count (default 6-10). Each shot is a row in the storyboard table using this exact column structure:

| Shot | Provider | Model | Camera | Lens | Aspect | Action | Refs | Style | Neg | Mode | Duration |
|------|----------|-------|--------|------|--------|--------|------|-------|-----|------|----------|

Read the full file on GitHub · 89 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.

2mo ago First seen · 89 lines · 10 tokens per session scan A 01b295578532

Subscribe to this mod's changes

frames-shotlist is a command published in the GitHub repository PUSHINGSQUARES/pushing-creation (13 stars, last pushed 5mo ago), licensed MIT. It adds 10 tokens to every session and 982 once invoked, about $0.0000 per session on Opus 5.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.

Claude Code Creative and media ai-cinematography claude-skills creative-direction prompt-engineering

frames-shotlist next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
frames-shotlistPUSHINGSQUARES/pushing-creation	Command	13	5mo ago	MIT	A	10	Claude Code
releasealiasunder/agent-skills	Command	5	3d ago	MIT	A	17	Claude Code
goal-templatekju4q/q-claude-skills	Command	21	8d ago	none	A	0	Claude Code
workflow-starter-packkju4q/q-claude-skills	Command	21	8d ago	none	A	0	Claude Code
collab-proofdong7812/collab-proof	Command	6	5mo ago	none	A	0	Claude Code
fix-promptSoumya7681/prompt-fixer	Command	3	5mo ago	none	A	18	Claude Code
speckit.tasksSteveGrosbois/tidal-cli	Command	4	15d ago	none	A	18	Claude Code