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 skills add davideagostini/ai-dev-skills --skill android-compose-startergit clone --depth 1 https://github.com/davideagostini/ai-dev-skillsWrote 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/davideagostini/ai-dev-skills/android-compose-starter)<a href="https://agentmods.dev/skills/davideagostini/ai-dev-skills/android-compose-starter"><img src="https://agentmods.dev/badge/skills/davideagostini/ai-dev-skills/android-compose-starter.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.00067 | $0.01500 |
| Opus 5 | $0.00034 | $0.00750 |
| Sonnet 5 | $0.00013 | $0.00300 |
| Haiku 4.5 | $0.00007 | $0.00150 |
Grade A, and why
android-compose-starter 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 7d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an Android architecture expert. Your job is to guide the user through building $ARGUMENTS — a production-ready Android + Jetpack Compose project following modern best practices.
Work through the WORKFLOW below step by step. At each step, consult the relevant reference file before giving instructions. Do not skip steps. Do not add libraries, patterns, or abstractions that are not needed yet.
WORKFLOW
Step 1 — Create the Android project
→ Consult project-setup.md
- Create a new project in Android Studio using the Empty Activity template
- Choose Kotlin, minimum SDK 26+, build config Kotlin DSL (
build.gradle.kts) - Set up
gradle/libs.versions.toml— all dependency versions live here, never inline - Configure
gradle.propertieswith performance and compatibility flags - Verify
./gradlew assembleDebugsucceeds before adding any library
Step 2 — Select and add libraries
→ Consult libraries.md
- Add libraries by category: UI (Compose BOM), DI (Hilt), async (Coroutines), networking, persistence
- Check current-latest stable versions on Google Maven and Maven Central
- Register every version in
[versions], every artifact in[libraries], every plugin in[plugins] - Add only what you need now — remove the "just in case" libraries
Core libraries to always include:
| Category | Library |
|---|---|
| UI | Compose BOM, Material3, activity-compose |
| Lifecycle | lifecycle-viewmodel-compose, lifecycle-runtime-compose |
| Navigation | navigation-compose |
| DI | hilt-android, hilt-navigation-compose (+ KSP compiler) |
| Async | kotlinx-coroutines-android |
Add networking (Retrofit + Moshi), persistence (Room or DataStore), and image loading (Coil) only when a feature requires them.
Step 3 — Set up the architecture skeleton
→ Consult architecture.md
- Create
App.ktwith@HiltAndroidApp - Create
MainActivitywith@AndroidEntryPoint,setContent { AppTheme { AppNavigation() } } - Create
BaseViewModelwith shared toast/snackbarSharedFlows - Create
navigation/Screen.ktsealed class with all route objects - Create
navigation/Navigation.ktwithNavHost - Create DI modules in
di/for each dependency category
What ships with it
17 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- README.md 5.3 KB
- references/accessibility.md 11 KB
- references/animation.md 10 KB
- references/architecture.md 12 KB
- references/common-bugs.md 1.0 KB
- references/composition-locals.md 11 KB
- references/deprecated-migrations.md 19 KB
- references/libraries.md 11 KB
- references/lists-and-scrolling.md 13 KB
- references/modifiers.md 10 KB
- references/performance.md 10 KB
- references/principles.md 1.6 KB
- references/project-setup.md 12 KB
- references/readiness-checklist.md 1.3 KB
- references/side-effects.md 13 KB
- references/state-management.md 11 KB
- references/view-composition.md 13 KB
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.
- 7d ago First seen · 129 lines · 67 tokens per session scan A 394b3b2542fe
android-compose-starter is a skill published in the GitHub repository davideagostini/ai-dev-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 67 tokens to every session and 1,500 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-08-31.
Other skills, from other repositories
compose-animations
Use when writing or reviewing Jetpack Compose motion: visibility enter/exit, animating one property toward a target, color or size transitions, multiple properties from one state, switching composable content, or choosing between AnimatedVisibility, animateAsState, rememberTransition, AnimatedContent, and Crossfade.
compose-focus-navigation
Use when writing or reviewing Jetpack Compose UI for TV, keyboard, desktop, accessibility focus, D-pad navigation, FocusRequester, focusProperties, key events, or initial focus behavior.
ios-slim-bindings
Create iOS slim bindings for MAUI. USE FOR: slim iOS binding, Native Library Interop, Swift/Objective-C wrappers, XcodeGen project.yml, Podfile, CocoaPods static linking, BUILDLIBRARYFORDISTRIBUTION, XcodeProject MSBuild, @objc/[Export] selector crashes, async completion handlers. DO NOT USE FOR: Android bindings…
kmp-lsp
Kotlin/Java/Swift LSP server for code navigation in Android and iOS codebases. Use when navigating Kotlin, Java, or Swift source files: finding class definitions, listing symbols, jumping to implementations, finding all usages, checking type signatures, or switching workspace between projects. Triggers for: "find this…
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…
kotlin-android
Use when building or fixing a native Android app in Kotlin and Jetpack Compose on the UDF layered architecture — ViewModel/StateFlow, Hilt, Room, Retrofit, coroutines, type-safe Navigation, and the Gradle/AGP surface. NOT shared Android and iOS UI from one Kotlin codebase (that is compose-multiplatform).