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-gamesnpx skills add phuonghx/aim-cli --skill mobile-gamesgit 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.00075 | $0.00690 |
| Opus 5 | $0.00037 | $0.00345 |
| Sonnet 5 | $0.00015 | $0.00138 |
| Haiku 4.5 | $0.00007 | $0.00069 |
Grade A, and why
mobile-games 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Building Games for Mobile
Phones reward games designed for their realities: a finger instead of a gamepad, a battery that drains, a chassis that overheats, and a player who gets interrupted.
What the Platform Forces on You
Each hardware and usage limit has a design response.
| Reality | Design response |
|---|---|
| Input is a fingertip | Use generous hit areas and gestures |
| Power is finite | Keep CPU and GPU work modest |
| The device heats up | Scale back as temperature climbs |
| Screens vary widely | Lay out UI responsively |
| Calls and alerts intrude | Pause cleanly when backgrounded |
Designing for Touch
A touchscreen is a different input device from a controller, not a worse one. Design for its strengths.
| Touch | Controller |
|---|---|
| Coarse pointing | Pixel-accurate |
| Fingers cover the screen | Nothing blocks the view |
| Handful of usable zones | Many discrete buttons |
| Natural gestures | Sticks and triggers |
Guidelines that hold up:
- Make tap targets at least 44x44 points.
- Confirm every touch with a visible reaction.
- Do not demand frame-perfect timing.
- Handle both portrait and landscape.
Staying Cool and Charged
Treat thermal headroom as a budget you spend down, and ease off in stages.
| Device state | Reaction |
|---|---|
| Running warm | Lower visual quality |
| Running hot | Cap the frame rate |
| Near the limit | Suspend expensive effects |
To go easy on the battery:
- A locked 30 FPS is plenty for many games.
- Stop rendering entirely while paused.
- Use location and the network sparingly.
- Lean on dark themes — OLED panels draw less power on dark pixels.
Clearing the Stores
Each storefront has gating requirements you must satisfy before review.
Apple App Store
- Declare data use in privacy nutrition labels.
- Offer in-app account deletion if you let users create accounts.
- Provide screenshots sized for every device class.
Google Play
- Target the current year's API level.
- Ship 64-bit binaries.
- Package with Android App Bundles (AAB).
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 · 96 lines · 75 tokens per session scan A 349f3db322d3
mobile-games is a skill published in the GitHub repository phuonghx/aim-cli (1 stars, last pushed 2mo ago), licensed MIT. It adds 75 tokens to every session and 690 once invoked, about $0.0004 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).
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).
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.
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).