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 motion-pricinggit 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/motion-pricing)<a href="https://agentmods.dev/skills/2233admin/design-pipeline/motion-pricing"><img src="https://agentmods.dev/badge/skills/2233admin/design-pipeline/motion-pricing/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/motion-pricing"><img src="https://agentmods.dev/badge/skills/2233admin/design-pipeline/motion-pricing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00092 | $0.02946 |
| Opus 5 | $0.00046 | $0.01473 |
| Sonnet 5 | $0.00018 | $0.00589 |
| Haiku 4.5 | $0.00009 | $0.00295 |
Grade A, and why
motion-pricing 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 5d 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Motion Pricing
Produce a defensible quote for a motion design project: choose a pricing model, run the day-rate math, account for the real cost drivers, and output a clean line-itemed estimate the client can approve.
When to use
Use when pricing any motion/animation project, sanity-checking an existing number, setting or revisiting a day rate, or explaining to a client why a price is what it is. The output is a structured quote plus the reasoning behind each line.
Decision tree — which pricing model
Is the brief locked (scope, deliverables, revision cap all defined)?
├─ NO → bill DAY RATE (or refuse to fix-quote until the brief is locked).
│ Exploratory/discovery/retainer work is day-rate by nature.
└─ YES → Is the work a repeatable style or a series (many similar units)?
├─ YES → estimate in days, sanity-check PER-FINISHED-MINUTE,
│ present as fixed per-project.
└─ NO → Is it tied to large campaign / broadcast / paid spend
where the deliverable's value >> its production cost?
├─ YES → estimate in days for the floor, then apply
│ VALUE-BASED usage uplift on top.
└─ NO → estimate in days, present FIXED PER-PROJECT
with a revision cap. ← the default path.
Always estimate internally in days (the only honest unit of effort), whatever you bill on. The model above only decides what the client sees.
Step 1 — Pick a pricing model
| Model | Bill on | Best for | Watch out |
|---|---|---|---|
| Day rate | Days of work | Open-ended, exploratory, or retainer work | Penalises speed; client may haggle days |
| Per-project (fixed) | Whole deliverable | Well-scoped jobs with a locked brief | Scope creep eats margin — needs a revision cap |
| Per-finished-minute | Final runtime | Explainers, series, repeatable style | Ignores complexity differences minute-to-minute |
| Value-based | Outcome/usage to client | High-leverage brand/ad work | Requires knowing the client's stakes |
What ships with it
4 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.
- 5d ago First seen · 211 lines · 92 tokens per session scan A 1876f4ec30fc
motion-pricing is a skill published in the GitHub repository 2233admin/design-pipeline (9 stars, last pushed 6d ago), licensed MIT. It adds 92 tokens to every session and 2,946 once invoked, about $0.0005 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-09-04.
Other skills, from other repositories
business-design
Read financials, map competitive landscapes, and argue design decisions in the language of value. Use when defending design to commercial stakeholders. For the live negotiation itself, use design-negotiation (designer-toolkit).
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.
ss-pattern
Generate a composed UI pattern from the active StyleSeed grammar and brand recipe using existing primitives.
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.
governance-encoder
Convert governance policies into machine-executable JSON constraint files that AI agents and CI pipelines validate against automatically. This produces rule engine files in .ai/governance/, NOT narrative decision records or documentation. Trigger when someone says: encode governance rules, governance as code, automate…