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 find-animation-opportunitiesgit 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/find-animation-opportunities)<a href="https://agentmods.dev/skills/60fps-design/plugin/find-animation-opportunities"><img src="https://agentmods.dev/badge/skills/60fps-design/plugin/find-animation-opportunities/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/find-animation-opportunities"><img src="https://agentmods.dev/badge/skills/60fps-design/plugin/find-animation-opportunities.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.00095 | $0.01923 |
| Opus 5.5 | $0.00038 | $0.00769 |
| Sonnet 5.5 | $0.00019 | $0.00385 |
| Haiku 4.5 | $0.00010 | $0.00192 |
Grade A, and why
find-animation-opportunities 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 3d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find animation opportunities
Most apps do not need more animation. They need it in a few places that carry meaning, and nowhere
else. Your job is to find those places in the user's code, say plainly what should stay still or
be toned down, and back each recommendation with a real interaction from the 60fps library.
Motion here means visual motion AND haptics: both are part of how an app feels.
Do not change any code in this pass. The deliverable is a short report.
1. Take stock of the motion that is already there
Before looking for gaps, search the code for what the app already does: withAnimation,
.animation(, .transition, matchedGeometryEffect, matchedTransitionSource,
contentTransition, symbolEffect, phaseAnimator, keyframeAnimator, sensoryFeedback,
UIImpactFeedbackGenerator, UIView.animate, and any reduce motion checks. On a big app this is a long list: group it by file and read the
haptics and transitions first, they are where most problems hide.
Then say which kind of app this is:
- Little motion. Most of the value is new opportunities.
- Already rich. Say so at the top. The value is now the few gaps, motion that is broken, and motion that is overdone. Do not recommend what the app already does.
Note the app's tone from its existing motion and design: calm and restrained, or bold and playful. Every recommendation must match it.
2. Decide the scope
If the user named a screen or a feature, look only there. Otherwise cover the screens a user sees
most: the root view and whatever it presents (tabs, overlays, sheets, the flows they open), plus
widgets, Live Activities and other extensions, which are easy to forget. Widgets cannot run their
own animations: the only motion there is a content transition when the timeline changes (rolling
digits, a crossfade), so never suggest more. Read the state that drives
a view too (@Observable models, view models, the code that assigns new data), not only the view:
the fix is often where the state changes.
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.
- 3d ago First seen · 148 lines · 95 tokens per session scan A 35334e5b43d5
find-animation-opportunities is a skill published in the GitHub repository 60fps-Design/plugin (1 stars, last pushed 3d ago), licensed MIT. It adds 95 tokens to every session and 1,923 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-10-13.
Other skills, from other repositories
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.
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.
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.