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 skydoves/android-testing-skills --skill structuring-a-compose-testgit clone --depth 1 https://github.com/skydoves/android-testing-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/skydoves/android-testing-skills/structuring-a-compose-test)<a href="https://agentmods.dev/skills/skydoves/android-testing-skills/structuring-a-compose-test"><img src="https://agentmods.dev/badge/skills/skydoves/android-testing-skills/structuring-a-compose-test/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/android-testing-skills/structuring-a-compose-test"><img src="https://agentmods.dev/badge/skills/skydoves/android-testing-skills/structuring-a-compose-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high YARA Match · line 3 YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).Fix: Remove offensive tool references and exploit code. Legitimate agent skills should not contain penetration testing tools, exploit frameworks, or reconnaissance utilities.
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.00219 | $0.03574 |
| Opus 5.5 | $0.00088 | $0.01430 |
| Sonnet 5.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 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 — 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.
- 1mo 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 (337 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 219 tokens to every session and 3,574 once invoked, about $0.0009 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
android_ui_verification
Automated end-to-end UI testing and verification on an Android Emulator using ADB.
solopi-ai
A command-line framework for testing Android apps and devices with SoloPi, including on-device or cloud AI decision models. It manages devices, test cases, recorded interactions, replays, performance history, and evidence.
ios-simulator
Verify and debug native, React Native, Expo, or Flutter apps on an iOS Simulator with agent-device. Use when an agent needs to launch an app, inspect its live UI, tap, type, scroll, validate a code change, collect failure evidence, or reproduce a workflow on an iPhone or iPad Simulator.
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.
eas-simulator
Run and control a user's app on a remote iOS/Android simulator hosted on EAS cloud. Read before running any eas simulator: commands - it has the current syntax for this experimental API. Use whenever the user needs a simulator they can't run locally - 'run my app on a cloud simulator', 'use eas simulator to…
flutter-add-widget-test
Implement a component-level test using WidgetTester to verify UI rendering and user interactions (tapping, scrolling, entering text). Use when validating that a specific widget displays correct data and responds to events as expected.