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/configuring-junit4-on-androidnpx skills add skydoves/android-testing-skills --skill configuring-junit4-on-androidgit 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/configuring-junit4-on-android)<a href="https://agentmods.dev/skills/skydoves/android-testing-skills/configuring-junit4-on-android"><img src="https://agentmods.dev/badge/skills/skydoves/android-testing-skills/configuring-junit4-on-android.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.1 | $0.00227 | $0.05018 |
| Opus 5 | $0.00113 | $0.02509 |
| Sonnet 5 | $0.00045 | $0.01004 |
| Haiku 4.5 | $0.00023 | $0.00502 |
Grade A, and why
configuring-junit4-on-android 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 6d 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 — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configuring JUnit4 on Android — The Right Runner, Registry, and Matrix
Almost every "test suite is misconfigured" report boils down to one of three root causes: the wrong AndroidJUnit4 is imported, the wrong InstrumentationRegistry is imported, or the size-annotation / dispatcher plumbing is missing. This skill encodes the exact Gradle matrix from androidx.test:core 1.7.0 onward, the canonical FQCNs, and the minimal MainDispatcherRule pattern that androidx itself ships in testutils-ktx.
When to use this skill
- The user reports
Cannot resolve symbol AndroidJUnit4,AndroidJUnit4 is deprecated, or asks "whichAndroidJUnit4should I import". - The user reports
IllegalStateException: No instrumentation registeredfromInstrumentationRegistry.getInstrumentation()in a unit test, or asks whyInstrumentationRegistryis crossed out. - The user wants Truth subjects (
IntentSubject,BundleSubject,LocationSubject,ParcelableSubject) but does not know which artifact ships them. - The user wants
am instrument -e size smallto filter tests and asks how to wire@SmallTest/@MediumTest/@LargeTest. - The user is writing a
ViewModel/ coroutine test and needs the canonicalMainDispatcherRuletemplate.
When NOT to use this skill
- The user is wiring Mockito mocks — use
../../mocking/mocking-with-mockito/SKILL.md. - The user is wiring MockK mocks — use
../../mocking/mocking-with-mockk/SKILL.md. - The user is configuring
runTest { … }orTurbine— use../../coroutines/testing-coroutines-with-runtest/SKILL.mdor../../coroutines/testing-flows-with-turbine/SKILL.md. - The user is configuring Robolectric specifically (SDK matrix, resources,
@Config) — use../../robolectric/using-robolectric-correctly/SKILL.md. - The user is running tests on a device with
am instrument— use../../../instrumentation/runner/running-instrumented-tests-with-androidjunit4/SKILL.md. - The user is choosing between fakes and mocks — use
../../../fundamentals/doubles/picking-test-doubles/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.
- 6d ago First seen · 326 lines · 227 tokens per session scan A 7bedc5c27296
configuring-junit4-on-android is a skill published in the GitHub repository skydoves/android-testing-skills (318 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 227 tokens to every session and 5,018 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
run-helix-tests
Submit and monitor .NET MAUI unit tests on Helix infrastructure. Supports running XAML, Resizetizer, Core, Essentials, and other unit test projects on distributed Helix queues.
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
nunit-testing
Use when writing or modifying tests in NUnit's own test projects, or when making a behavioral change to production code that needs test coverage. Covers test structure, attribute choice, helper visibility, platform guards, and which test projects are real.
detect-flaky-tests
Detects flaky Go tests by analyzing GitHub Actions workflow runs across the last 7 days and all PRs — covering both the run-tests job (unit/integration) and the e2e-test job (gVisor and microVM lanes). For each newly-detected flaky test or infra issue, opens a GitHub issue with full evidence and a draft fix PR. Does…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
add-go-test
Write or extend Go unit tests in this repo. Use when the user asks to add or update Go tests.