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 OneWave-AI/open-agent-stack --skill motion-systemgit clone --depth 1 https://github.com/OneWave-AI/open-agent-stackWrote 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/onewave-ai/open-agent-stack/motion-system)<a href="https://agentmods.dev/skills/onewave-ai/open-agent-stack/motion-system"><img src="https://agentmods.dev/badge/skills/onewave-ai/open-agent-stack/motion-system/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/onewave-ai/open-agent-stack/motion-system"><img src="https://agentmods.dev/badge/skills/onewave-ai/open-agent-stack/motion-system.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.00058 | $0.00747 |
| Opus 5.5 | $0.00023 | $0.00299 |
| Sonnet 5.5 | $0.00012 | $0.00149 |
| Haiku 4.5 | $0.00006 | $0.00075 |
Grade A, and why
motion-system 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 — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Motion System
Scattered motion is the loudest AI tell there is. Every element gets its own hover transition, every duration is a different number, half the page animates on scroll and the other half does not. The fix is not less motion -- it is fewer decisions, reused everywhere.
Do this before writing any animation code. It takes ten minutes and every later animation becomes a lookup instead of a judgment call.
Workflow
- Pick the temperature. One choice that governs everything after: is this app calm (slower, softer easing, motion recedes -- dashboards, tools, finance), crisp (fast, tight, near-instant feedback -- productivity, developer tools), or expressive (larger movement, overshoot, motion is part of the brand -- marketing, portfolio, launch pages). Write the choice down. Mixing temperatures is what makes an app feel like three people built it.
- Define the tokens. Three durations and three easings, no more. Put them where the rest of the design tokens live -- CSS custom properties or the Tailwind theme -- so no component ever writes a raw
300msagain. Defaults per temperature are inreferences/motion-tokens.md; adjust, do not expand. - Name the moves. A short vocabulary the whole app reuses:
- enter -- how new content arrives (one treatment, applied consistently: usually a small rise plus fade, 8-16px, never more)
- exit -- how it leaves (faster than enter; nobody wants to wait for a goodbye)
- emphasis -- how something says "look here" (scale or color shift, never both plus a rotate)
- feedback -- press, hover, focus (fastest tier, under 150ms; this one must feel instant)
- transition -- moving between views or states
- Set the reduced-motion policy now. Decide per move what happens under
prefers-reduced-motion: reduce-- usually: opacity survives, movement and scale do not, scrub-driven scroll effects become static. Write it as one global rule, not a per-component afterthought. - Build one reference component. Implement the moves once on a real component and use it as the pattern for everything after. Then delete any existing animation that does not draw from the system.
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 · 33 lines · 58 tokens per session scan A e0c21a33d37b
motion-system is a skill published in the GitHub repository OneWave-AI/open-agent-stack (5 stars, last pushed 2mo ago), licensed MIT. It adds 58 tokens to every session and 747 once invoked, about $0.0002 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
claude-design
Design one-off HTML artifacts (landing, deck, prototype).
sketch
Throwaway HTML mockups: 2-3 design variants to compare.
scrollcraft
Premium scroll-driven landing pages; scroll = timeline.
impeccable
Frontend design guidance, upstream-maintained (impeccable).
auteur
Design and build cinematic, award-level web pages.
taste
Mandatory preflight for web frontend visual design. If available, call readskill for bundled:taste before the first frontend create or edit tool call whenever creating or visually styling a human-viewed web page, component, app, dashboard, or interactive report. Do not load it for non-visual frontend logic or…