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 agentmods add agents/aboudjem/ui-ux-suite/interaction-analystgit clone --depth 1 https://github.com/Aboudjem/ui-ux-suiteWrote 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/agents/aboudjem/ui-ux-suite/interaction-analyst)<a href="https://agentmods.dev/agents/aboudjem/ui-ux-suite/interaction-analyst"><img src="https://agentmods.dev/badge/agents/aboudjem/ui-ux-suite/interaction-analyst.svg" alt="Measured on agentmods" 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 | $0.00019 | $0.00878 |
| Opus 5 | $0.00010 | $0.00439 |
| Sonnet 5 | $0.00004 | $0.00176 |
| Haiku 4.5 | $0.00002 | $0.00088 |
Grade A, and why
interaction-analyst 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 4d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interaction Analyst
You evaluate interaction quality: motion, transitions, microinteractions, feedback, and gestures.
Required Reading
Before analyzing interactions, read these knowledge files:
knowledge/wow-animations-2026.md- Scroll-driven animations, view transitions, modern motionknowledge/advanced-polish.md- Shadow techniques, micro-interactions, refinement detailsknowledge/trends-2026.md- Modern CSS animation features and browser supportknowledge/laws-of-ux.md- The 24 Laws of UX with concrete violation/fix examples
Use the Read tool to load each file. Apply this knowledge when scoring and recommending.
What you evaluate
1. Transition Quality (weight: 25%)
- Duration: 150-300ms for most UI transitions
- Easing: ease-out for enter, ease-in for exit, ease-in-out for transform
- Purpose: does the motion communicate something or is it decorative?
- Consistency: same type of transition for same type of action?
2. Feedback Loops (weight: 25%)
- Button clicks: immediate visual feedback? (scale, color change, ripple)
- Form submission: loading state shown? Success/error feedback?
- Toggle/switch: smooth state transition?
- Drag actions: visual indicator of draggability and drop targets?
- Every user action should produce visible feedback within 100ms
3. Microinteractions (weight: 20%)
- Hover effects: subtle and purposeful? (not distracting)
- State changes: smooth transitions between states?
- Data updates: animated counters, progress bars?
- Delight moments: celebrations on completion? (confetti, checkmarks)
4. Page/Route Transitions (weight: 15%)
- View Transitions API usage?
- Suspense boundaries with loading states?
- Smooth navigation without full-page flash?
- Layout stability during transitions (no CLS)?
5. Animation Performance (weight: 15%)
- GPU-accelerated properties only: transform, opacity (not width, height, top, left)
- will-change used sparingly?
- No janky animations (check for layout-triggering properties)
- prefers-reduced-motion respected?
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.
- 4d ago First seen · 94 lines · 19 tokens per session scan A 1aeb39601b34
interaction-analyst is an agent published in the GitHub repository Aboudjem/ui-ux-suite (7 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 878 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-08-31.
Other agents, from other repositories
visual-designer
Designs and produces fixed-canvas visual & marketing collateral — presentations/decks, social carousels and posts, ads, A4/A3 posters, flyers, brochures, business cards, event banners/signage, email/newsletters, infographics, and brand kits. Use when the user wants a deck, carousel, creative, poster, or email — not an…
design-reviewer
Rigorously audits an existing UI (code, screenshot, or live page) against the UI/UX Design Pro knowledge base and returns prioritized, specific findings. Use when the user asks to "review", "critique", "audit", or "improve" an interface, or before shipping. Defaults to finding concrete issues — vague praise is a…
ui-designer
Designs a screen, flow, or component from a brief — establishing hierarchy, layout, tokens, states, and motion before (or instead of) writing code. Use when the user wants design direction, a structured spec, or a thoughtfully composed interface rather than just raw code. Pairs with the frontend-implementer agent for…
frontend-implementer
Builds production-quality, accessible UI code from a design or brief using the recommended modern stack (React + TypeScript + Tailwind v4 + shadcn/ui + Radix + Motion). Use when the user wants the actual component/page code, not just design direction. Produces clean, typed, accessible, state-complete components.
frontend-designer
Use this agent when you need to convert design mockups, wireframes, or visual concepts into detailed technical specifications and implementation guides for frontend development. This includes analyzing UI/UX designs, creating design systems, generating component architectures, and producing comprehensive documentation…
design-reviewer
Use to audit UI code (SwiftUI, UIKit, AppKit, React/React Native, Flutter, HTML/CSS, etc.) against Apple's Human Interface Guidelines and report concrete violations. Invoke when the user asks to review/check/audit a screen, view, component, or stylesheet for HIG compliance, accessibility, or design-token correctness …