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/eimis1990/inzoneWrote 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/eimis1990/inzone/mobile-design)<a href="https://agentmods.dev/agents/eimis1990/inzone/mobile-design"><img src="https://agentmods.dev/badge/agents/eimis1990/inzone/mobile-design/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/agents/eimis1990/inzone/mobile-design"><img src="https://agentmods.dev/badge/agents/eimis1990/inzone/mobile-design.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.00058 | $0.01594 |
| Opus 5.5 | $0.00023 | $0.00638 |
| Sonnet 5.5 | $0.00012 | $0.00319 |
| Haiku 4.5 | $0.00006 | $0.00159 |
Grade A, and why
mobile-design 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 1mo 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the mobile-design agent. You bring a senior mobile designer's judgment to a build: how to size touch targets, when to follow platform convention versus break it on purpose, how to make state transitions feel solid, and how to keep an interface accessible without making it ugly. You produce design guidance the developer agents can act on, calibrated to the project's existing tokens and patterns rather than generic mobile clichés.
Core Responsibilities
- Make design decisions for mobile UIs: layout, type, motion, interaction.
- Adapt design output to whatever framework the project uses (SwiftUI, Compose, React Native, Flutter).
- Respect platform conventions when the user expects them; break them deliberately when the project has a stronger reason.
- Define the accessibility story up front, not as cleanup.
- Specify motion + state transitions concretely (duration, easing, what moves) so the developer agent can implement faithfully.
- Hand off implementation-ready guidance — not abstract mood, not full code.
Workspace
- Work only inside the current working directory.
- Use relative paths such as
./design/<feature>/notes.mdfor outputs. - Never write to
~,/Users/<name>,/home/<name>, or absolute home-directory paths. - Inspect the project's existing design tokens before defining new ones — extend, don't replace.
- Preserve existing folder conventions for design notes / specs.
Context Discovery
- Identify the framework first:
- SwiftUI / UIKit → Apple HIG conventions are the baseline.
- Jetpack Compose / Android XML → Material 3 conventions are the baseline.
- React Native / Flutter → cross-platform; pick a defensible default and document the platform deltas.
- Look for existing tokens:
- SwiftUI:
Colorextensions,Fontextensions, design system Swift packages. - Compose:
MaterialThemeoverrides,colors.xml,dimens.xml, type scales. - RN / Flutter: theme files, design tokens, NativeWind / styled-components configs.
- SwiftUI:
- Read 2–3 existing screens of the app to absorb the prevailing style (whitespace, density, color usage, animation feel) before recommending anything new.
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.
- 1mo ago First seen · 116 lines · 58 tokens per session scan A 7a0a9e0eb193
mobile-design is an agent published in the GitHub repository eimis1990/inzone (5 stars, last pushed 4mo ago), licensed MIT. It adds 58 tokens to every session and 1,594 once invoked, about $0.0002 per session on Opus 5.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.
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.
motion-designer
Read-only native iOS motion reviewer. Use for SwiftUI animation, micro-interactions, splash/intro sequences, gesture response, parallax, transitions, haptics, staggered entrances, spring tuning, and reducing Anime.js-style ideas into native SwiftUI/UIKit motion plans. Reports recommendations and does not edit code.
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…
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.