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/KumarSashank/motiscopeWrote 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/kumarsashank/motiscope/motiscope)<a href="https://agentmods.dev/rules/kumarsashank/motiscope/motiscope"><img src="https://agentmods.dev/badge/rules/kumarsashank/motiscope/motiscope/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/kumarsashank/motiscope/motiscope"><img src="https://agentmods.dev/badge/rules/kumarsashank/motiscope/motiscope.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.00011 | $0.00589 |
| Opus 5.5 | $0.00004 | $0.00236 |
| Sonnet 5.5 | $0.00002 | $0.00118 |
| Haiku 4.5 | $0.00001 | $0.00059 |
Grade A, and why
motiscope 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
motiscope — recreate animations from screen recordings
motiscope turns a screen recording of an animation into working web-animation code. It measures the one thing a screenshot cannot show — time — and leaves perception to you.
The division of labor
- The numbers measure the WHEN.
motiscope analyzeemits exact durations, per-segment easing as a realcubic-bezierfitted from the velocity profile, beat boundaries, stagger timing, and loop period. Copy these verbatim; never re-estimate them from frames. - You supply the WHAT. motiscope curates a handful of keyframe PNGs and deliberately does not classify animation types. Look at the frames and name what you actually see — a mask reveal, a path draw, a morph, a 3D flip, a text split, particles, anything.
Commands
motiscope doctor # verify ffmpeg + ffprobe (the only dependencies)
motiscope analyze <video> [--preset balanced|draft|detailed|landing]
motiscope home # reference guides live under $(motiscope home)/references/
analyze writes .motiscope/<slug>/ containing report.md (the measured timing),
motion.json (the raw energy curve), and frames/*.png. Read the report, then look at
every frame, then build the animation. Local video files only — motiscope never
downloads URLs.
Workflows
| Skill | What it does |
|---|---|
motiscope-analyze |
Analyze a screen recording of an animation to characterize its motion — timing, easing, transforms, and sequencing — so it can be recreated as web code. |
motiscope-recreate |
Recreate an analyzed animation as working web code — GSAP (JavaScript), CSS/Web Animations, Framer Motion (React), or Lottie/SVG. |
motiscope-rebuild-site |
Rebuild a whole landing page / multi-section website from a screen recording that scrolls or walks through it. |
motiscope-doctor |
Check and configure motiscope — verify ffmpeg/ffprobe are installed and scaffold the API-key config used for optional (stubbed) asset generation. |
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 · 46 lines · 11 tokens per session scan A 1c0850436c5e
motiscope is a cursor rule published in the GitHub repository KumarSashank/motiscope (125 stars, last pushed 2mo ago), licensed MIT. It adds 11 tokens to every session and 589 once invoked, about $0.0000 per session on Opus 5.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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
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.
as-contract-cast-smell
// ❌ WRONG — bypasses the family ContractSerializer seam const contract = JSON.parse(raw) as Contract; const contract = JSON.parse(raw) as Contract .