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/piyushverma0/android-agent-skills/android-setupnpx skills add piyushverma0/android-agent-skills --skill android-setupgit clone --depth 1 https://github.com/piyushverma0/android-agent-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/piyushverma0/android-agent-skills/android-setup)<a href="https://agentmods.dev/skills/piyushverma0/android-agent-skills/android-setup"><img src="https://agentmods.dev/badge/skills/piyushverma0/android-agent-skills/android-setup.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.00133 | $0.02706 |
| Opus 5 | $0.00067 | $0.01353 |
| Sonnet 5 | $0.00027 | $0.00541 |
| Haiku 4.5 | $0.00013 | $0.00271 |
Grade A, and why
android-setup 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 6d 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 — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Android Project Setup
Correct project initialization prevents 80% of downstream agent errors. Read this entire skill before writing any build files.
Non-negotiables
- Kotlin DSL only (
build.gradle.kts,settings.gradle.kts) — never Groovy.gradle - Version Catalog only (
libs.versions.toml) — never hardcode versions in build files - KSP only — never
kapt minSdk = 24,targetSdk = 35,compileSdk = 35- Kotlin
2.0.0+, AGP8.5.0+ namespacedeclared in every module'sbuild.gradle.kts
Project Structure
my-app/
├── app/
│ ├── src/main/
│ │ ├── java/com/company/app/
│ │ │ ├── MainActivity.kt
│ │ │ └── MyApplication.kt
│ │ ├── res/
│ │ └── AndroidManifest.xml
│ └── build.gradle.kts
├── core/
│ ├── data/
│ ├── domain/
│ └── ui/
├── feature/
│ └── <feature-name>/
├── gradle/
│ └── libs.versions.toml ← ALL versions live here
├── build.gradle.kts ← root, no dependencies
├── settings.gradle.kts
└── gradle.properties
settings.gradle.kts
pluginManagement {
repositories {
google { content { includeGroupByRegex("com\\.android.*"); includeGroupByRegex("com\\.google.*"); includeGroupByRegex("androidx.*") } }
mavenCentral()
gradlePluginPortal()
}
}
dependencyResolutionManagement {
repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
repositories {
google()
mavenCentral()
}
}
rootProject.name = "MyApp"
include(":app")
// include(":core:data") // add modules as needed
Root build.gradle.kts
// Top-level build file. Do NOT add dependencies here.
plugins {
alias(libs.plugins.android.application) apply false
alias(libs.plugins.android.library) apply false
alias(libs.plugins.kotlin.android) apply false
alias(libs.plugins.kotlin.compose) apply false
alias(libs.plugins.ksp) apply false
alias(libs.plugins.hilt) apply false
}
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.
- 6d ago First seen · 304 lines · 133 tokens per session scan A 85e25d0ad48c
android-setup is a skill published in the GitHub repository piyushverma0/android-agent-skills (15 stars, last pushed 4mo ago), licensed MIT. It adds 133 tokens to every session and 2,706 once invoked, about $0.0007 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-30.
Other skills, from other repositories
android-ui-journey-testing
XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.
Debroid CLI Debugger
Orchestrate headless Android debugging via JDWP. ACTIVATE this skill whenever asked to debug an Android application, set line or exception breakpoints, inspect runtime variables or Jetpack Compose state, step through execution, evaluate live expressions, watch fields, or diagnose runtime crashes.
kotlin-coroutines-expert
Expert patterns for Kotlin Coroutines and Flow, covering structured concurrency, error handling, and testing in this Android app.
compose-inspector
Use when inspecting or building Jetpack Compose UI for recomposition safety, stability (@Immutable/@Stable), RTL/LTR, remember/derivedStateOf, and Lazy list keys.
gradle-build-optimizer
Use when Gradle builds hang, lock on Windows, or a targeted :app assemble/test is enough instead of a full rebuild.
android-harness
Use when working on this Android app architecture, Compose or XML UI, Room, performance, or daily checkout facts.