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.
git clone --depth 1 https://github.com/gokulkrishh/.cursorWrote 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/gokulkrishh/.cursor/motion-react)<a href="https://agentmods.dev/rules/gokulkrishh/.cursor/motion-react"><img src="https://agentmods.dev/badge/rules/gokulkrishh/.cursor/motion-react/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/rules/gokulkrishh/.cursor/motion-react"><img src="https://agentmods.dev/badge/rules/gokulkrishh/.cursor/motion-react.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.00000 | $0.01040 |
| Opus 5.5 | $0.00000 | $0.00416 |
| Sonnet 5.5 | $0.00000 | $0.00208 |
| Haiku 4.5 | $0.00000 | $0.00104 |
Grade A, and why
motion-react 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 1mo 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Motion for React
You're an expert in React, TypeScript, Framer Motion, Motion for React and web animation.
Framer Motion is now called Motion for React. All the knowledge you've gained from Framer Motion is now applicable to Motion for React.
Importing
- Never import from
framer-motion. - Whenever you want to import from
framer-motion, you must import frommotion/react. - When importing the
motioncomponent, import frommotion/reactunless this is a server component, in which case you must importmotionlike this:import * as motion from "motion/react-client". - If the top of the file is marked with
"use client", you must import from"motion/react". - When importing the
animatefunction, if this is a React file then import from"motion/react", otherwise import from"motion".
Performance
- Inside functions that will, or could, run every animation frame:
- Avoid object allocation, prefer mutation where safe.
- Prefer
forloops overforEachormapetc. - Avoid
Object.entries,Object.valuesetc as these create new objects.
- Examples of functions that could run every animation frame include
useTransformandonUpdate. - Outside of these functions, revert to your normal coding style as defined either by your natural behaviour or other rules.
- If animating a
transformliketransform,x,y,scaleetc, then add style the component withwillChange: "transform". If animatingbackgroundColor,clipPath,filter,opacity, also add these values towillChange. Preferably, this style will be added along with the other styles for this component, for instance in an included stylesheet etc. But if no other styles are defined then it can be passed via thestyleprop. - Only ever add these values to
willChange:transformopacityclipPathfilter
- Coerce numbers and strings between each other in as few steps as possible.
Motion Values
- Never use
value.onChange(update), always usevalue.on("change", update)
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.
- 1mo ago First seen · 71 lines · 1,040 tokens per session scan A bb396ff30403
motion-react is a cursor rule published in the GitHub repository gokulkrishh/.cursor (3 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,040 tokens. 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 cursor rules, from other repositories
windsurfrules
Create detailed components with these requirements.
state-management
Use the following stack. Do not introduce or recommend Redux or React Context for shared/global state.
backend
Backend development rules for TT Studio - AI model management backend.
tanstack-start-guide
TanStack Start best practices emphasizing client-first architecture, type safety, and modern React patterns.
new-component
Workflow for creating new React components.
tanstack-react-router_routing
TanStack Router: Routing.