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 skills/phuonghx/aim-cli/mobile-designnpx skills add phuonghx/aim-cli --skill mobile-designgit clone --depth 1 https://github.com/phuonghx/aim-cliWhat 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.00070 | $0.02233 |
| Opus 5 | $0.00035 | $0.01117 |
| Sonnet 5 | $0.00014 | $0.00447 |
| Haiku 4.5 | $0.00007 | $0.00223 |
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 yesterday.
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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile Design System
Build for thumbs, not cursors. Respect the battery, respect the platform, survive offline. A phone is its own medium, not a shrunken desktop. Reason about the constraints first, then confirm the platform before you commit to anything.
Validation script
There is one helper script. Run it; you do not need to read its source.
| Script | What it does | How to run |
|---|---|---|
scripts/mobile_audit.py |
Scans RN/Flutter source for touch, performance, and platform issues | python scripts/mobile_audit.py <project_path> |
Read the reference files first
Do not begin coding until you have opened the references that apply to the work in front of you. Each one goes deeper than the summaries below.
Read on every mobile task
| File | Focus |
|---|---|
| mobile-design-thinking.md | Start here. Breaks the habit of reaching for memorized defaults |
| touch-psychology.md | Fitts' Law, reach zones, gestures, haptics |
| mobile-performance.md | 60fps lists and animations, memory, RN + Flutter |
| mobile-backend.md | Push, offline sync, mobile-shaped APIs |
| mobile-testing.md | Test pyramid, E2E on devices, platform splits |
| mobile-debugging.md | JS vs native crashes, DevTools, Logcat |
| mobile-navigation.md | Tabs, stacks, drawers, deep links |
| mobile-typography.md | System fonts, dynamic text, readability |
| mobile-color-system.md | OLED, dark mode, sunlight, battery |
| decision-trees.md | Choosing framework, state, storage |
The thinking guide comes before everything else. It is what keeps the output tailored to the project instead of generic.
Read the one that matches your target
| Target | File | Covers |
|---|---|---|
| iPhone / iPad | platform-ios.md | HIG, SF Pro, SwiftUI conventions |
| Android | platform-android.md | Material 3, Roboto, Compose conventions |
| Cross-platform | both of the above | Where the two diverge |
What ships with it
13 files 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.
- decision-trees.md 9.3 KB
- mobile-backend.md 11 KB
- mobile-color-system.md 7.2 KB
- mobile-debugging.md 4.1 KB
- mobile-design-thinking.md 8.8 KB
- mobile-navigation.md 8.4 KB
- mobile-performance.md 13 KB
- mobile-testing.md 7.9 KB
- mobile-typography.md 7.9 KB
- platform-android.md 11 KB
- platform-ios.md 10 KB
- scripts/mobile_audit.py 35 KB runs code
- touch-psychology.md 12 KB
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.
- yesterday First seen · 219 lines · 70 tokens per session scan A b4dcd26682c3
mobile-design is a skill published in the GitHub repository phuonghx/aim-cli (1 stars, last pushed 2mo ago), licensed MIT. It adds 70 tokens to every session and 2,233 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 skills, from other repositories
hs-release
Cut a core Hindsight release (vX.Y.Z) and open the changelog + blog PR. Use when asked to cut/start a release, bump the version, or publish a new Hindsight version.
hindsight-local
Store user preferences, learnings from tasks, and procedure outcomes. Use to remember what works and recall context before new tasks. (user).
research-repository
Build a repository that makes findings findable, reusable, and cumulative across teams. Use when the same research keeps getting redone. For synthesising one study, use affinity-diagram.
design-negotiation
Advocate for design quality, scope, and timeline with partners and leadership using evidence and shared goals. Use in the conversation itself. For the commercial vocabulary behind it, use business-design (ux-strategy).
user-persona
Build research-grounded personas with goals, frustrations, and behavioural patterns. Use when decisions need a consistent user reference. For one session's emotional snapshot use empathy-map; for motivation framing use jobs-to-be-done.
version-control-strategy
Define version control for design files, components, and libraries — branching, naming, and release. Use when file history is chaotic. For design system contribution rules, use design-system-governance (design-systems).