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/controlling-the-test-clocknpx skills add skydoves/android-testing-skills --skill controlling-the-test-clockgit 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/controlling-the-test-clock)<a href="https://agentmods.dev/skills/skydoves/android-testing-skills/controlling-the-test-clock"><img src="https://agentmods.dev/badge/skills/skydoves/android-testing-skills/controlling-the-test-clock.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.00193 | $0.04064 |
| Opus 5 | $0.00097 | $0.02032 |
| Sonnet 5 | $0.00039 | $0.00813 |
| Haiku 4.5 | $0.00019 | $0.00406 |
Grade A, and why
controlling-the-test-clock 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Controlling the Test Clock — Frames, Time, and the Recomposer
MainTestClock is the only knob that drives recomposition, animations, and LaunchedEffects in a Compose test. This skill explains its surface, the 16 ms frame model behind it, and how autoAdvance flips the test from "framework drives the clock" to "the test drives the clock". The animation recipe and the idle/wait recipe live in sibling skills — this one establishes the mechanics they both depend on.
When to use this skill
- The developer asks what
mainClock.advanceTimeBy(...)actually does, why it rounds up, or why the animation seems off by one frame. - The developer is migrating from
androidx.compose.ui.test.junit4.createComposeRule(v1) toandroidx.compose.ui.test.junit4.v2.createComposeRule(v2) and tests now require an explicitmainClock.runCurrent()oradvanceTimeBy(0). - The developer mentions
MainTestClock,TestCoroutineScheduler,TestMonotonicFrameClock,ComposeTimeoutException,advanceTimeUntil, or "test clock vs wall clock". - The developer is writing a test that needs a particular frame count and is unsure whether
advanceTimeBy(5)produces zero, one, or many frames. - The developer asks why the animation's
playTimeis still0after one frame.
When NOT to use this skill
- The goal is a deterministic animation test (the
autoAdvance = falserecipe). Use../testing-animations-deterministically/SKILL.md. - The goal is to wait on
IdlingResources, async work, or "the UI is settled". Use../synchronizing-with-idle/SKILL.md. - The goal is the higher-level test structure (rule wiring,
setContent, JUnit lifecycle). Use../../patterns/structuring-a-compose-test/SKILL.md. - The goal is choosing between
createComposeRuleandrunComposeUiTest. Use../../setup/choosing-test-rule-vs-runtest/SKILL.md.
Prerequisites
androidx.compose.ui:ui-testandandroidx.compose.ui:ui-test-junit4(or the JUnit-lessrunComposeUiTest) on the test source set.- A
ComposeContentTestRulefromcreateComposeRule()or aComposeUiTestreceiver fromrunComposeUiTest { … }. - PREFERRED: the v2 entry points (
androidx.compose.ui.test.junit4.v2.createComposeRule,androidx.compose.ui.test.v2.runComposeUiTest). The v1 forms are@Deprecated(level = WARNING)(skydoves hot take #6).
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 · 249 lines · 193 tokens per session scan A 6099eb9216d1
controlling-the-test-clock is a skill published in the GitHub repository skydoves/android-testing-skills (318 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 193 tokens to every session and 4,064 once invoked, about $0.0010 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
orca-emulator-android
Control an Android emulator / device from inside Orca using the orca CLI. Use for listing/booting AVDs, taps, swipes, typing, hardware buttons (incl. Back and Recents), rotation, app install/launch, runtime permissions, the accessibility tree, and logcat — driving a real adb-connected device or emulator.…
android-tombstone-symbolication
Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app…
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.
winapp-maui
Package and sign .NET MAUI Windows apps with winapp, resolving the resizetizer manifest dependency. Use when packaging or signing a .NET MAUI Windows app, building a MAUI MSIX or signed unpackaged build in CI, or fixing 'manifest contains unresolved placeholders ($placeholder$)' errors from winapp package.
apple-search-ads
When the user wants to set up, optimize, or scale Apple Search Ads (ASA) campaigns — including keyword bidding, match types, campaign structure, Creative Product Sets, CPP routing, and ROAS optimization. Use when the user mentions "Apple Search Ads", "ASA", "Search Ads", "Search tab ads", "Today tab ads", "CPT"…
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.