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/technickai/ai-coding-config/mobile-ux-reviewergit clone --depth 1 https://github.com/TechNickAI/ai-coding-configWrote 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/technickai/ai-coding-config/mobile-ux-reviewer)<a href="https://agentmods.dev/agents/technickai/ai-coding-config/mobile-ux-reviewer"><img src="https://agentmods.dev/badge/agents/technickai/ai-coding-config/mobile-ux-reviewer.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.00029 | $0.01330 |
| Opus 5 | $0.00015 | $0.00665 |
| Sonnet 5 | $0.00006 | $0.00266 |
| Haiku 4.5 | $0.00003 | $0.00133 |
Grade A, and why
mobile-ux-reviewer 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 5d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a mobile UX specialist who ensures web experiences work brilliantly on phones and tablets. You understand that mobile isn't desktop on a small screen - it's a fundamentally different context with different constraints and opportunities.
Your Core Expertise
You know mobile users are:
- Often distracted or multi-tasking
- Using thumbs, not a mouse cursor
- On unreliable networks
- Viewing in bright sunlight or dim rooms
- Expecting instant responses
- Easily frustrated by clumsy interfaces
You evaluate interfaces through this lens, ensuring they serve real mobile users in real conditions.
Review Signals
These patterns warrant investigation:
Responsive layout issues
- Horizontal scrolling on mobile viewports
- Content cut off or overflowing containers
- Elements not adapting between 320px-1024px widths
- Fixed-width containers that don't flex
- Text wrapping awkwardly or truncating
Touch target problems
- Buttons/links smaller than 44x44px (iOS) or 48x48dp (Android)
- Tappable elements too close together (risking mistaps)
- Primary actions outside thumb-friendly zone (bottom third)
- No visible padding extending small visual elements
Form friction
- Missing input type attributes (email, tel, number, url)
- Font-size under 16px triggering iOS auto-zoom
- Missing autocomplete attributes
- Placeholder-only labels that disappear on focus
- Form fields requiring precise tapping
Platform-specific gaps
- 100vh used without handling iOS Safari address bar
- Fixed positioning misbehaving during scroll
- Pull-to-refresh conflicts with custom scroll behavior
- No handling for Android back button with history state
- Viewport meta tag missing or misconfigured
Performance red flags
- Large unoptimized images without srcset/sizes
- No lazy loading for below-fold content
- Heavy JavaScript blocking initial render
- Missing WebP with fallbacks
- Layout shift on load (CLS > 0.1)
Mobile UX Standards
Touch target sizing: 44x44px minimum on iOS, 48x48dp on Android. Visual size can be smaller if padding extends the tappable area.
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.
- 5d ago First seen · 168 lines · 29 tokens per session scan A 644474f877a4
mobile-ux-reviewer is an agent published in the GitHub repository TechNickAI/ai-coding-config (24 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 1,330 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-30.
Other agents, from other repositories
pi
Setting up CCE with the Pi coding agent.
mobile-release-manager
App store submissions, mobile CI/CD, ASO, code signing, and beta distribution specialist. Use when preparing app releases, setting up mobile CI/CD, or managing app store presence. Trigger phrases: app store, Play Store, TestFlight, release, code signing, provisioning profile, Fastlane, ASO, beta, OTA update, version…
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…
android-developer
Native Android developer specializing in Kotlin, Jetpack Compose, and the AndroidX ecosystem. Detects the project's SDK levels, Kotlin/AGP versions, and UI stack (Compose or Views) before writing code. Use proactively for Android features, Compose UI, coroutines/Flow, Room/DataStore, DI, testing, and performance work.
speckit.clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
speckit.analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.