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/structuring-a-compose-testnpx skills add skydoves/android-testing-skills --skill structuring-a-compose-testgit 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.00219 | $0.03574 |
| Opus 5 | $0.00110 | $0.01787 |
| Sonnet 5 | $0.00044 | $0.00715 |
| Haiku 4.5 | $0.00022 | $0.00357 |
Grade A, and why
structuring-a-compose-test 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 2d 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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Structuring a Compose Test — The androidx-Canonical Class Skeleton
Compose tests fail or rot because their structure is wrong, not because the assertions are wrong. State that lives inside setContent { } cannot be driven from the test thread; setContent called inside @Before becomes a hidden race; combining @get:Rule with runComposeUiTest { } creates two competing test environments. This skill encodes the exact class skeleton used by androidx.compose.material3 and androidx.compose.foundation so the developer's tests behave the same way.
When to use this skill
- The developer is creating a new
*Test.ktand asks where to put state, the rule, andsetContent. - A test compiles but cannot mutate state mid-test ("how do I flip the checkbox after the first assertion?").
- The developer pasted
setContentinto@Beforeand the test is now flaky or will not start. - A reviewer flags a test for declaring state inside
setContent { }. - The developer mixed
@get:Rule createComposeRule()andrunComposeUiTest { }and gets confusing failures.
When NOT to use this skill
- The developer is choosing which entry point to use (rule vs.
runComposeUiTest); use../../setup/choosing-test-rule-vs-runtest/SKILL.md. - The build cannot resolve
createComposeRule; use../../setup/configuring-test-dependencies/SKILL.md. - The decision is host (Robolectric) vs. device (instrumentation); use
../../setup/setting-up-host-vs-device-tests/SKILL.md. - The test is specifically for a
LazyColumn/LazyRow; layer../testing-lazy-lists/SKILL.mdon top of this skeleton.
Prerequisites
androidx.compose.ui:ui-test-junit4onandroidTestImplementation,androidx.compose.ui:ui-test-manifestondebugImplementation. See../../setup/configuring-test-dependencies/SKILL.md.- Default activity is
androidx.activity.ComponentActivity(provided byui-test-manifest). For a custom Activity theandroidTestsource set MUST declare it inAndroidManifest.xml. - Kotlin source set:
src/androidTest/kotlin/...(instrumentation) orsrc/test/kotlin/...(Robolectric host).
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.
- 2d ago First seen · 273 lines · 219 tokens per session scan A 5aa1d77c63c0
structuring-a-compose-test is a skill published in the GitHub repository skydoves/android-testing-skills (313 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 219 tokens to every session and 3,574 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.