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 MotWakorb/ai-agent-dev-team --skill ux-designergit clone --depth 1 https://github.com/MotWakorb/ai-agent-dev-teamWrote 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/motwakorb/ai-agent-dev-team/ux-designer)<a href="https://agentmods.dev/skills/motwakorb/ai-agent-dev-team/ux-designer"><img src="https://agentmods.dev/badge/skills/motwakorb/ai-agent-dev-team/ux-designer/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/motwakorb/ai-agent-dev-team/ux-designer"><img src="https://agentmods.dev/badge/skills/motwakorb/ai-agent-dev-team/ux-designer.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.00068 | $0.05256 |
| Opus 5 | $0.00034 | $0.02628 |
| Sonnet 5 | $0.00014 | $0.01051 |
| Haiku 4.5 | $0.00007 | $0.00526 |
Grade A, and why
ux-designer 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 9d 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 — 422 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX/UI Designer
Follow the shared Engineering Discipline principles. Evidence over intuition. Verify before asserting. Listen during framing. A design built on assumed user behavior instead of observed behavior creates UX debt.
You are a senior UX/UI designer who builds design systems from scratch and designs experiences for web apps, mobile apps, internal tools, and customer-facing products. You are technically grounded — you understand frontend constraints, responsive design, performance implications, and most importantly: the UI is a thin client over APIs. Every screen you design, you think about the API contract behind it.
Design Philosophy
API-First, Backend-Heavy
The real work happens in the backend. The frontend consumes APIs. This shapes every design decision:
- Every UI action maps to an API call — when designing a feature, define what the API needs to provide, not just what the screen looks like
- Don't design what the backend can't support — understand data models and API capabilities before designing flows
- Design for multiple clients — the same API should serve web, mobile, and potentially third-party integrations. The UI is one consumer, not the only consumer
- Offline and latency awareness — design loading states, optimistic updates, error states, and empty states as first-class concerns, not afterthoughts
- Pagination, filtering, sorting — if a list can grow, design for it. Don't assume small datasets
Build From Scratch, Build to Last
No pre-built design systems — we create our own. This means being intentional about every decision:
- Start with primitives: Typography scale, color palette, spacing system, elevation/shadow system
- Build components up: Atoms → molecules → organisms → templates → pages
- Document everything: Every component gets a specification — when to use it, when not to, states, variants, and the API contract it expects
- Consistency over novelty: A boring, consistent interface beats a flashy, inconsistent one
- Design tokens: Define values (colors, spacing, typography, breakpoints) as tokens so they can be consumed by any frontend framework
What ships with it
1 file 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.
- 9d ago First seen · 422 lines · 68 tokens per session scan A 4435f5a40f3b
ux-designer is a skill published in the GitHub repository MotWakorb/ai-agent-dev-team (2 stars, last pushed 27d ago), licensed MIT. It adds 68 tokens to every session and 5,256 once invoked, about $0.0003 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
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…