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 Lrinvl1203/world-class-web-design-os --skill interaction-designgit clone --depth 1 https://github.com/Lrinvl1203/world-class-web-design-osWrote 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/lrinvl1203/world-class-web-design-os/interaction-design)<a href="https://agentmods.dev/skills/lrinvl1203/world-class-web-design-os/interaction-design"><img src="https://agentmods.dev/badge/skills/lrinvl1203/world-class-web-design-os/interaction-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/skills/lrinvl1203/world-class-web-design-os/interaction-design"><img src="https://agentmods.dev/badge/skills/lrinvl1203/world-class-web-design-os/interaction-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.00041 | $0.00301 |
| Opus 5 | $0.00020 | $0.00151 |
| Sonnet 5 | $0.00008 | $0.00060 |
| Haiku 4.5 | $0.00004 | $0.00030 |
Grade A, and why
interaction-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 10d 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
Interaction Design
Start with state, not animation
For every interactive element define:
- trigger/input;
- state before;
- state after;
- feedback latency;
- reversal/cancel path;
- keyboard/touch alternative;
- loading/error/empty behavior if applicable.
Motion-purpose taxonomy
Animation is justified when it improves at least one:
- feedback;
- orientation;
- continuity;
- hierarchy/attention;
- storytelling;
- brand personality.
If none apply, remove it.
Motion budget
Per viewport, prefer:
- at most one dominant narrative motion moment;
- a small number of supporting transitions;
- micro-feedback where interaction occurs.
Do not animate every section entrance. Repetition destroys salience.
Signature interaction
Design one interaction that expresses the brand or product concept. Make it optional to task completion and give it a reduced-motion equivalent.
Accessibility
Never make hover the only way to discover essential content. Drag-only functionality requires a non-drag single-pointer alternative where required by the accessibility baseline.
For product flows, read references/product-edge-cases.md before release and cover the states that apply; a polished happy path is not a complete interaction model.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 51 lines · 41 tokens per session scan A 530775046ca5
interaction-design is a skill published in the GitHub repository Lrinvl1203/world-class-web-design-os (8 stars, last pushed 14d ago), licensed MIT. It adds 41 tokens to every session and 301 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
data-display-and-selection
Complex data deserves multiple view modes — grid, list, table — chosen by the user based on their task. Row and item selection should use large hit areas (the whole row or card, not just a checkbox). Selected state is communicated through a subtle background colour shift. Mass actions appear when items are selected.…
information-architecture
In large applications, information architecture determines whether users can find, understand, and act on data. Naming matters. The UI should mirror the data model and signal how data can be transformed. Dangerous or irreversible changes always require a confirm dialog. Use when designing navigation, naming entities…
brand-visual-language
A brand's visual tone — playful or serious, rounded or angular — should be consistent across all UI elements. Shape language in typography, border-radius, and iconography communicates personality before a single word is read. Use when establishing a design system, choosing icon libraries, setting border-radius tokens…
generate-ui-from-brand
Pipeline skill — turns a URL or DESIGN.md into a concrete UI structure with decisions already made. Extracts live design tokens, normalizes them into a semantic system, applies UX principles, and outputs an actionable UI spec. Use when building UI for an existing brand from scratch, auditing a design system, or…
loading-states-and-perceived-performance
Manage user expectations during wait times with appropriate loading states — from simple spinners to complex skeleton screens and staggered animations. Perceived performance is often more important than actual load time. Use when designing data-heavy components, handling API calls, building hero sections, or improving…
micro-interactions
Micro-interactions are small, purposeful animations and responses that reward the user and make the interface feel alive — an animated icon, a satisfying toggle, a subtle reveal. Borrowed from the natural world, they add delight without distraction. Use when designing interactive components, success states, toggles…