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-flows-with-turbinegit 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-flows-with-turbine)<a href="https://agentmods.dev/skills/skydoves/android-testing-skills/testing-flows-with-turbine"><img src="https://agentmods.dev/badge/skills/skydoves/android-testing-skills/testing-flows-with-turbine.svg" alt="Measured on agentmods" 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.00240 | $0.05551 |
| Opus 5 | $0.00120 | $0.02776 |
| Sonnet 5 | $0.00048 | $0.01110 |
| Haiku 4.5 | $0.00024 | $0.00555 |
Grade A, and why
testing-flows-with-turbine 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 8d 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 — 438 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Flows With Turbine — Assert Emissions Without toList Hangs
Turbine is the canonical way to assert Flow emissions one-at-a-time, with built-in cancellation that prevents hot flows (StateFlow, SharedFlow) from hanging the test. This skill covers flow.test, the ReceiveTurbine API, turbineScope for multi-flow tests, and when raw flow.toList() actually beats Turbine. The non-Flow coroutine plumbing is ../testing-coroutines-with-runtest/SKILL.md.
When to use this skill
- The class under test exposes a
StateFlow<UiState>orSharedFlow<Event>and the test must assert each emission. - A test hangs on
flow.toList()over aSharedFloworStateFlow— neither completes. - The developer wants to assert "no more emissions for a beat" or "the next event is an error", which
toList()cannot express. - Two flows must be observed concurrently (e.g.
uiStateplus a one-shoteventsflow) and asserted in interleaved order. - The build error is
TurbineAssertionError: Unconsumed events foundorExpected an item but found Complete/Error. - The developer mentions Turbine APIs:
awaitItem,awaitComplete,awaitError,expectMostRecentItem,skipItems,expectNoEvents,withTurbineTimeout,turbineScope,testIn.
When NOT to use this skill
- The test is about
runTest,TestScope,Dispatchers.setMain, or virtual time. Use../testing-coroutines-with-runtest/SKILL.mdfirst; Turbine sits on top ofrunTest. - The flow is cold and completes deterministically, and the assertion is "the full list equals X".
flow.toList()is shorter — see Decision matrix below. - The "flow" is actually Compose snapshot state. Read it via the test rule, not Turbine.
Prerequisites
- Gradle:
testImplementation("app.cash.turbine:turbine:1.x")(docs/CORPUS.md§G.1; R5). - Turbine multiplatform — JVM, Android, iOS, JS, Native, wasm. Apache 2.0, Square / Cash App.
- The surrounding test must be a
runTest { … }body (or anysuspendcontext).flow.test { }is itselfsuspend. - For multi-flow tests,
@OptIn(ExperimentalCoroutinesApi::class)becauseturbineScopeinteracts withTestScope.backgroundScope.
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.
- 8d ago First seen · 438 lines · 240 tokens per session scan A e1a418a26037
testing-flows-with-turbine is a skill published in the GitHub repository skydoves/android-testing-skills (318 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 240 tokens to every session and 5,551 once invoked, about $0.0012 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
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…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.
mobiai-ios-testing
Use when writing or running tests in an iOS project — unit tests, UI tests, snapshot tests, choosing the right framework.
testing-llm
LLM and AI testing patterns — mock responses, evaluation with DeepEval/RAGAS, structured output validation, and agentic test patterns (generator, healer, planner). Use when testing AI features, validating LLM outputs, or building evaluation pipelines.