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/taotao135791-bit/gsap-transform/motion-stategit clone --depth 1 https://github.com/taotao135791-bit/gsap-transformWrote 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/taotao135791-bit/gsap-transform/motion-state)<a href="https://agentmods.dev/rules/taotao135791-bit/gsap-transform/motion-state"><img src="https://agentmods.dev/badge/rules/taotao135791-bit/gsap-transform/motion-state.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.00093 | $0.00388 |
| Opus 5 | $0.00046 | $0.00194 |
| Sonnet 5 | $0.00019 | $0.00078 |
| Haiku 4.5 | $0.00009 | $0.00039 |
Grade A, and why
motion-state 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 5d 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-state
Every /studio project carries a state.json that is the source of truth. scene.js is generated from it (node scripts/state-to-scene.mjs).
Schema lives in skills/motion-state/schema.json (JSON Schema draft-07). Runtime lives in skills/motion-state/runtime.mjs:
validate(state); // throws on schema or anti-slop violation
at(state, t); // → beats overlapping t
add(state, beat); // returns new state with beat appended
remove(state, beatId); // returns new state with beat removed
update(state, id, patch) // returns new state with patched beat
summary(state); // → { beatCount, layerCount, duration, primitives }
Browser surface: window.__studio.state mirrors the same API. Mutations trigger rebuild() so GSDevTools reflects the change live.
Anti-slop Group S (enforced at every mutation):
- S1:
atin[0, duration] - S2: layer overlap without
allowOverlap: true - S4: missing
schemaVersion - S5:
beats.length > 200(LLM runaway guard)
For the full contract, schema, and limitations: see skills/motion-state/SKILL.md.
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.
- 5d ago First seen · 30 lines · 93 tokens per session scan A 332ffe7fad56
motion-state is a cursor rule published in the GitHub repository taotao135791-bit/gsap-transform (2 stars, last pushed 2mo ago), licensed MIT. It adds 93 tokens to every session and 388 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-31.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.