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/skydoves/android-testing-skills/developing-with-compose-previewsnpx skills add skydoves/android-testing-skills --skill developing-with-compose-previewsgit clone --depth 1 https://github.com/skydoves/android-testing-skillsWhat 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 | $0.00216 | $0.03602 |
| Opus 5 | $0.00108 | $0.01801 |
| Sonnet 5 | $0.00043 | $0.00720 |
| Haiku 4.5 | $0.00022 | $0.00360 |
Grade A, and why
developing-with-compose-previews 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 3d 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developing With Compose Previews — Preview-Driven Development
@Preview is the cheapest verification loop in Compose: edit, see the render in ~1 s, no build/install/navigate cycle. It only pays off if composables are structured so previews stay alive — hoisted state, no ViewModel in the signature, realistic sample data. This skill encodes that structure and the anti-patterns that cause teams to abandon previews. For taking those previews as on-device screenshots in CI, see ../capturing-preview-screenshots-in-ci/SKILL.md.
When to use this skill
- A
@Preview"fails to render" or crashes because the composable takes aViewModel, repository, orContext-bound dependency. - The user wants to see loading / empty / error / overflow-text / RTL states without running the app —
@PreviewParameterterritory. - A composable loads images with Coil/Glide and the preview shows nothing — needs
LocalInspectionMode. - The user asks "how should I structure Compose previews so they don't keep breaking" or mentions "preview-driven development".
- Previews exist but drift out of date / show the "out of date" banner constantly and the team is about to delete them.
When NOT to use this skill
- The user wants to capture previews as screenshots on a device or in CI (HotSwan
captureAllPreviews, GitHub Pages catalog) — use../capturing-preview-screenshots-in-ci/SKILL.md. - The user wants pixel-diff golden-image regression tests (Paparazzi / Roborazzi) — that is a different tool; see
../capturing-preview-screenshots-in-ci/SKILL.mdfor where it fits relative to device rendering. - The user is writing behavioral UI tests (
ComposeTestRule, finders, assertions) — start at../../setup/configuring-test-dependencies/SKILL.mdand../../finders/finding-nodes-by-tag-text-content/SKILL.md.
Prerequisites
androidx.compose.ui:ui-tooling-previewon the main classpath (provides@Preview,@PreviewParameter,PreviewParameterProvider; seecompose/ui/ui-tooling-preview/), plusdebugImplementation("androidx.compose.ui:ui-tooling")so Android Studio can render.LocalInspectionModeships inandroidx.compose.ui:ui(compose/ui/ui/.../platform/InspectionMode.kt—staticCompositionLocalOf { false }), no extra dependency.- A Compose-enabled module (the
org.jetbrains.kotlin.plugin.composeplugin orbuildFeatures.compose = true).
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.
- 3d ago First seen · 226 lines · 216 tokens per session scan A 1dbbb43d7d17
developing-with-compose-previews is a skill published in the GitHub repository skydoves/android-testing-skills (313 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 216 tokens to every session and 3,602 once invoked, about $0.0011 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
edge-to-edge
Use this skill to migrate your Jetpack Compose app to add adaptive edge-to-edge support and troubleshoot common issues. Use this skill to fix UI components (like buttons or lists) that are obscured by or overlapping with the navigation bar or status bar, fix IME insets, and fix system bar legibility.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
flutter-fix-layout-issues
Fixes Flutter layout errors (overflows, unbounded constraints) using Dart and Flutter MCP tools. Use when addressing "RenderFlex overflowed", "Vertical viewport was given unbounded height", or similar layout issues.
referral-program
When the user wants to design, launch, or optimize an in-app referral / invite / share-to-earn program — including reward structure, mechanics, fraud prevention, deep link setup, and viral coefficient measurement. Use when the user mentions "referral program", "invite a friend", "refer and earn", "share to earn"…
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.
ios-hig-design
Design native iOS interfaces following Apple Human Interface Guidelines. Use when the user mentions "iPhone app", "iPad layout", "SwiftUI", "UIKit", "Dynamic Island", "safe areas", "HIG compliance", "SF Symbols", "haptic feedback", "iOS accessibility", "make my app feel native", or "follow Apple design guidelines".…