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 markoblogo/abvx-agent-skills --skill motion-review-gategit clone --depth 1 https://github.com/markoblogo/abvx-agent-skillsWrote 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/markoblogo/abvx-agent-skills/motion-review-gate)<a href="https://agentmods.dev/skills/markoblogo/abvx-agent-skills/motion-review-gate"><img src="https://agentmods.dev/badge/skills/markoblogo/abvx-agent-skills/motion-review-gate/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/markoblogo/abvx-agent-skills/motion-review-gate"><img src="https://agentmods.dev/badge/skills/markoblogo/abvx-agent-skills/motion-review-gate.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.00082 | $0.00981 |
| Opus 5 | $0.00041 | $0.00491 |
| Sonnet 5 | $0.00016 | $0.00196 |
| Haiku 4.5 | $0.00008 | $0.00098 |
Grade A, and why
motion-review-gate 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 11d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Motion Review Gate
Review motion as a pre-ship gate. This skill does not design a whole interface and does not rewrite unrelated frontend code.
Use it after implementation or during review when the diff includes animation, transitions, gestures, Lottie assets, interaction states, or motion-heavy UI polish.
Pair it with browser-verification when the visual behavior must be checked in a real browser.
When a diff includes drag, swipe, momentum, snap points, or another direct-manipulation gesture, also run fluid-interaction-review; this gate alone does not fully verify gesture physics.
Use For
- CSS transitions, keyframes,
@starting-style, WAAPI, Framer Motion, Motion, or Lottie changes; - drawers, popovers, menus, dropdowns, tooltips, toasts, command palettes, modals, hover states, press states, and gestures;
- frontend diffs where animation might hurt speed, accessibility, or product feel;
- checking whether motion should be removed rather than polished.
Do Not Use For
- general frontend critique without motion-specific risk;
- visual hierarchy, brand direction, or typography review without interaction/motion changes;
- full accessibility or performance audits beyond animation-related issues.
Review Order
- Purpose — every animation must serve feedback, spatial consistency, state indication, explanation, or prevention of jarring change.
- Frequency — keyboard-triggered and 100+ times/day actions should not animate; frequent actions should be reduced.
- Timing and easing — most UI motion stays under 300ms; avoid
ease-infor UI response; prefer strong ease-out or appropriate custom curves. - Physicality — avoid
scale(0); popovers, menus, and tooltips should originate from their trigger; modals can stay centered. - Interruptibility — rapidly triggered UI should retarget smoothly; prefer transitions or springs over restart-prone keyframes.
- Performance — animate
transformandopacity; avoid layout properties and parent CSS-variable recalc storms. - Accessibility — respect
prefers-reduced-motion; gate hover motion behind real hover media queries. - Cohesion — motion should match the product surface: crisp for dashboards, more expressive only when the brand or moment earns it.
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.
- 11d ago First seen · 88 lines · 82 tokens per session scan A 9bad3a7be864
motion-review-gate is a skill published in the GitHub repository markoblogo/abvx-agent-skills (16 stars, last pushed 2d ago), licensed MIT. It adds 82 tokens to every session and 981 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-30.
Other skills, from other repositories
docs-release-notes
Use when a change needs a user-visible release-note, changelog, or changeset entry — "add a release note", "add a changeset for this", "what goes in the changelog?", "write up what shipped", "note this for the next release" — or when finalizing a branch whose customer-visible features, bug fixes, or UI changes should…
writing-web
Simple web development with HTML, CSS, JS, and HTMX. Use when working with .html, .css, or .htmx files, web templates, stylesheets, or vanilla JS scripts. NOT for React/Vue/Angular (use writing-typescript) or Node.js backends.
axiom-auto-layout-debugging
Use when encountering "Unable to simultaneously satisfy constraints" errors, constraint conflicts, ambiguous layout warnings, or views positioned incorrectly - systematic debugging workflow for Auto Layout issues in iOS.
fe-spec
Converts requirements for a new frontend feature into a structured spec. Use when: before starting a new feature, when feature.md needs to be written, or when converting a planning doc into a dev spec. Do NOT load for: bug fixes, refactoring, simple style changes.
review-animations
Reviews animation and motion code against a high craft bar derived from Emil Kowalski's design engineering philosophy. Default to flagging; approval is earned.
fixing-motion-performance
Audit and fix animation performance issues including layout thrashing, compositor properties, scroll-linked motion, and blur effects. Use when animations stutter, transitions jank, or reviewing CSS/JS animation performance.