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 agentmods add commands/pushingsquares/pushing-creation/frames-shotlistgit clone --depth 1 https://github.com/PUSHINGSQUARES/pushing-creationWhat 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 | $0.00010 | $0.00982 |
| Opus 5 | $0.00005 | $0.00491 |
| Sonnet 5 | $0.00002 | $0.00196 |
| Haiku 4.5 | $0.00001 | $0.00098 |
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 3d 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 — 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.mdexists and isn't empty. If missing: "Run/frames-brainstormfirst to build your style pack, or hand-editstyle.mdfrom the starter template." Stop here. - Confirm
projects/<slug>/storyboard.mdexists. - If
storyboard.mdalready 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 |
|------|----------|-------|--------|------|--------|--------|------|-------|-----|------|----------|
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.
- 3d ago First seen · 89 lines · 10 tokens per session scan A 01b295578532
frames-shotlist is a command published in the GitHub repository PUSHINGSQUARES/pushing-creation (9 stars, last pushed 3mo ago), licensed MIT. It adds 10 tokens to every session and 982 once invoked, about $0.0001 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 commands, from other repositories
al
Run AgentLint diagnostic across all projects. Use when: user says /al, 'check all projects', 'agent lint', or '体检'.
tldr
Re-apply TLDR rules for this turn (verdict first, no filler).
moyu-lite
Invoke the moyu:moyu-lite skill and follow it exactly.
context
上下文管理，加载项目信息（会话级，另见 /cc-best:memory 管理持久记忆）.
audit-plugin
Audit plugin skills, commands, and agents for structure, size, and naming issues.
lfe-dep-audit
Inspector sub-skill. Reviews dependency manifest files (package.json, requirements.txt, go.mod, Cargo.toml, pom.xml) changed in the current diff for risky version patterns and stale majors. Emits a human-run audit instruction rather than executing tools. Writes .plans/checks/depfindings.md. Called by lfe-inspector…