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/synchronizing-with-idlenpx skills add skydoves/android-testing-skills --skill synchronizing-with-idlegit 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/synchronizing-with-idle)<a href="https://agentmods.dev/skills/skydoves/android-testing-skills/synchronizing-with-idle"><img src="https://agentmods.dev/badge/skills/skydoves/android-testing-skills/synchronizing-with-idle.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.00218 | $0.05539 |
| Opus 5 | $0.00109 | $0.02769 |
| Sonnet 5 | $0.00044 | $0.01108 |
| Haiku 4.5 | $0.00022 | $0.00554 |
Grade A, and why
synchronizing-with-idle 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 — 337 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Synchronizing With Idle — Pick the Right Wait
A Compose test that waits on the wrong primitive is the #1 source of flakiness. This skill enumerates every idle/wait API on ComposeTestRule and ComposeUiTest, locks down what "idle" actually means, and gives a decision matrix for choosing among them. Animation-specific waits live in ../testing-animations-deterministically/SKILL.md; the underlying clock semantics live in ../controlling-the-test-clock/SKILL.md.
When to use this skill
- The test occasionally fails with "node not found" or "node count mismatch" but the production code is correct.
- The developer reaches for
Thread.sleep(2000)to wait for a screen, a snackbar, a navigation transition, or an IO-backed state. - A
ViewModelposts state from a coroutine and the test needs to wait until the UI reflects it. - The developer asks about
IdlingResource, the Espresso bridge,runOnIdlevsrunOnUiThread, or whetherrunWhenIdleis faster. - The developer mentions
waitUntil,waitUntilExactlyOneExists,waitUntilNodeCount,AndroidComposeUiTestTimeoutException, orIdlingPolicies.setMasterPolicyTimeout. - The developer reads or mutates state from the test thread (e.g.
state.firstVisibleItemIndex) and asks why it sometimes returns stale data.
When NOT to use this skill
- The condition is a paused-clock animation. Use
../testing-animations-deterministically/SKILL.mdandmainClock.advanceTimeUntil. - The mechanics of
MainTestClockitself (frames, rounding, dispatchers) are unclear. Read../controlling-the-test-clock/SKILL.mdfirst. - The test is failing because of test-tag/finder issues, not async timing. Use
../../debug/printing-the-semantics-tree/SKILL.mdand../../finders/finding-nodes-by-tag-text-content/SKILL.md. - Espresso interop is the actual question. Use
../../interop/testing-with-espresso-interop/SKILL.md(sibling skill, separate scope).
Prerequisites
androidx.compose.ui:ui-testandandroidx.compose.ui:ui-test-junit4(orrunComposeUiTest).- A
ComposeContestTestRulefromcreateComposeRule()(PREFERRED v2:androidx.compose.ui.test.junit4.v2.createComposeRule). - For experimental
waitUntilNodeCount/waitUntilExactlyOneExists/waitUntilAtLeastOneExists/waitUntilDoesNotExist:@OptIn(ExperimentalTestApi::class)on the test class or method.
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 · 337 lines · 218 tokens per session scan A e8de9f6ea093
synchronizing-with-idle is a skill published in the GitHub repository skydoves/android-testing-skills (318 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 218 tokens to every session and 5,539 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
通过 SoloPi 的机器可读 CLI 编译和执行 AI 验证计划，管理签名端侧 ExecuTorch 决策模型、持久设备池、无人值守任务、安卓设备、应用、动作、配置、用例步骤与交互录制、回放及性能历史、动态 Agent、批量与重复执行、性能监控、压力测试和证据。适用于需求/AC 到 Result Judge 三态结论、cloud/on-device 决策切换、模型发布门禁，以及 generation 租约的多设备 CI 执行。.
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…