Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/skydoves/compose-performance-skillsnpx agentmods add skills/skydoves/compose-performance-skills/testing-compose-in-release-modeWrote 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/skydoves/compose-performance-skills/testing-compose-in-release-mode)<a href="https://agentmods.dev/skills/skydoves/compose-performance-skills/testing-compose-in-release-mode"><img src="https://agentmods.dev/badge/skills/skydoves/compose-performance-skills/testing-compose-in-release-mode/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/skydoves/compose-performance-skills/testing-compose-in-release-mode"><img src="https://agentmods.dev/badge/skills/skydoves/compose-performance-skills/testing-compose-in-release-mode.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00189 | $0.03754 |
| Opus 5.5 | $0.00076 | $0.01502 |
| Sonnet 5.5 | $0.00038 | $0.00751 |
| Haiku 4.5 | $0.00019 | $0.00375 |
Grade A, and why
testing-compose-in-release-mode 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 — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Compose in Release Mode — Debug Builds Lie About Performance
Compose ships unbundled — its UI runtime is loaded from app code, runs interpreted in debug, and the Live Literals plugin turns every constant into a getter. Debug recomposition counts, debug startup numbers, and debug compiler reports are not what users experience. This skill teaches Claude how to set up a release-with-symbols build for honest measurement before any perf claim is made.
When to use this skill
- The developer reports a perf number ("startup is 1.4s", "this composable recomposes 50 times per scroll") that came from a debug build, Layout Inspector against debug, or
CompilationMode.None. - The developer is about to file a perf bug, open a regression report, or post benchmark numbers in a PR.
- A CI perf gate is being designed (Macrobenchmark, baseline-profile diff, frame-timing budget).
- The developer asks "why are my benchmark numbers so much worse than what I see on Play Store?".
- Compose Compiler reports are about to be read — they MUST come from the release output directory or every conclusion is suspect.
When NOT to use this skill
- Feature development before perf is in scope — debug iteration speed is fine while functionality is being built.
- Behavior testing (correctness, integration, instrumentation tests for screens) — that is separate from perf testing and stays in debug.
- Build configuration of R8 itself — see
../../build/configuring-r8-for-compose/SKILL.md. - Generating a Baseline Profile from a benchmark run — see
../generating-baseline-profiles/SKILL.md. - Reading individual lines of a Compose Compiler report — see
../../stability/diagnosing-compose-stability/SKILL.md.
Prerequisites
- A working Android project with a Compose UI.
- A release signing config. A debug-signed release-mode build is acceptable for measurement (use a
signingConfig signingConfigs.debugon the release type), but unsigned release builds will not install. - Kotlin 2.0+ with the
org.jetbrains.kotlin.plugin.composeGradle plugin. - A real physical device to run on. Emulator and Cuttlefish numbers are not interchangeable with on-device numbers.
- Familiarity with Macrobenchmark and Baseline Profiles helps but is not required.
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 · 266 lines · 189 tokens per session scan A 4c8a5f204388
testing-compose-in-release-mode is a skill published in the GitHub repository skydoves/compose-performance-skills (520 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 189 tokens to every session and 3,754 once invoked, about $0.0008 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-30.
Other skills, from other repositories
claude-android-ninja
Build and migrate Android apps with Kotlin, Jetpack Compose, MVVM, Hilt, Room 3 (KSP, SQLiteDriver, Flow/suspend DAOs), Navigation3, and multi-module Gradle. Use for new projects or modules, Compose screens and ViewModels, Room 3 and RemoteMediator, API 37 / targetSdk migration, Play Integrity client wiring…
rebrand
Rebrand a fresh clone of android-clean-template into a new app. Asks for the app name, application id, and the sample-feature, login and networking decisions, then executes docs/CLONECHECKLIST.md end to end. Use on a fresh un-rebranded clone (application id still com.mkchtv.cleantemplate) or when the user asks to set…
sceneview
Build 3D and AR apps with the SceneView SDK in Jetpack Compose, SwiftUI (iOS/macOS/visionOS via SceneViewSwift), Web (Filament.js), Flutter and React Native. Use whenever the user asks for "3D in Compose", "AR with ARCore in Compose", a model viewer, or any cross-platform 3D/AR app where the dependency is…
sceneview-ios
Build 3D and AR apps on Apple platforms (iOS, macOS, visionOS) with SceneViewSwift — the SwiftUI wrapper around RealityKit. Use whenever the user asks for "3D in SwiftUI", "AR with ARKit in SwiftUI", a model viewer for iOS, or any Apple-platform 3D/AR app where the dependency is the SceneViewSwift Swift Package from…
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.