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 2233admin/design-pipeline --skill shot-compositiongit clone --depth 1 https://github.com/2233admin/design-pipelineWrote 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/2233admin/design-pipeline/shot-composition)<a href="https://agentmods.dev/skills/2233admin/design-pipeline/shot-composition"><img src="https://agentmods.dev/badge/skills/2233admin/design-pipeline/shot-composition/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/2233admin/design-pipeline/shot-composition"><img src="https://agentmods.dev/badge/skills/2233admin/design-pipeline/shot-composition.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.00101 | $0.03292 |
| Opus 5 | $0.00051 | $0.01646 |
| Sonnet 5 | $0.00020 | $0.00658 |
| Haiku 4.5 | $0.00010 | $0.00329 |
Grade A, and why
shot-composition 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 6d 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 shot-composition — 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shot Composition
Stage the frame and move the camera: grid systems, safe areas, focal hierarchy, negative space, parallax layering, and how layout guides the eye over time. Produces composition notes, layer structure (bg/mid/fg), and concrete camera-move plans with numbers.
When to use
- Defining a frame's layout, focal point, and negative space.
- Planning element enter/exit directions and motion paths.
- Designing camera push/pull, pan, follow, and parallax moves.
- Adapting one composition across 16:9, 9:16, and 1:1 with safe areas.
Decision tree
What are you staging?
├─ A static frame's layout
│ └─ set grid → place ONE focal point on a thirds power point
│ → rank hierarchy (size>contrast>color>position) → reserve negative space
├─ Where things enter / leave
│ └─ follow reading direction; nearest edge; ease-out in, ease-in out
│ (new content → from right/below; back/undo → reverse it)
├─ A sense of depth / a camera move
│ └─ split into bg/mid/fg layers (the three motion layers)
│ → ONE camera move per beat (push | pan | follow | parallax), ease-in-out
└─ One comp across aspects (16:9 / 9:16 / 1:1)
└─ master in 16:9, focal in the center band → RESTACK (don't crop) for 9:16
→ keep critical content inside title-safe margins
Cross-reference — apply the shared frameworks. This skill is the spatial half of animation-principles. Apply them explicitly:
- 1/3 Rule (
animation-principles) has two forms and this skill uses both spatially: (a) Composition thirds — place the focal point on a rule-of-thirds power point (33%/67%); (b) Distance — no element travels more than ~1/3 of the frame without an intermediate keyframe or a scale/opacity change, so entrances stay readable. - Three motion layers (
animation-principles: Primary / Secondary / Ambient) map directly onto depth: foreground = Primary (the move the eye follows), midground = Secondary (the subject + supporting reactions), background = Ambient (slow, low-contrast life). Parallax speed scales with that role. - Settle the Three Pillars (Emotional intent / Visual narrative / Motion craft) and the chosen Motion Personality (
motion-art-direction) before numbering a camera move — premium wants slow long pushes, energetic wants whip-pans.
What ships with it
2 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.
- 6d ago First seen · 186 lines · 101 tokens per session scan A c2bbedc1d615
shot-composition is a skill published in the GitHub repository 2233admin/design-pipeline (9 stars, last pushed 7d ago), licensed MIT. It adds 101 tokens to every session and 3,292 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to shot-composition, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
ss-lint
Quick automated lint — detects common design system violations in seconds.
omd-apply
A skill that applies a project's DESIGN.md file as visual and brand guidance for interface work. It covers components, colors, fonts, layout, copy, motion, and visual assets.
ss-review
Review UI code for design system compliance, accessibility, and best practices.
design-system-tokens
Design token management with the W3C Design Token spec, three-tier hierarchy (global/alias/component), OKLCH color, Style Dictionary transforms, and dark mode theming. Use when creating token files, implementing theme systems, or building design-to-code pipelines.
system-benchmark
Benchmark a design system against industry standards and comparable public systems, producing a qualitative comparison across dimensions with specific, named reference points. Goes beyond an internal health assessment to answer 'how does our system compare to what good looks like out there?' Trigger when someone says…
token-documentation
Write documentation for design tokens — covering semantic intent, usage context, and do/don't examples. Trigger when someone says: document these tokens, token reference, what does this token mean, token usage guide, write the token docs, token intent, or anything about creating human-readable documentation for design…