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 testing-coroutines-with-runtestgit 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/testing-coroutines-with-runtest)<a href="https://agentmods.dev/skills/skydoves/android-testing-skills/testing-coroutines-with-runtest"><img src="https://agentmods.dev/badge/skills/skydoves/android-testing-skills/testing-coroutines-with-runtest/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/testing-coroutines-with-runtest"><img src="https://agentmods.dev/badge/skills/skydoves/android-testing-skills/testing-coroutines-with-runtest.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.00172 | $0.05062 |
| Opus 5 | $0.00086 | $0.02531 |
| Sonnet 5 | $0.00034 | $0.01012 |
| Haiku 4.5 | $0.00017 | $0.00506 |
Grade A, and why
testing-coroutines-with-runtest 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 10d 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 — 379 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Coroutines With runTest — Virtual Time Without Wall Clock
runTest is the only correct entry point for testing suspend functions and viewModelScope-backed code on the JVM. This skill nails down the TestScope contract, the two TestDispatcher flavors, the shared TestCoroutineScheduler virtual clock, and the MainDispatcherRule plumbing that keeps Dispatchers.setMain from leaking between tests. Flow-specific assertions live in ../testing-flows-with-turbine/SKILL.md.
When to use this skill
- The class under test exposes a
suspend funor launches intoviewModelScope/lifecycleScope. - The developer reaches for
runBlocking { … }and the test hangs, or a 10-minutedelaymakes the test slow. - A ViewModel emits
Loading -> Successfrom a coroutine and the test needs to assert each intermediate state. - The build emits the deprecation
runBlockingTest is deprecated. Use runTestorrunTest(... dispatchTimeoutMs = ...)errors. - The test fails with
IllegalStateException: Module with the Main dispatcher is missingbecauseviewModelScoperouted work throughDispatchers.Main. - The developer needs to advance virtual time (
advanceTimeBy(5.seconds),advanceUntilIdle()) to trigger a timeout / retry / debounce.
When NOT to use this skill
- The test asserts
Flowemissions across time. Use../testing-flows-with-turbine/SKILL.md(Turbine handles cancellation, hot vs cold,awaitItem/awaitComplete). - The test exercises Compose's
MainTestClockrather thankotlinx.coroutines.test. Use../../../compose/synchronization/controlling-the-test-clock/SKILL.md. - The test runs on an emulator/device through AndroidJUnit4. JUnit4 setup itself is
../../runner/configuring-junit4-on-android/SKILL.md.
Prerequisites
- Gradle:
testImplementation("org.jetbrains.kotlinx:kotlinx-coroutines-test:1.10.x")(docs/CORPUS.md§G.1). MUST betestImplementationonly — neverimplementation. The library installsDispatchers.setMainplumbing that is unsafe to ship to production. @file:OptIn(ExperimentalCoroutinesApi::class)(or per-call) on test files.currentTime,advanceTimeBy,advanceUntilIdle,runCurrent, and the dispatcher constructors are still@ExperimentalCoroutinesApion 1.10.x (R5).- For ViewModel tests, an injected
CoroutineDispatcher(a "DispatcherProvider") so the SUT can route work onto the sameTestCoroutineSchedulerthe test body advances. Hard-codedDispatchers.IO/Dispatchers.Defaultwill NOT see virtual time. - For KMP libraries that compile to JS / wasm, use the single-expression form
fun foo() = runTest { … }so the platformTestResultis returned (R5; see "TestResult contract" below).
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.
- 10d ago First seen · 379 lines · 172 tokens per session scan A 4e26ba067ab6
testing-coroutines-with-runtest is a skill published in the GitHub repository skydoves/android-testing-skills (319 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 172 tokens to every session and 5,062 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
swift-testing-pro
Writes, reviews, and improves Swift Testing code using modern APIs and best practices. Use when reading, writing, or reviewing projects that use Swift Testing.
swift
Swift development: concurrency patterns, async/await, actors, testing with XCTest and Swift Testing framework.
modernize-tests
Modernize test suites to use modern Swift Testing features or migrate from XCTest.
swift-testing-expert
Expert guidance for Swift Testing: test structure, #expect/#require macros, traits and tags, parameterized tests, test plans, parallel execution, async waiting patterns, and XCTest migration. Use when writing new Swift tests, modernizing XCTest suites, debugging flaky tests, or improving test quality and…
guide-swift-testing
Swift Testing patterns — structs over classes, async confirmations, parameterized tests, exit tests, attachments, common agent mistakes. Use when writing, reviewing, or migrating Swift Testing code.
swift-testing
WHEN writing, running, or diagnosing Swift Testing suites, including migrating XCTest tests to them and a crashing or non-reporting test target under xcodebuild; NOT for authoring XCTest or XCUITest tests; returns macro-driven test patterns, the XCTest boundary, and the correct way to read xcodebuild results.