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 rules/kevin-liu-01/loop/frontend-10x-motiongit clone --depth 1 https://github.com/Kevin-Liu-01/LoopWrote 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/rules/kevin-liu-01/loop/frontend-10x-motion)<a href="https://agentmods.dev/rules/kevin-liu-01/loop/frontend-10x-motion"><img src="https://agentmods.dev/badge/rules/kevin-liu-01/loop/frontend-10x-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 | $0.00613 | $0.00613 |
| Opus 5 | $0.00307 | $0.00307 |
| Sonnet 5 | $0.00123 | $0.00123 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
frontend-10x-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 4d 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.
What it actually says
Motion and 3D Rules
Motion is a system with three layers:
- ambient: slow loops, shader drift, environmental life
- interaction: hover, press, open, focus
- narrative: scroll and route choreography
Apply these rules:
- One strong hero move beats many small distractions.
- If a page has a heavy 3D or shader hero, quiet the rest of the UI.
- Do not propose plain CSS as the primary animation system by default.
- Use CSS only for tiny hover/focus states, tokenized fallbacks, native progressive enhancement, and view-transition class styling.
- Use Motion for component and layout animation.
- Use GSAP for orchestration, mixed-surface sequences, and ScrollTrigger narratives.
- Pair GSAP with Lenis when synchronized scroll is part of the concept.
- Use React Three Fiber plus drei for React 3D scenes.
- Use OGL or shader-first pipelines when the surface itself is the product.
- Use shaders when the surface itself is the brand move, not as filler.
- Prefer interruptible transitions for interaction states and keyframes for staged one-shot sequences.
- Animate contextual icon swaps with small opacity, scale, and blur changes instead of hard replacing them.
- Split enter animations into semantic chunks and stagger them lightly.
- Make exit animations subtler than enter animations.
- Treat sound, haptics, and toasts as optional feedback layers for the interaction system, not random garnish.
- Use React
startTransition,useTransition,useDeferredValue, anduseEffectEventto keep animated UIs responsive. - Use React or browser view transitions as progressive enhancement when the support matrix and framework version allow it.
Performance rules:
- Prefer animating
transformandopacity. - Be careful with
filter,backdrop-filter, large blur, and animated shadow. - Narrow
will-changeusage. - Ship a readable poster frame before heavy canvas or video fully hydrates.
- Degrade aggressively on mobile and under
prefers-reduced-motion. - Above-the-fold copy and CTA must remain readable while motion runs.
- Do not animate large blur or shadow changes across big surfaces unless profiling says it is fine.
- Do not hide expensive animation behavior behind giant CSS keyframe stacks.
Parallax rules:
- Keep pointer movement small and clamped.
- Foreground moves more than background.
- Do not put independent drift on every layer.
- Never let text feel detached from its container.
- Keep text and CTA zones on calmer layers than decorative motion.
Scroll rules:
- Every pinned or scrubbed section must explain something.
- Avoid long scroll-jacking sequences.
- Test touch devices before committing to choreography-heavy storytelling.
- Do not drop Lenis into dense docs or dashboards just because it sounds premium.
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.
- 4d ago First seen · 60 lines · 613 tokens per session scan A fa2b01bbb313
frontend-10x-motion is a cursor rule published in the GitHub repository Kevin-Liu-01/Loop (18 stars, last pushed 1mo ago), licensed MIT. It adds 613 tokens to every session, about $0.0031 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 cursor rules, from other repositories
frontend
Demo Shop frontend guidance.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
performance
USE WHEN: Optimizing Core Web Vitals, managing assets, and ensuring high Lighthouse/A11y scores.
handoff
Project handover — write timestamped handoff docs under .handoff/ with HANDOFF.md as symlink to latest. Handles project, submodule, task, and archive handoffs.
motion-design
Motion design rules — context-aware animation principles drawn from Emil Kowalski, Jakub Krehel, and Jhey Tompkins. Covers timing, enter/exit recipes, motion gaps, accessibility, performance, and anti-patterns.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.