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/organizing-test-source-setsnpx skills add skydoves/android-testing-skills --skill organizing-test-source-setsgit 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/organizing-test-source-sets)<a href="https://agentmods.dev/skills/skydoves/android-testing-skills/organizing-test-source-sets"><img src="https://agentmods.dev/badge/skills/skydoves/android-testing-skills/organizing-test-source-sets.svg" alt="Measured on agentmods" 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 | $0.00182 | $0.05073 |
| Opus 5 | $0.00091 | $0.02537 |
| Sonnet 5 | $0.00036 | $0.01015 |
| Haiku 4.5 | $0.00018 | $0.00507 |
Grade A, and why
organizing-test-source-sets 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 5d 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 — 397 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Organizing Test Source Sets — src/test/, src/androidTest/, and the KMP Split
Where a test file lives determines which JVM runs it, which dependencies it sees, and whether it ships in the test APK. Most modules need only src/test/ and src/androidTest/. Modules that share helpers between host and device tests historically used src/sharedTest/ (a Codelab convention, not Google-documented as such), which broke on AGP 7.2+ and pushed Compose itself to the KMP-style androidHostTest / androidDeviceTest split. This skill encodes the matrix so the agent can place a test file with confidence.
When to use this skill
- The user asks "where do I put my tests" or "src/test/ or src/androidTest/".
- The user asks "what's testImplementation vs androidTestImplementation vs debugImplementation".
- The user reports
Unresolved reference: createComposeRuleand the agent suspects the dependency is on the wrong configuration. - The user is migrating off
src/sharedTest/after AGP 7.2+ broke theirsourceSets { test.java.srcDir(...) }block. - The user mentions
androidHostTest/androidDeviceTestand asks how to set them up in a non-KMP module. - The user asks "why is my Robolectric test in
src/androidTest/" — it should be insrc/test/.
When NOT to use this skill
- The user is wiring Gradle dependencies for Compose test (
ui-test-junit4,ui-test-manifest) — use../../../compose/setup/configuring-test-dependencies/SKILL.md. - The user is choosing test scope (small/medium/big) — use
../../concepts/understanding-the-testing-pyramid/SKILL.md. - The user is configuring
AndroidJUnitRunneritself — use../../../instrumentation/runner/running-instrumented-tests-with-androidjunit4/SKILL.md. - The user is configuring a JUnit4 runner for JVM tests — use
../../../jvm-tests/runner/configuring-junit4-on-android/SKILL.md.
Prerequisites
- A module with the Android Gradle Plugin (
com.android.applicationorcom.android.library). - Familiarity with Gradle configuration names (
testImplementation,androidTestImplementation,debugImplementation). - An understanding that JVM tests run on the host's JVM and instrumented tests run on a device/emulator. (See
../../concepts/understanding-the-testing-pyramid/SKILL.md.)
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.
- 5d ago First seen · 397 lines · 182 tokens per session scan A d6f75aac6781
organizing-test-source-sets is a skill published in the GitHub repository skydoves/android-testing-skills (318 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 182 tokens to every session and 5,073 once invoked, about $0.0009 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
orca-emulator-android
Control an Android emulator / device from inside Orca using the orca CLI. Use for listing/booting AVDs, taps, swipes, typing, hardware buttons (incl. Back and Recents), rotation, app install/launch, runtime permissions, the accessibility tree, and logcat — driving a real adb-connected device or emulator.…
android-tombstone-symbolication
Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app…
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.
winapp-maui
Package and sign .NET MAUI Windows apps with winapp, resolving the resizetizer manifest dependency. Use when packaging or signing a .NET MAUI Windows app, building a MAUI MSIX or signed unpackaged build in CI, or fixing 'manifest contains unresolved placeholders ($placeholder$)' errors from winapp package.
apple-search-ads
When the user wants to set up, optimize, or scale Apple Search Ads (ASA) campaigns — including keyword bidding, match types, campaign structure, Creative Product Sets, CPP routing, and ROAS optimization. Use when the user mentions "Apple Search Ads", "ASA", "Search Ads", "Search tab ads", "Today tab ads", "CPT"…
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.