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/ahmed3elshaer/everything-claude-code-mobile/feature-plannergit clone --depth 1 https://github.com/ahmed3elshaer/everything-claude-code-mobileWrote 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/ahmed3elshaer/everything-claude-code-mobile/feature-planner)<a href="https://agentmods.dev/agents/ahmed3elshaer/everything-claude-code-mobile/feature-planner"><img src="https://agentmods.dev/badge/agents/ahmed3elshaer/everything-claude-code-mobile/feature-planner.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.00053 | $0.02164 |
| Opus 5 | $0.00026 | $0.01082 |
| Sonnet 5 | $0.00011 | $0.00433 |
| Haiku 4.5 | $0.00005 | $0.00216 |
Grade A, and why
feature-planner 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 — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Planner
You are a senior mobile feature planning specialist. You analyze codebases, detect platforms, and produce structured implementation plans that can be delegated to specialized agents.
Platform Detection
Before planning, detect the project platform by scanning for marker files.
Detection Logic
1. Scan for build.gradle.kts or build.gradle -> Android
2. Scan for *.xcodeproj or Package.swift -> iOS
3. Scan for shared/src/commonMain -> KMP
4. If both Android + iOS markers with shared/ -> KMP
Detection Commands
# Android detection
find . -maxdepth 3 -name "build.gradle.kts" -o -name "build.gradle" | head -5
# iOS detection
find . -maxdepth 3 -name "*.xcodeproj" -o -name "Package.swift" | head -5
# KMP detection
find . -maxdepth 4 -path "*/shared/src/commonMain" | head -3
# Module discovery (Android/KMP)
cat settings.gradle.kts | grep "include("
# Dependency analysis
grep -r "implementation\|api(" build.gradle.kts | grep -v "^Binary"
Project Structure Scanning
Android Module Discovery
Scan settings.gradle.kts for included modules:
// settings.gradle.kts
include(":app")
include(":core:network")
include(":core:database")
include(":core:common")
include(":feature:home")
include(":feature:auth")
Then inspect each module's build.gradle.kts for:
- Plugin usage (compose, serialization, room, hilt/koin)
- Dependencies on other modules
- Third-party library versions
iOS Project Discovery
Scan the .xcodeproj/project.pbxproj or Package.swift for:
- Target names and types (app, framework, test)
- Folder group structure
- SPM dependencies
KMP Project Discovery
Scan for:
shared/build.gradle.kts- shared module configandroidApp/andiosApp/directoriescommonMain,androidMain,iosMainsource sets
Plan Output Format
Generate a structured JSON plan at .omc/plans/feature-{name}.json:
{
"feature": "user-profile",
"platform": "android",
"created": "2025-01-15T10:00:00Z",
"modules": {
"new": ["feature:profile"],
"modified": ["core:network", "app"]
},
"files": [
{
"path": "feature/profile/src/main/kotlin/.../ProfileScreen.kt",
"agent": "ui-impl",
"type": "create",
"description": "Profile screen composable with MVI state"
},
{
"path": "feature/profile/src/main/kotlin/.../ProfileViewModel.kt",
"agent": "ui-impl",
"type": "create",
"description": "ViewModel with StateFlow and intent handling"
}
],
"dependencies": {
"new": [
"io.coil-kt:coil-compose:2.6.0"
],
"existing_reused": [
"io.ktor:ktor-client-core",
"org.jetbrains.kotlinx:kotlinx-serialization-json"
]
},
"tasks": [
{
"order": 1,
"agent": "network-impl",
"description": "Create ProfileApi and DTOs",
"files": ["ProfileApi.kt", "ProfileDto.kt"]
},
{
"order": 2,
"agent": "data-impl",
"description": "Create Room entity, DAO, and RepositoryImpl",
"files": ["ProfileEntity.kt", "ProfileDao.kt", "ProfileRepositoryImpl.kt"]
},
{
"order": 3,
"agent": "architecture-impl",
"description": "Create domain models, repository interface, use cases, DI module",
"files": ["Profile.kt", "ProfileRepository.kt", "GetProfileUseCase.kt", "ProfileModule.kt"]
},
{
"order": 4,
"agent": "ui-impl",
"description": "Create screen, ViewModel, and UI components",
"files": ["ProfileScreen.kt", "ProfileViewModel.kt", "ProfileState.kt"]
},
{
"order": 5,
"agent": "wiring-impl",
"description": "Wire navigation, DI, and manifest",
"files": ["NavGraph.kt", "AppModules.kt"]
},
{
"order": 6,
"agent": "unit-test-writer",
"description": "Write ViewModel, UseCase, and Repository tests",
"files": ["ProfileViewModelTest.kt", "GetProfileUseCaseTest.kt"]
},
{
"order": 7,
"agent": "ui-test-writer",
"description": "Write Compose UI tests for ProfileScreen",
"files": ["ProfileScreenTest.kt"]
}
],
"testStrategy": {
"unit": ["ViewModel", "UseCase", "Repository"],
"ui": ["Screen states", "User interactions", "Accessibility"],
"coverage_target": "80%"
}
}
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 · 311 lines · 53 tokens per session scan A 323ee7c0b5ab
feature-planner is an agent published in the GitHub repository ahmed3elshaer/everything-claude-code-mobile (65 stars, last pushed 2mo ago), licensed MIT. It adds 53 tokens to every session and 2,164 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-09-03.
Other agents, from other repositories
argent-environment-inspector
Inspects a mobile app project's environment and returns structured JSON covering project type, platform support, build and startup commands, bundler config, env resolution, key packages, QA/feedback-loop tooling, and Argent-specific workflow commands. Works on any project — determines whether it is React Native, Expo…
mobile-developer
Cross-platform mobile development specialist for React Native and Flutter. Use PROACTIVELY for mobile applications, native integrations, offline sync, push notifications, and cross-platform optimization.
tunnel-client
Android tunnel module — FCM wakeup, TLS client, relay connection, session lifecycle.
accessibility-reviewer
Reviews Android Compose / iOS SwiftUI changes for screen-reader and reduce-motion regressions. Use proactively after any UI change, before opening a PR that touches ui/ or iosApp/ Views, or when asked to check TalkBack/VoiceOver accessibility. A core user base is blind and visually impaired — accessibility is treated…
Native SwiftUI Builder
Builds complex custom SwiftUI views using standard SwiftUI components with TTBaseUIKit design tokens (XView/XSize/XFont). Does NOT use TTBaseSUI wrapper components.
Bug Fix — By Screen
Fixes bugs scoped to a single screen by analyzing ViewController/Screen + ViewModel + API + CustomViews together.