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/laith0003/ux-skill/ux-motiongit clone --depth 1 https://github.com/Laith0003/ux-skillWrote 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/commands/laith0003/ux-skill/ux-motion)<a href="https://agentmods.dev/commands/laith0003/ux-skill/ux-motion"><img src="https://agentmods.dev/badge/commands/laith0003/ux-skill/ux-motion.svg" alt="Measured on agentmods" 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.00104 | $0.03518 |
| Opus 5 | $0.00052 | $0.01759 |
| Sonnet 5 | $0.00021 | $0.00704 |
| Haiku 4.5 | $0.00010 | $0.00352 |
Grade A, and why
ux-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 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.
How it starts
The opening of the file, as written. The whole thing — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ux-motion
You are running the /ux-motion command from the ux plugin. The job is to evaluate every animation on a surface against five dimensions — timing, easing, meaning, reduced-motion compliance, performance — and identify what to keep, what to tune, and what to kill.
When to use
Triggers: "motion check", "are the animations good", "fix the motion", "review the animations", "motion audit", "is this too much animation", "the motion feels off", "performance pass on the motion".
Use after building a motion-rich surface, after a redesign that added new transitions, or when something "feels wrong" but the user cannot name it. Not for layout or copy issues — those are /ux-audit and /ux-copy.
Input
One of: a live URL (preferred — motion is observable), a screen recording, a CSS/JS file with animation definitions, or a code snippet. Static screenshots are insufficient — flag and request a recording or live URL.
Process
1. Inventory every animation
List every animation present, including:
- CSS transitions on hover, focus, active states.
- CSS keyframe animations (loaders, indicators, attention-grabbers).
- JS-driven animations (libraries: GSAP, Framer Motion, Motion One, Web Animations API).
- Scroll-linked animations (parallax, scroll-tied transforms, scroll-triggered reveals).
- Page-transition animations.
- Micro-interactions (button press, checkbox tick, toggle slide).
- Implicit animations (carousel auto-advance, marquee, autoplay video).
For each, note: trigger, duration, easing, properties animated, scope (single element or page-wide).
2. Evaluate each animation on five dimensions
Dimension 1 — Timing
- Micro-interactions (button press, hover state, checkbox tick): 150–250ms. Anything ≥ 300ms feels sluggish on micro.
- Component transitions (modal open, drawer slide, toast appear): 200–300ms.
- Complex transitions (page transitions, multi-element choreography): up to 400ms — beyond that, the user starts waiting.
- Loaders / indicators: continuous, but the loop should be 800–1500ms to feel alive without nagging.
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 · 303 lines · 104 tokens per session scan A eed0cca2369b
ux-motion is a command published in the GitHub repository Laith0003/ux-skill (66 stars, last pushed 1mo ago), licensed MIT. It adds 104 tokens to every session and 3,518 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-08-30.
Other commands, from other repositories
design-system
Generate design tokens, theme configuration, or extract a design system from existing code or Figma files.
figma-sync
Detect drift between Figma designs and code implementation — compare tokens, spacing, colors, typography, and component structure.
motion-designer
Use when animation feels wrong. Transitions too slow or too bouncy, motion with no purpose, blanket transitions on every property, no reduced-motion support, or animation that drops frames.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
spacing-layout-specialist
Use when spacing looks arbitrary. Padding and margins off any scale, inconsistent gaps between the same components, no grid underneath, or a layout that needs a denser mode.
add-library
Kullanıcı "kütüphane ekle", "library ekle", "tasarım sistemi ekle", "design system ekle" dediğinde bu komutu uygula.