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/Oriolshhh/runware-image-mcpWrote 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/oriolshhh/runware-image-mcp/motion-design)<a href="https://agentmods.dev/rules/oriolshhh/runware-image-mcp/motion-design"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/motion-design/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/oriolshhh/runware-image-mcp/motion-design"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/motion-design.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.00015 | $0.00455 |
| Opus 5 | $0.00008 | $0.00228 |
| Sonnet 5 | $0.00003 | $0.00091 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
motion-design 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.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: motion-design
Motion Design
Purpose
Use motion to explain state and space without delaying interaction, causing discomfort, or creating performance regressions.
When to use it
- When adding or changing animation, transitions, drag behavior, or micro-interactions.
Instructions
- State the purpose: feedback, spatial continuity, state explanation, or removal of a jarring transition. Delete motion without a defensible purpose.
- Consider frequency. Remove motion from keyboard and highly repeated actions; keep frequent feedback nearly immediate.
- Match origin and direction to the trigger and interaction. Ensure exit behavior corresponds to entry and interruptions reverse or retarget smoothly.
- Prefer transform/opacity and existing platform primitives. Avoid animating layout properties or adding a motion library without approval.
- Keep timings short enough to feel responsive; tune from rendered behavior, not copied constants.
- Implement
prefers-reduced-motionand appropriate pointer/hover guards. - Test rapid retriggering, cancellation, low-power/load conditions, touch, and the reduced-motion path in a real browser.
Output format
A motion contract and evidence: purpose, frequency, trigger/origin, properties, timing/easing rationale, interruption, reduced motion, and observed performance.
Anti-patterns
- Animation because a page feels empty.
- Long entrances before users can act, motion on keyboard commands, or decorative bounce everywhere.
transition: all, layout-property animation, or a motion dependency for one effect.
Verification checklist
- Every effect has purpose and remains responsive under repetition and interruption.
- Reduced-motion, touch/pointer behavior, and performance were actually exercised.
Apply
context-discoverybefore broad scanning: use a supplied context capsule first; otherwise check context frontmatter freshness, read.agent/context/routing.md, load only relevant summaries, and verify critical claims against source.
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 · 49 lines · 15 tokens per session scan A a6f2118193e8
motion-design is a cursor rule published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 455 once invoked, about $0.0001 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-09-03.
Other cursor rules, from other repositories
external-scale
Source: docs/agents/external-scale.md Regenerate: npm run agents:sync -w packages/openbridge-webcomponents -->.
codex-premium-website-skills
Apply Codex Skills standards to frontend, website, motion, accessibility, QA, agent reasoning, and handoff work.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
ui-motion-workflow
Orchestrate motion-aware UI work by sequencing direction, provider choice, implementation, and browser validation.
mobile-first-ui
Mobile-first UI for settings, dialogs, and lists — smaller type, stacked layouts, nested add dialogs.
interface-kit
UI implementation craft — accessibility, performance, typography, motion, anti-generic aesthetics. Read when building/polishing UI after direction is chosen. Does NOT replace redesign multi-model competition.