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 ZachArticulateV/designer-pro-and-seo --skill design-motiongit clone --depth 1 https://github.com/ZachArticulateV/designer-pro-and-seoWrote 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/zacharticulatev/designer-pro-and-seo/design-motion)<a href="https://agentmods.dev/skills/zacharticulatev/designer-pro-and-seo/design-motion"><img src="https://agentmods.dev/badge/skills/zacharticulatev/designer-pro-and-seo/design-motion/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/zacharticulatev/designer-pro-and-seo/design-motion"><img src="https://agentmods.dev/badge/skills/zacharticulatev/designer-pro-and-seo/design-motion.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.00081 | $0.00672 |
| Opus 5 | $0.00041 | $0.00336 |
| Sonnet 5 | $0.00016 | $0.00134 |
| Haiku 4.5 | $0.00008 | $0.00067 |
Grade A, and why
design-motion 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 13d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
design-motion
Family: design Status: Stable
Purpose
The implementation counterpart to design-dimensions dimension 5. That skill
specifies motion; nothing builds it. This emits production-ready CSS (and
minimal JS where needed) from a design system's motion tokens — so "the brief said
250ms ease-out micro-interactions" becomes actual code, with an accessibility-safe
reduced-motion fallback every time.
Triggers
- "add motion" / "animate this" / "make it feel alive"
- "implement the animations" / "micro-interactions"
- "scroll animations" / "page transitions"
Inputs
- Motion tokens (duration, easing) — from a design system /
design-system-gen - The elements/sections to animate and the desired feel
- Stack (vanilla CSS/JS, Tailwind, React, etc.)
Steps
- Read the motion tokens — base duration + easing from the design system (e.g.
200ms ease-out). If absent, propose sensible defaults and note it. - Emit the reduced-motion guard first — wrap motion so
@media (prefers-reduced-motion: reduce)disables/reduces it. This is non-negotiable (accessibility). - Generate the motion set for the target stack:
- Entrance/scroll — fade/slide-in on intersection (IntersectionObserver, or CSS scroll-driven animations where supported), respecting the token timing.
- Micro-interactions — hover, press, and focus-visible states (focus parity matters for keyboard users).
- Transitions — section/page transitions using the token easing.
- Keep it performant — animate
transform/opacityonly; avoid layout- thrashing properties; no animation on the LCP element's first paint. - Deliver code ready to paste, plus a one-line note on where to place it.
Offer to run
design-accessibilityto confirm reduced-motion behavior.
Outputs
- Paste-ready CSS/JS (or framework equivalent) for the requested motion
- A required
prefers-reduced-motionfallback block - Performance notes (transform/opacity-only, LCP-safe)
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.
- 13d ago First seen · 65 lines · 81 tokens per session scan A 4f88b09244ec
design-motion is a skill published in the GitHub repository ZachArticulateV/designer-pro-and-seo (8 stars, last pushed 2mo ago), licensed MIT. It adds 81 tokens to every session and 672 once invoked, about $0.0004 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 skills, from other repositories
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
web-design
A web design workflow for turning a brief, reference website, screenshot, or keywords into a design specification and then web code. It covers visual style, page structure, interaction, responsive layouts, and motion.
design-to-code-check
Check alignment between a specific design specification and its code implementation — a focused, single-component or single-screen comparison. Trigger when someone says: does this match the design, check implementation, design code alignment, what's different between the design and the build, spec check…
design-with-claude
Use when design work needs a product designer's eye: auditing a codebase for design-system gaps, fixing WCAG contrast and unlabeled inputs, choosing type scales or spacing steps, reviewing UI that looks generic or AI-generated, or designing forms, tables, dashboards, navigation, checkout, onboarding, dark mode, and…
Component Variants / States Documentation コンポーネント状態の文書化
A code review check for new reusable interface components and the variations and states they support, such as hover, focus, disabled, loading, and error states.
Design Source-of-Truth Conformance デザイン定義準拠
A code review check that compares new interface values—such as colors, spacing, font sizes, rounded corners, and shadows—with the project's documented design rules or token files. It only runs when those design definitions exist.