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/mtnyilmaz/agents/mobile-developernpx skills add mtnyilmaz/agents --skill mobile-developergit clone --depth 1 https://github.com/mtnyilmaz/agentsWhat 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.00053 | $0.01200 |
| Opus 5 | $0.00026 | $0.00600 |
| Sonnet 5 | $0.00011 | $0.00240 |
| Haiku 4.5 | $0.00005 | $0.00120 |
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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile Developer
Expert in building production-grade mobile apps with React Native and Expo.
Reference Documentation
Read these docs when needed:
.agents/rules/design-system.md— Tokens, component layering, loading/empty/error UX (bundled for Expo installs).agents/rules/native-ux-design.md— Safe area, touch targets, platform patterns, parity with web.agents/rules/frontend-patterns.md— Mobile sections (Expo Router, components, state).agents/rules/project-architecture.md— See apps/mobile section.agents/rules/project-architecture.md— tRPC mobile client, shared Zod schemas.agents/rules/auth-patterns.md— JWT flow for mobile, SecureStore token management.agents/rules/project-architecture.md— Package versions
Expo Official Guides (References)
Official detailed instructions from the Expo team. Read these for specialized topics:
references/expo/building-native-ui/— Native view creationreferences/expo/expo-api-routes/— API routes in Exporeferences/expo/expo-cicd-workflows/— CI/CD via EASreferences/expo/expo-deployment/— Apple/Google stores deployreferences/expo/expo-tailwind-setup/— NativeWind & Tailwind setupreferences/expo/native-data-fetching/— Fetching on nativereferences/expo/upgrading-expo/— Expo SDK upgrades
App Structure (Expo Router)
apps/mobile/
app/
_layout.tsx ← root layout (providers, fonts, theme)
(auth)/
_layout.tsx
login.tsx
register.tsx
(tabs)/
_layout.tsx ← bottom tab navigator
index.tsx ← home tab
profile.tsx
(modals)/
confirm.tsx
components/ ← mobile-specific components
hooks/ ← mobile hooks (useCamera, useLocation, etc.)
lib/
secure-store.ts ← Token CRUD (single source of truth)
api-client.ts ← REST client with token interceptor + 401 handler
trpc.ts ← tRPC client (reads from same tokenStore)
services/ ← Endpoint functions (never handle tokens)
store/ ← Zustand stores
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.
- 2d ago First seen · 140 lines · 53 tokens per session scan A b8133fcf32b1
mobile-developer is a skill published in the GitHub repository mtnyilmaz/agents (6 stars, last pushed 3mo ago), licensed MIT. It adds 53 tokens to every session and 1,200 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
edge-to-edge
Use this skill to migrate your Jetpack Compose app to add adaptive edge-to-edge support and troubleshoot common issues. Use this skill to fix UI components (like buttons or lists) that are obscured by or overlapping with the navigation bar or status bar, fix IME insets, and fix system bar legibility.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
flutter-fix-layout-issues
Fixes Flutter layout errors (overflows, unbounded constraints) using Dart and Flutter MCP tools. Use when addressing "RenderFlex overflowed", "Vertical viewport was given unbounded height", or similar layout issues.
referral-program
When the user wants to design, launch, or optimize an in-app referral / invite / share-to-earn program — including reward structure, mechanics, fraud prevention, deep link setup, and viral coefficient measurement. Use when the user mentions "referral program", "invite a friend", "refer and earn", "share to earn"…
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.
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".…