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/kevinzai/commander/ccc-mobilenpx skills add KevinZai/commander --skill ccc-mobilegit clone --depth 1 https://github.com/KevinZai/commanderWrote 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/kevinzai/commander/ccc-mobile)<a href="https://agentmods.dev/skills/kevinzai/commander/ccc-mobile"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-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 | $0.00039 | $0.00754 |
| Opus 5 | $0.00019 | $0.00377 |
| Sonnet 5 | $0.00008 | $0.00151 |
| Haiku 4.5 | $0.00004 | $0.00075 |
Grade A, and why
ccc-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 3d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$ccc-mobile — Mobile domain hub
Load ONE skill. Get the entire mobile development domain. 8 skills in one.
Sub-Skills
| # | Skill | Focus |
|---|---|---|
| 1 | react-native | React Native development — Expo, navigation, native modules, state management |
| 2 | flutter | Flutter/Dart — widget architecture, state management, platform channels |
| 3 | swiftui | SwiftUI — MVVM patterns, Combine, iOS-specific features |
| 4 | jetpack-compose | Jetpack Compose — Material Design 3, Android lifecycle |
| 5 | mobile-testing | Mobile testing — Detox, Maestro, XCTest, Espresso |
| 6 | app-store-optimization | ASO — App Store + Play Store listing optimization |
| 7 | push-notifications | Push notifications — FCM, APNs, OneSignal, Expo Notifications |
| 8 | deep-linking | Universal links, App Links, deep link configuration |
No expressed intent? Present the top 3 sub-skills + "More…" as an AskUserQuestion picker (≤4 options).
Routing Matrix
| Your Intent | Route To |
|---|---|
| "React Native" / "Expo" | react-native |
| "Flutter" / "Dart" | flutter |
| "iOS" / "SwiftUI" | swiftui |
| "Android" / "Jetpack Compose" | jetpack-compose |
| "Mobile tests" / "Detox" / "Maestro" | mobile-testing |
| "App Store" / "Play Store" / "ASO" | app-store-optimization |
| "Push notifications" / "FCM" / "APNs" | push-notifications |
| "Deep links" / "Universal links" | deep-linking |
Platform Selection Guide
| Need | Recommendation |
|---|---|
| One codebase, both platforms | React Native (larger ecosystem) or Flutter (stronger UI) |
| iOS-only, native feel | SwiftUI |
| Android-only, native feel | Jetpack Compose |
| Performance-critical | Flutter (Impeller) or native |
| Existing web team (React) | React Native |
When to invoke this skill
Example 1
- user: build a React Native app with navigation and native modules
- assistant: Loads ccc-mobile and routes to react-native skill for Expo/bare workflow, React Navigation, and native module integration patterns.
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.
- 3d ago First seen · 71 lines · 39 tokens per session scan A d4d8e20cddb6
ccc-mobile is a skill published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 754 once invoked, about $0.0002 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
android-kotlin
Android Kotlin development with Coroutines, Jetpack Compose, Hilt, and MockK testing.
apple-app-store-reviewer
Audit Apple-platform apps before App Store submission or resubmission. Use for iOS, iPadOS, macOS, tvOS, watchOS, and visionOS release reviews involving source code, archives or IPAs, App Store Connect metadata, screenshots, subscriptions, login, privacy manifests, AI features, UGC, age ratings, review notes, or an…
mobile-design
Generates distinctive, production-grade mobile interfaces for Flutter and React Native. Prioritizes platform-native patterns, adaptive layouts, and fluid motion. Use when building mobile apps, screens, widgets, or when the user requests to style or create visually striking mobile UI.
compose-multiplatform
Use when building one shared Compose UI in Kotlin across Android, iOS, and desktop — commonMain @Composables, expect/actual, source-set placement, native interop, multiplatform ViewModel/navigation/Koin. NOT a single-platform native build (that is kotlin-android / swift-ios), and NOT Dart/Flutter cross-platform UI…
modify-feature
Modify existing KMP features with spec-first workflow. Invoke with /modify-feature.
create-feature
Creates complete KMP features with Clean Architecture through PRD generation, task breakdown, orchestrated implementation, and spec-driven cleanup. Invoke with /create-feature.