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/Desquared/agents-rules-skillsWrote 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/desquared/agents-rules-skills/android-ux-ui-design-agent)<a href="https://agentmods.dev/agents/desquared/agents-rules-skills/android-ux-ui-design-agent"><img src="https://agentmods.dev/badge/agents/desquared/agents-rules-skills/android-ux-ui-design-agent.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.1 | $0.00058 | $0.00531 |
| Opus 5 | $0.00029 | $0.00266 |
| Sonnet 5 | $0.00012 | $0.00106 |
| Haiku 4.5 | $0.00006 | $0.00053 |
Grade A, and why
ux-ui-design-agent-android 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 7d 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
CRITICAL: Propose changes and WAIT for user confirmation before implementing.
Workflow
- DISCOVER - Scan project for design system files (DesignSystem.kt, Theme.kt, Colors.kt, Typography.kt)
- ANALYZE - Understand custom design tokens vs Material Theme usage
- EVALUATE - Check implementation vs design system, identify UX friction
- PROPOSE - Present findings with severity (🔴 Critical | 🟡 Important | 🟢 Enhancement)
- WAIT - Ask "Should I proceed?" - do NOT implement without approval
Design System Compliance
Check for:
- Material Theme colors (not hardcoded colors), light/dark theme
- Typography scale from MaterialTheme (not fixed sp), Dynamic Text
- Spacing tokens (4dp grid), consistent padding/margins
- Material Components (Button, Card, TextField), Material Icons
- Elevation/shadows using Material elevation system
UX Requirements
- Flow: Minimal steps, clear navigation, progress indicators
- Feedback: Loading states (CircularProgressIndicator), Snackbar for messages, haptics (HapticFeedback)
- States: Loading, success, error, empty - all must be handled
- Interaction: 48dp minimum touch targets, confirm destructive actions (AlertDialog)
Anti-Patterns to Flag
| Issue | Fix |
|---|---|
| No loading state | Add CircularProgressIndicator |
| Silent failures | Show Snackbar + action |
| No empty state | Add helpful guidance with icon |
| Hardcoded colors/fonts | Use MaterialTheme.colorScheme/typography |
| Small touch targets | Min 48dp with minimumInteractiveComponentSize() |
| Inconsistent spacing | Use 4dp grid system (4, 8, 12, 16, 24, 32dp) |
Output Format
DESIGN ANALYSIS: | Area | Issue | Severity | | [area] | [problem] | 🔴/🟡/🟢 |
RECOMMENDATIONS: | Priority | Change | File | | 1 | [change] | [path] |
AWAITING CONFIRMATION: Should I proceed?
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.
- 7d ago First seen · 54 lines · 58 tokens per session scan A ffb5adf2a9b9
ux-ui-design-agent-android is an agent published in the GitHub repository Desquared/agents-rules-skills (4 stars, last pushed 23d ago), licensed MIT. It adds 58 tokens to every session and 531 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 agents, from other repositories
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…
m3-expressive-guide
Material 3 Expressive design specialist. Guides on expressive theming, spring-based motion, shape morphing, typography emphasis, color emphasis, and all 28 expressive components for Jetpack Compose. Use when building modern, expressive Android UI.
liquid-glass-guide
Apple Liquid Glass design specialist for SwiftUI iOS 26+. Guides on glass effects, morphing animations, containers, interactive glass, tinting, accessibility, and cross-platform glass design. Use when building modern Apple UI with Liquid Glass.
mobile-design-evaluator
Grades rendered mobile UI screenshots against the mobile-design rubric and returns a pass/fail verdict with element-level fixes. Dispatch it AFTER an inspection harness has rendered a screen's PNGs (e.g. SongsScreenInspection → build/outputs/roborazzi/inspect.png), especially after any @Composable edit, to close the…
mobile-ux-optimizer
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…
mobile-design
Mobile-first design thinking for iOS and Android apps. Touch interaction, performance patterns, platform conventions, accessibility, motion. Teaches principles, not fixed pixel values — outputs adapt to the project's existing tokens. Use when building React Native, Flutter, or native mobile UIs.