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 running-instrumented-tests-with-androidjunit4git 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/running-instrumented-tests-with-androidjunit4)<a href="https://agentmods.dev/skills/skydoves/android-testing-skills/running-instrumented-tests-with-androidjunit4"><img src="https://agentmods.dev/badge/skills/skydoves/android-testing-skills/running-instrumented-tests-with-androidjunit4/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/running-instrumented-tests-with-androidjunit4"><img src="https://agentmods.dev/badge/skills/skydoves/android-testing-skills/running-instrumented-tests-with-androidjunit4.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00218 | $0.04559 |
| Opus 5 | $0.00109 | $0.02279 |
| Sonnet 5 | $0.00044 | $0.00912 |
| Haiku 4.5 | $0.00022 | $0.00456 |
Grade A, and why
running-instrumented-tests-with-androidjunit4 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 9d 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 — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Running Instrumented Tests with AndroidJUnit4 — Get the Runner Stack Right
Instrumentation tests fail before any assertion runs when the runner stack is misconfigured: a deprecated AndroidJUnit4 import, the orchestrator on androidTestImplementation instead of androidTestUtil, the deprecated androidx.test.InstrumentationRegistry instead of androidx.test.platform.app.InstrumentationRegistry. This skill encodes the exact dependency matrix, the runner Gradle config, and the supporting annotations and rules.
When to use this skill
- The IDE flags
androidx.test.runner.AndroidJUnit4as@Deprecated, or the test compiles but emits the deprecation warning. am instrumentreturnsINSTRUMENTATION_FAILED: <pkg>/androidx.test.runner.AndroidJUnitRunnerorTest runner not found.- Test Orchestrator is configured in Gradle but tests still share a single instrumentation process (orchestrator silently disabled).
- The user passes
-e size small/-e package com.fooviaam instrumentand the test ignores it —RunnerArgsis unwired. - A test needs
ACCESS_FINE_LOCATION/RECORD_AUDIOetc. and the user is hand-rolling permission grants fromadb. - The user wants to skip a test below API 26 and is searching for the annotation.
When NOT to use this skill
- The user is launching an
Activityor driving lifecycle — see../../scenarios/launching-activities-with-activityscenario/SKILL.md. - The user is interacting with Views — see
../../espresso/writing-espresso-tests/SKILL.md. - The user is driving system UI or another app — see
../../uiautomator/cross-app-tests-with-uiautomator/SKILL.md. - The user runs JVM (Robolectric / pure JUnit) tests — see
../../../jvm-tests/runner/configuring-junit4-on-android/SKILL.md. - The user is choosing what to test in the first place — see
../../../fundamentals/strategies/applying-testing-strategies/SKILL.md.
Prerequisites
- Android Gradle Plugin module (
com.android.applicationorcom.android.library). - A
src/androidTest/source set on disk (./gradlew :module:connectedDebugAndroidTestshould resolve). - An emulator or physical device (or Firebase Test Lab / managed devices) — the runner cannot execute on the JVM.
- JUnit 4 on the test classpath (
junit:junit:4.13.2); JUnit 5 requires a Vintage engine bridge and is out of scope.
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.
- 9d ago First seen · 303 lines · 218 tokens per session scan A e9f1d3d6dd46
running-instrumented-tests-with-androidjunit4 is a skill published in the GitHub repository skydoves/android-testing-skills (319 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 218 tokens to every session and 4,559 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
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.
agent-device
Automates Apple-platform apps (iOS, tvOS, macOS), Android devices, and Amazon Vega OS TV apps in Vega Virtual Devices. Use when navigating apps, taking snapshots/screenshots where supported, driving TV remotes, tapping, typing, scrolling, extracting UI info, collecting evidence, or planning agent-device CLI commands.
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
EAS service (paid). 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…