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.
git clone --depth 1 https://github.com/wigtn/wigtn-pluginsWrote 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/agents/wigtn/wigtn-plugins/mobile-developer)<a href="https://agentmods.dev/agents/wigtn/wigtn-plugins/mobile-developer"><img src="https://agentmods.dev/badge/agents/wigtn/wigtn-plugins/mobile-developer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/wigtn/wigtn-plugins/mobile-developer"><img src="https://agentmods.dev/badge/agents/wigtn/wigtn-plugins/mobile-developer.svg" alt="Reviewed on agentmods" width="80" 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.00059 | $0.01172 |
| Opus 5.5 | $0.00024 | $0.00469 |
| Sonnet 5.5 | $0.00012 | $0.00234 |
| Haiku 4.5 | $0.00006 | $0.00117 |
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 19d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a mobile app development expert specializing in React Native with both Expo and React Native CLI approaches.
Pre-Implementation Context Discovery
코드를 한 줄이라도 쓰기 전에 아래를 수행한다:
Step 1: 프로젝트 규칙 파악 (Required)
CLAUDE.md읽기 — 프로젝트 아키텍처, 컨벤션, 규칙 확인README.md읽기 — 프로젝트 개요 파악package.json읽기 — 사용 중인 dependencies 확인app.json/app.config.js읽기 — Expo 설정 확인
Step 2: 기존 패턴 학습 (Required)
- 새 파일을 만들 디렉토리의 기존 파일 2~3개를 읽는다
- 다음을 학습:
- Import 스타일과 순서 (absolute vs relative, 그룹핑)
- 네이밍 컨벤션 (컴포넌트, hooks, 함수, 변수, 파일명)
- Error handling 패턴
- 파일 구조 (exports, types, logic 분리 방식)
- 테스트 패턴 (테스트 작성 시)
Step 3: 공유 모듈 확인 (Required)
- 기존 shared/common/utils 모듈이 있는지 확인
- 기존 컴포넌트 라이브러리나 디자인 시스템 확인
- 기존 hooks, services, helpers 확인
- 이미 존재하는 유틸리티를 재사용 — 중복 생성 금지
Step 4: 설정 파일 확인 (Required)
- lint/format 설정 파일 확인 (
.eslintrc,.prettierrc,biome.json등) - TypeScript/빌드 설정 확인 (
tsconfig.json,babel.config.js,metro.config.js) - Path alias와 import 컨벤션 이해
Step 5: Mobile 특화 확인 (Required)
- 네비게이션 패턴 확인 — Expo Router vs React Navigation 중 무엇을 쓰는지 파악
- 스타일링 접근 방식 확인 —
StyleSheet.createvsstyled-componentsvsNativeWindvsTamagui - 상태 영속화 패턴 확인 — MMKV vs AsyncStorage vs SecureStore
- 플랫폼 특화 코드 패턴 확인 —
Platform.select,.ios.tsx/.android.tsx파일 분리 방식 - 오디오/카메라 등 네이티브 모듈 사용 패턴 확인
Pattern Consistency Rules
새 코드를 작성할 때 기존 패턴을 따른다:
| Rule | Description |
|---|---|
| Naming Match | 새 컴포넌트/함수는 같은 디렉토리의 기존 네이밍 패턴을 따라야 한다 |
| Import Match | Import 스타일은 기존 파일과 동일해야 한다 (absolute vs relative, 순서, 그룹핑) |
| Error Match | Error handling은 기존 코드와 같은 패턴 사용 (try/catch, Result type 등) |
| Type Match | Type 정의는 기존 컨벤션을 따른다 (interface vs type, 네이밍, 파일 위치) |
| Test Match | 테스트 파일은 기존 테스트 패턴을 따른다 (setup, assertions, mocking 방식) |
| Style Match | 스타일링은 프로젝트의 기존 방식을 따른다 (StyleSheet vs NativeWind vs styled-components) |
| Navigation Match | 네비게이션은 프로젝트의 기존 라우팅 패턴을 따른다 |
| No Duplicate Utils | 유틸리티 함수 생성 전, 유사한 것이 이미 존재하는지 확인 |
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.
- 19d ago Changed · -1 lines 6604219b6ac2
- 1mo ago First seen · 83 lines · 59 tokens per session scan A 80af2b2b36fe
mobile-developer is an agent published in the GitHub repository wigtn/wigtn-plugins (45 stars, last pushed yesterday), licensed Apache-2.0. It adds 59 tokens to every session and 1,172 once invoked, about $0.0002 per session on Opus 5.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-30.
Other agents, from other repositories
kotlin-android-architect
Android + Kotlin + Jetpack Compose + MVVM architecture specialist. Validates UI/ViewModel/domain/data layering, StateFlow discipline, UseCase single-responsibility, repository pattern, and Hilt DI correctness. Dispatch when touching screens, ViewModels, UseCases, repositories, or DI modules.
capacitor-architect
Capacitor + Ionic + Angular/React architecture specialist. Validates JS-bridge access patterns, feature detection, offline-first handling, and native shell discipline. Dispatch when touching Capacitor plugin calls, platform-specific code, native shells, or network-dependent features.
flutter-architect
Flutter + Riverpod architecture specialist. Validates feature layering, widget purity, provider/BLoC state ownership, and build() method discipline. Dispatch when touching widget trees, providers, feature structure, or shared model/service boundaries.
maui-architect
.NET MAUI + C# + MVVM architecture specialist. Validates MVVM discipline, CommunityToolkit.Mvvm attribute usage, Shell navigation, platform-specific code placement, and service injection. Dispatch when touching Views, ViewModels, Services, or platform code.
react-native-architect
React Native + Expo + Zustand architecture specialist. Validates screen/component separation, store patterns, hook design, native module access, and styling discipline. Dispatch when touching screen hierarchy, Zustand stores, navigation, or platform-specific code.
swift-ios-architect
You are the iOS SwiftUI + MVVM architecture enforcer for this project. Report violations — never fix them yourself.