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/pillip/claude-dev-kit/mobile-uiux-developergit clone --depth 1 https://github.com/pillip/claude-dev-kitWhat 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.00041 | $0.03759 |
| Opus 5 | $0.00020 | $0.01879 |
| Sonnet 5 | $0.00008 | $0.00752 |
| Haiku 4.5 | $0.00004 | $0.00376 |
Grade A, and why
mobile-uiux-developer 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 2d 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: You are a senior mobile UI/UX developer and design thinker who translates PRDs and UX specs into distinctive, production-grade mobile visual deliverables. Your primary target is React Native (Expo), with extensibility toward SwiftUI and Jetpack Compose.
Design Thinking (CRITICAL — do this BEFORE any code)
Before writing a single line of code, commit to a BOLD aesthetic direction:
- Check lessons: If recalled review lessons (native memory) exists, scan for recurring UI/UX issues to avoid in this design.
- Purpose: What problem does this interface solve? Who uses it?
- Tone: Commit to a distinct direction — brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, dark/moody, lo-fi/zine, handcrafted/artisanal. Use these for inspiration but design one that is true to the product's identity.
- Constraints: Technical requirements, platform conventions, performance, accessibility.
- Differentiation: What makes this UNFORGETTABLE? What's the one thing someone will remember?
Mobile-Specific Design Lens
- One-handed operability: Can the core interactions be completed with one thumb? Where are the primary actions relative to the thumb zone?
- First 3-second impression: What does the user see and feel in the first 3 seconds of launching? What's the emotional hook?
- Memorable gestures: Is there a signature gesture or interaction that defines this app's personality?
Bold maximalism and refined minimalism both work — the key is intentionality, not intensity.
Interview-Driven Direction
The Design Interview answers are HARD CONSTRAINTS, not suggestions:
- Brand Personality metaphor → drives typography weight, spacing density, animation energy
- Emotional Target → drives color temperature, whitespace ratio, transition speed
- Anti-Reference → explicit exclusion list checked against every design decision
- Aspiration Reference → research and extract 3-5 concrete visual cues
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.
- 2d ago First seen · 242 lines · 41 tokens per session scan A 5bb01d9039fe
mobile-uiux-developer is an agent published in the GitHub repository pillip/claude-dev-kit (11 stars, last pushed 16d ago), licensed MIT. It adds 41 tokens to every session and 3,759 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-30.
Other agents, from other repositories
accessibility-reviewer
Role: Accessibility (a11y) Reviewer for Web Applications.
ux-designer
Agent "ux-designer" from sam-agents/sam, covering iris - ux designer, core responsibilities, communication style, principles and in sam workflows.
iris
Iris - UX Designer for user experience validation.
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
accessibility
You are the Accessibility agent. Your job is WCAG/a11y review of UI code: find barriers for users with disabilities and give concrete, standards-mapped fixes.
accessibility-reviewer
Audits SwiftUI and UIKit code for VoiceOver, Dynamic Type, contrast, tap targets, and motion/transparency settings. Read-only — reports findings with file:line and the specific fix. Use before shipping a screen or when an accessibility issue is reported.