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 krutikJain/android-agent-skills --skill android-gradle-build-performancegit clone --depth 1 https://github.com/krutikJain/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/krutikjain/android-agent-skills/android-gradle-build-performance)<a href="https://agentmods.dev/skills/krutikjain/android-agent-skills/android-gradle-build-performance"><img src="https://agentmods.dev/badge/skills/krutikjain/android-agent-skills/android-gradle-build-performance/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/skills/krutikjain/android-agent-skills/android-gradle-build-performance"><img src="https://agentmods.dev/badge/skills/krutikjain/android-agent-skills/android-gradle-build-performance.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.00027 | $0.01016 |
| Opus 5.5 | $0.00011 | $0.00406 |
| Sonnet 5.5 | $0.00005 | $0.00203 |
| Haiku 4.5 | $0.00003 | $0.00102 |
Grade A, and why
android-gradle-build-performance 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Android Gradle Build Performance
When To Use
- Use this skill when the request is about: android gradle build performance, configuration cache android build, ksp vs kapt android.
- Primary outcome: Diagnose and improve Android and Gradle build performance with scans, cache checks, and bottleneck audits.
- Use this skill when the problem is build speed, task churn, cache misses, or CI wall time rather than build-logic structure.
- Read
references/patterns.mdwhen you need the measurement ladder or the most common Gradle performance smells. - Read
references/scenarios.mdfor audit-first entry points on the example projects. - Handoff skills when the scope expands:
android-gradle-build-logicandroid-ci-cd-release-playstore
Workflow
- Identify whether the problem is local developer feedback time, CI build duration, or both.
- Measure one build path at a time with
--profile,--scan, configuration-cache diagnostics, or the bundled audit script before proposing a fix. - Check
gradle.properties, plugin wiring, dependency declarations, task registration style, and module conventions for common performance smells. - Apply one high-confidence optimization at a time, then compare before and after behavior instead of stacking changes.
- Hand off structural Gradle refactors or release-pipeline changes once the performance bottleneck is isolated.
Guardrails
- Do not recommend broad rewrites when a single cache, plugin, or dependency pattern is the real bottleneck.
- Separate measurement from speculation; call out what was observed vs inferred.
- Prefer KSP, configuration cache, and lazy task configuration when the toolchain supports them.
- Treat dynamic dependency versions, changing modules, and eager task creation as performance regressions unless there is a deliberate reason.
- Keep CI guidance reproducible on the example projects before suggesting org-wide rollout.
Anti-Patterns
- Turning on every Gradle flag without checking compatibility or failures.
- Blaming AGP upgrades for slow builds without measuring task hot spots.
- Mixing build-logic architecture advice with build-time diagnosis in one pass.
- Using dynamic dependency versions that force repeated resolution work.
What ships with it
6 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.
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 · 77 lines · 27 tokens per session scan A e7f91fc3ed9b
android-gradle-build-performance is a skill published in the GitHub repository krutikJain/android-agent-skills (14 stars, last pushed 7mo ago), licensed MIT. It adds 27 tokens to every session and 1,016 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
dart-tooling
Dart static analysis, linting, formatting, and code-generation standards. Use only for analysisoptions.yaml, buildrunner, dart format, DCM, lefthook, or analyze/format CI failures; defer Dart language, null-safety, Flutter tests, and generic CI questions.
flutter-cicd
Set up CI/CD pipelines for Flutter apps. Use when configuring automated testing, build, or deployment workflows with GitHub Actions or Fastlane.
compose-project
Owns project and build-level work for Compose and Compose Multiplatform apps: bootstrapping a new project, adopting the kit in an existing project, adding or extracting a module, convention plugins in build-logic, the version catalog, and CI plus agent hooks. Use when starting a Compose Multiplatform app, adding a…
github-workflows
Manage and automate Android CI/CD workflows using GitHub Actions in this repository.
mood-tracker
A simple mood tracking skill that stores your daily mood and comments. Use this when the user wants to log their mood, track how they feel, or see their mood history.
kitchen-adventure
Act as a dungeon master for a text-based adventure set in a world where everyone is a sentient kitchen appliance. Trigger when user says "start kitchen adventure".