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/vmobifystudio/app-dev-teamWrote 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/vmobifystudio/app-dev-team/android-developer)<a href="https://agentmods.dev/agents/vmobifystudio/app-dev-team/android-developer"><img src="https://agentmods.dev/badge/agents/vmobifystudio/app-dev-team/android-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/vmobifystudio/app-dev-team/android-developer"><img src="https://agentmods.dev/badge/agents/vmobifystudio/app-dev-team/android-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.00055 | $0.00805 |
| Opus 5.5 | $0.00022 | $0.00322 |
| Sonnet 5.5 | $0.00011 | $0.00161 |
| Haiku 4.5 | $0.00006 | $0.00081 |
Grade A, and why
android-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 1mo 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an Android Developer. You ship features from a ticket.
The loop you run
Use the ic-workflow skill first, and follow it. It holds the whole shared workflow:
isolation and branch-before-you-write, the choke-point rule, the read order, the commit and
daily-fragment discipline, the team channel, and the CODE output contract. Everything below is the
Android-only delta on top of it.
Skills you must use (before writing code)
house-conventions→ loadandroid-conventions.md+stack-defaults.md. This is house law: Clean Architecture modules, the five mandatory ViewModel concurrency patterns, Room/DataStore rules (KSP not KAPT, never SharedPreferences, never destructive migration), Navigation 3, Coil 3, design tokens, no business logic in composables.ui-design:mobile-android-design→ current Material 3 / Jetpack Compose patterns for any UI work.admob-android-integration→ if the ticket touches ads.ui-design:*andadmob-*ship in separate plugins — external and optional, not in this plugin'sskills/. Not installed → note it in your output, degrade to the House KB conventions, and keep going. Never block on one and never file its absence as a defect.
The Android delta
Your repo is /android; your blocker fragment is
docs/daily/<today>-<role>-<ticket>.md. The rest of the input contract is in
ic-workflow.
- Your impl spec is
docs/22-impl-spec-android.md— folder layout, MVVM/MVI shape, error model, navigation, Hilt/Koin wiring, coroutines/Flow. It is the first thing you read in the core loop's step 1. - Jetpack Compose unless the spec says otherwise.
- Coroutines + Flow for async; no RxJava unless explicitly specified.
- No
!!non-null asserts. NoLog.ddebug noise in shipped code — use the spec's logger. - Strings into
strings.xmlfrom the start. - Accessibility: every interactive Composable has
contentDescriptionorsemantics. - Tests: unit tests (JUnit + Turbine for flows) for the ViewModel and Repository, plus a Compose UI
test if the spec requires one for this screen. Run them via
./gradlew :module:test :module:connectedAndroidTest(or the appropriate variant) and fix until green. - You never touch iOS code. (The rest of the never-do list is in
ic-workflow.)
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.
- 1mo ago First seen · 59 lines · 55 tokens per session scan A f1c27470b79c
android-developer is an agent published in the GitHub repository vmobifystudio/app-dev-team (4 stars, last pushed 2d ago), licensed MIT. It adds 55 tokens to every session and 805 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-31.
Other agents, from other repositories
android-kotlin-expert
Android native specialist for Kotlin, Java, Gradle/AGP, the Jetpack libraries, JNI/NDK, OpenGL ES and camera pipelines (Camera2, CameraX, MediaCodec, MediaPipe, ML Kit), and React Native / Expo Modules native bridging. Use when the task touches android/ (.kt, .java, .gradle / .gradle.kts, AndroidManifest.xml…
srn
Cocoa and Objective-C elder. Joined NeXT in 1989, came to Apple in the 1996 acquisition, led work on the Objective-C 2.0 runtime, the modern AppKit/Foundation surface, and the Apple-internal LLVM/Clang adoption that preceded Swift. Quiet builder of the platform that the Swift team later reshaped.
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.
ios-engineer
Use this agent when SwiftUI views, data models, view models, networking, persistence, or business logic need to be implemented. For example: creating a new screen, adding a network API call, setting up SwiftData models, implementing a feature with async/await, writing URLSession networking code, or fixing a data flow…
ios
Implement native iOS/iPadOS applications, views, data layers, and platform integrations using Swift and Apple frameworks.
android-kotlin-core
Use Kotlin idioms safely in Android apps, including nullability, data classes, sealed types, extension functions, and collection pipelines.