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/arbazkhan971/godmode/mobilenpx skills add arbazkhan971/godmode --skill mobilegit clone --depth 1 https://github.com/arbazkhan971/godmodeWrote 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/arbazkhan971/godmode/mobile)<a href="https://agentmods.dev/skills/arbazkhan971/godmode/mobile"><img src="https://agentmods.dev/badge/skills/arbazkhan971/godmode/mobile.svg" alt="Measured on agentmods" 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.00014 | $0.01081 |
| Opus 5 | $0.00007 | $0.00541 |
| Sonnet 5 | $0.00003 | $0.00216 |
| Haiku 4.5 | $0.00001 | $0.00108 |
Grade A, and why
mobile 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Activate When
/godmode:mobile, "mobile app", "iOS", "Android"- "React Native", "Flutter", "Swift", "Kotlin"
- App signing, store submission, mobile performance
Workflow
1. Platform Assessment
Target: iOS|Android|both
Approach: native|cross-platform|hybrid
IF cross-platform:
Framework: React Native|Flutter|KMP|.NET MAUI
Shared: business logic only|business+UI|everything
# Detect existing mobile project
ls ios/ android/ pubspec.yaml 2>/dev/null
ls package.json | xargs grep -l "react-native" 2>/dev/null
2. Architecture Selection
MVVM: most apps, reactive UI frameworks
models/ -> views/ -> viewmodels/
MVI: complex state, unidirectional data flow
State (immutable) -> Intent (actions) -> Reducer
Clean Architecture: large apps, complex business logic
Presentation -> Domain -> Data (dependency inversion)
IF app < 10 screens: MVVM is sufficient. IF state management complex: prefer MVI. IF > 30 screens with multiple data sources: Clean Arch.
3. Project Setup
iOS: bundle ID, min deployment target, ATS, Info.plist privacy descriptions, launch screen. Android: package name, min/target SDK, ProGuard, build variants (debug/staging/release). React Native: TypeScript, React Navigation, state management, Metro config. Flutter: pubspec.yaml, state management (Riverpod/Bloc), GoRouter, flavors (dev/staging/prod).
4. App Signing
iOS: Dev cert + provisioning profile (development),
Dist cert + App Store profile (release).
NEVER share private keys. Use Fastlane match.
Android: keytool -genkey -v -keystore release.keystore
NEVER lose the keystore (app updates impossible).
Store in secure vault, not in VCS.
5. Store Submission
iOS App Store:
[ ] Review Guidelines compliance
[ ] Privacy policy URL
[ ] App Privacy labels
[ ] Screenshots (6.7", 5.5" minimum)
[ ] App name (30 char max)
Google Play:
[ ] Developer Policy compliance
[ ] Data safety section
[ ] AAB format (not APK)
[ ] Screenshots + feature graphic
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 · 148 lines · 14 tokens per session scan A 965f9ff23ce9
mobile is a skill published in the GitHub repository arbazkhan971/godmode (26 stars, last pushed 8d ago), licensed MIT. It adds 14 tokens to every session and 1,081 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
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".…
asc-revenuecat-catalog-sync
Reconcile App Store Connect subscriptions and in-app purchases with RevenueCat products, entitlements, offerings, and packages using asc and RevenueCat MCP. Use when setting up or syncing subscription catalogs across ASC and RevenueCat.
asc-metadata-sync
Sync, validate, and apply App Store metadata with the current asc canonical metadata workflow. Use when updating metadata, localizations, keywords, or migrating legacy fastlane metadata.
asc-xcode-build
Build, archive, generate export options, export, upload, and manage Xcode version/build numbers with the current asc xcode helpers. Use when creating an IPA or PKG for App Store Connect, TestFlight, or registered-device release testing.
asc-app-create-ui
Create a new App Store Connect app record via browser automation. Use when there is no public API for app creation and you need an agent to drive the New App form.
asc-id-resolver
Resolve App Store Connect IDs (apps, builds, app and digital-goods versions, groups, testers) from human-friendly names using asc. Use when commands require IDs.