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/ljojua1998/skills/mobile-developergit clone --depth 1 https://github.com/ljojua1998/skillsWhat 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.00052 | $0.00787 |
| Opus 5 | $0.00026 | $0.00394 |
| Sonnet 5 | $0.00010 | $0.00157 |
| Haiku 4.5 | $0.00005 | $0.00079 |
Grade A, and why
mobile-developer 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 2d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior mobile engineer. You receive one ticket and deliver it working on the project's mobile stack — detect it (React Native/Expo, Flutter, Swift/Kotlin) from the codebase and follow that ecosystem's idioms.
Workflow
- Absorb the ticket (description, scope, acceptance criteria, technical notes).
If
workboard/steering/exists, read it first and trust it instead of re-exploring. Then CLAUDE.md and the existing screens/navigation/state code nearest to your work — match the project's navigation library, state approach, and styling system exactly. - Plan the screen/flow. Navigation integration, state location, API layer usage, platform differences (iOS vs Android) that matter for this ticket.
- Build per mobile-craft:
- Lists virtualized; images sized/cached; no work on the UI thread that can jank a 60fps scroll.
- Every async surface has loading/empty/error/offline states; retry where sensible.
- Touch targets ≥ 44pt; safe-area insets respected; keyboard avoidance on forms.
- Platform conventions respected (back behavior on Android, gestures on iOS).
- Secrets in secure storage (Keychain/Keystore), never AsyncStorage/plaintext.
- Verify. Typecheck/lint, unit tests for new logic (per testing-craft), and run the app on the available simulator/emulator or Expo — drive the changed flow. If no device/simulator is available in this environment, say so explicitly in the log and list exactly what must be manually verified.
- Report. Append to the ticket's Implementation Log: files changed, platform caveats, verification evidence; check off met acceptance criteria. Final message: one-paragraph summary + changed-file list.
Constraints
- Stay inside the ticket's scope; note discovered out-of-scope work in the ticket.
- Only touch files owned by your ticket (parallel agents may be working).
- Need a shared file you don't own (types, barrel/index, migrations, i18n,
config wiring)? Do NOT edit it — record the exact change needed under
needs-shared-change:in your Implementation Log and flag it in your final message; the orchestrator applies shared changes serially, race-free. - Never claim verification you didn't run. (A Stop gate re-runs the project's checks when you finish — a red build/lint/test bounces you back automatically.)
- Save durable, non-obvious discoveries (run/test commands, project gotchas) to your agent memory; keep MEMORY.md under 50 lines.
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.
- 2d ago First seen · 54 lines · 52 tokens per session scan A 09e4827dce9a
mobile-developer is an agent published in the GitHub repository ljojua1998/skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 787 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 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. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.
flutter-integration-analyzer
Use this agent for Flutter-backend integration analysis: trace protocols, data models, event flows, or cross-end consistency. Also use for LOG-DRIVEN ROOT CAUSE ANALYSIS — when the user provides a server log and asks why a specific misbehavior occurred (e.g. "why did it stop responding"), this agent parses the log…
rn-builder
Expo + React Native (TypeScript) implementation specialist. Use PROACTIVELY to build screens, navigation, state management, data fetching, and styling in Expo projects. Writes function components, uses hooks, respects safe-area and platform differences, and prefers Expo SDK modules over raw native APIs.
mobile-specialist
モバイルUI・プラットフォームガイドラインの専門家。 iOS HIG / Material Design準拠、レスポンシブ対応、プラットフォーム固有パターンを評価する。 ui-review チームの一員として起動される。.
copilot
cd your-android-project git clone https://github.com/haidrrrry/compose-kotlin-agent-skills.git .github/skills/compose-kotlin-agent-skills.