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 60fps-Design/plugin --skill motion-referencegit clone --depth 1 https://github.com/60fps-Design/pluginWrote 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/60fps-design/plugin/motion-reference)<a href="https://agentmods.dev/skills/60fps-design/plugin/motion-reference"><img src="https://agentmods.dev/badge/skills/60fps-design/plugin/motion-reference/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/60fps-design/plugin/motion-reference"><img src="https://agentmods.dev/badge/skills/60fps-design/plugin/motion-reference.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.00092 | $0.00602 |
| Opus 5.5 | $0.00037 | $0.00241 |
| Sonnet 5.5 | $0.00018 | $0.00120 |
| Haiku 4.5 | $0.00009 | $0.00060 |
Grade A, and why
motion-reference 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 9d 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 reference
The 60fps MCP server holds 2,000+ clips of real iOS interactions. Each one has a written motion
breakdown, and many have a compile-checked SwiftUI recreation. Use it instead of inventing timings.
The numbers in this library came off apps that shipped.
Use the tools in this order
60fps_search_shots. Write natural language, not keywords. "Springy bottom sheet for checkout" works. "Sheet" does not. Only setapporfiltersif the user named one.60fps_get_motion_breakdown. This gives you the start state, the transition, the end state, and the timing and easing. Design from this.60fps_get_motion_code. This returns a self-contained SwiftUI file. Show it to the user in full, in a swift code block. It is the deliverable, not a citation.60fps_get_related_shotsif the first pick is close but not right.
Read the results honestly
Search ranks the whole library by closeness, so it always returns something, however far off the
question was. A high total is how many shots were searched, not how many matched. Judge each
result on its own merits, and say so when nothing fits.
When not to use it
The library is iOS only, and it is about motion.
Do not use it for Android, Material, Flutter, React Native or web. Do not use it for icon design, colour palettes, logos or brand work. Do not use it for performance or frame-rate profiling, which shares the name and nothing else. On any of those it will still return iOS clips, and they will be wrong. Answer directly instead.
Using the code
Each file is standalone. Paste it into Xcode and run it.
It carries none of the original app's words, colours, branding or assets, by design. Restyle it to the user's design system. The motion is the part worth keeping.
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.
- 9d ago Changed · +5 lines 4f65b225b9f3
- 1mo ago First seen · 48 lines · 92 tokens per session scan A 63b6af0ed23b
motion-reference is a skill published in the GitHub repository 60fps-Design/plugin (1 stars, last pushed 9d ago), licensed MIT. It adds 92 tokens to every session and 602 once invoked, about $0.0004 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-31.
Other skills, from other repositories
add-component
Add a SwiftUI component from ShipSwift. Use when the user says "add component", "add a view", "add X view", "I need a chart", "add animation", or wants a specific UI element.
figma-a11y-annotations
Rules for generating accessibility annotations on iOS/iPadOS mobile designs in Figma. Enforces a bare-minimum annotation discipline, an iOS vocabulary instead of web ARIA terms, and exact grammar for names, control types, page titles, values, hints, headings, groups, and reading order. Never annotates visible text as…
iOS SwiftUI Accessibility
Enforces WCAG 2.2 accessible coding patterns when writing SwiftUI — labels, traits, Dynamic Type, contrast, touch targets, focus management, orientation, and more. Based on the ios-swiftui-accessibility-techniques project with 41 static analysis rules across 24 WCAG criteria.
liquid-glass
Implement, migrate, review, and diagnose iOS Liquid Glass interfaces in SwiftUI and UIKit. Use for system chrome, custom glass effects, transitions, accessibility, and version-specific issues in native iOS apps.
ttb-skill-native-swiftui-components
Build reusable native SwiftUI UI components using 100% standard SwiftUI primitives with TTBaseUIKit design tokens, localization, chainable modifiers, and project architecture rules. NO TTBaseSUI wrappers. iOS 14+.
apple-design
Complete Apple Human Interface Guidelines (HIG) and Apple Design System standard. Use when designing, building, or auditing UI/UX for iOS, iPadOS, macOS, watchOS, visionOS, or Apple-styled web and mobile applications.