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 ShipWithAI/shipwithai-plugins --skill mobile-designgit clone --depth 1 https://github.com/ShipWithAI/shipwithai-pluginsWrote 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/shipwithai/shipwithai-plugins/mobile-design)<a href="https://agentmods.dev/skills/shipwithai/shipwithai-plugins/mobile-design"><img src="https://agentmods.dev/badge/skills/shipwithai/shipwithai-plugins/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/skills/shipwithai/shipwithai-plugins/mobile-design"><img src="https://agentmods.dev/badge/skills/shipwithai/shipwithai-plugins/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.00085 | $0.02214 |
| Opus 5.5 | $0.00034 | $0.00886 |
| Sonnet 5.5 | $0.00017 | $0.00443 |
| Haiku 4.5 | $0.00009 | $0.00221 |
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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile UI design evaluation
This skill is a rubric for an evaluator, not a generator. Given a rendered screen (a screenshot, ideally one per device config), grade it against the criteria below and return a verdict plus specific, element-level fixes.
The ordering is deliberate and matches how mobile agent output actually fails: most defects are structural (clipped, overlapping, off-grid) before they are tasteless. Catch broken layouts first — they are hard fails — then judge polish.
How to use this skill
- When: reviewing a mobile UI screenshot, or after the implementer edits any
@Composableand re-renders. Pair it with the screenshot harness (Roborazzi / emulator capture). Anything a deterministic layout assertion already caught does not need re-judging here; this skill covers what assertions can't see plus all of taste. - Two passes: Tier 1 (structural integrity) → any violation is a blocker. Tier 2 (visual quality) → weighted issues, reported but not auto-failing unless they pile up.
- Output: a verdict (
pass/fail), violations grouped by tier, each naming the element, the config it appears in, and a concrete fix. Never return "looks off" — always say what and where.
Evaluation protocol — render the matrix
Most "broken" only shows under stress. Evaluate each screen across this matrix and grade the worst case, not the happy path:
- Default — reference device (e.g. Pixel-class, ~411dp wide).
- Compact width — ~360dp or narrower (small phones, split screen).
- Large font scale —
fontScale1.5 and 2.0 (accessibility text size). This is where overflow and truncation surface. - Dark mode — both light and dark.
- Long content — longest realistic strings, large numbers, missing images.
- RTL — only if the app localizes to RTL.
A defect in any config is a defect.
Tier 1 — Structural integrity (blockers)
Each item is a hard fail. Fix before evaluating taste. These are the "is it broken?" checks, severity-ranked.
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.
- 1mo ago First seen · 193 lines · 85 tokens per session scan A a7cbeb4ad06a
mobile-design is a skill published in the GitHub repository ShipWithAI/shipwithai-plugins (9 stars, last pushed 2mo ago), licensed MIT. It adds 85 tokens to every session and 2,214 once invoked, about $0.0003 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 skills, from other repositories
rn-asset-hygiene
Use when a React Native project has messy assets — unreferenced/unused image, SVG, or Lottie files, scattered or deeply-relative require() paths, or string-based asset references you want made type-safe. Audits first (read-only), then offers git-safe cleanup. Wraps the rn-typed-assets CLI.
design-system
Creates the Tamagui brand system for an Expo/React Native Power Apps mobile app, including design-system.md, tokens.ts, and an HTML gallery.
ui-mobile
Mobile UI patterns - React Native, iOS/Android, touch targets.
ios-hig-design
Design native iOS interfaces following Apple Human Interface Guidelines. Use when the user mentions "iPhone app", "iPad layout", "SwiftUI", "UIKit", "Dynamic Island", "safe areas", "HIG compliance", "SF Symbols", "haptic feedback", "iOS accessibility", "make my app feel native", or "follow Apple design guidelines".…
liquid-glass-design
Patterns for implementing Apple's Liquid Glass — a dynamic material that blurs content behind it, reflects color and light from surrounding content, and reacts to touch and pointer interactions. Covers SwiftUI, UIKit, and WidgetKit integration.
mobile-design
Generates distinctive, production-grade mobile interfaces for Flutter and React Native. Prioritizes platform-native patterns, adaptive layouts, and fluid motion. Use when building mobile apps, screens, widgets, or when the user requests to style or create visually striking mobile UI.