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 TalissonVitorino/kmp-ios-skills --skill mobile-testinggit clone --depth 1 https://github.com/TalissonVitorino/kmp-ios-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/talissonvitorino/kmp-ios-skills/mobile-testing)<a href="https://agentmods.dev/skills/talissonvitorino/kmp-ios-skills/mobile-testing"><img src="https://agentmods.dev/badge/skills/talissonvitorino/kmp-ios-skills/mobile-testing/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/talissonvitorino/kmp-ios-skills/mobile-testing"><img src="https://agentmods.dev/badge/skills/talissonvitorino/kmp-ios-skills/mobile-testing.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.00102 | $0.01501 |
| Opus 5 | $0.00051 | $0.00750 |
| Sonnet 5 | $0.00020 | $0.00300 |
| Haiku 4.5 | $0.00010 | $0.00150 |
Grade A, and why
mobile-testing 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile Testing Patterns
Test Dependencies
// build.gradle.kts
dependencies {
testImplementation(platform("org.junit:junit-bom:6.1.3")) // JUnit 6 / Jupiter 6 — requires Java 17+
testImplementation("org.junit.jupiter:junit-jupiter")
testRuntimeOnly("org.junit.platform:junit-platform-launcher") // mandatory since Gradle 9
testImplementation("io.mockk:mockk:1.14.11")
testImplementation("app.cash.turbine:turbine:1.2.1")
testImplementation("org.jetbrains.kotlinx:kotlinx-coroutines-test:1.11.0")
testImplementation("io.kotest:kotest-assertions-core:6.2.4")
androidTestImplementation(platform("androidx.compose:compose-bom:2026.08.00"))
androidTestImplementation("androidx.compose.ui:ui-test-junit4")
debugImplementation("androidx.compose.ui:ui-test-manifest")
}
// Without useJUnitPlatform() the Jupiter tests are never discovered — the task
// reports success with zero tests. This form works in JVM, KMP and AGP modules:
tasks.withType<Test>().configureEach { useJUnitPlatform() }
androidTestImplementationdoes not extendimplementation, so the Compose BOM must be repeated there;debugImplementationdoes extend it, soui-test-manifestinherits the version.android { testOptions { unitTests.all { it.useJUnitPlatform() } } }still works undercom.android.application/com.android.library. AGP 9 forbids those plugins alongsideorg.jetbrains.kotlin.multiplatform, and the replacementcom.android.kotlin.multiplatform.libraryplugin has notestOptionsDSL — KMP modules need thetasks.withType<Test>form.- Jupiter and MockK are JVM-only (MockK publishes a
jvmvariant and nothing else) — declare them injvmTest/androidUnitTestonly.kotlin("test"), Turbine,kotlinx-coroutines-testandkotest-assertions-coreare all published for every KMP target, so they belong incommonTest.
ViewModel Testing
viewModelScope dispatches to Dispatchers.Main — replace it in unit tests or every launch crashes. Use a JUnit 5 extension:
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 · 135 lines · 102 tokens per session scan A 096e206c46c0
mobile-testing is a skill published in the GitHub repository TalissonVitorino/kmp-ios-skills (12 stars, last pushed 16d ago), licensed MIT. It adds 102 tokens to every session and 1,501 once invoked, about $0.0005 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
cmp-qa-prep
Bring up the E2E harness for a Kotlin/Compose Multiplatform app — boot the Android emulator, install the debug build, run the Maestro smoke — or, simpler, run the verify lane, which does all three itself. Use this when the user wants to run E2E/device tests on their CMP/KMP app, "prep my KMP test environment", "smoke…
cmp-test
Generate a regression test suite for a Compose Multiplatform app by OBSERVING it — read the running app's semantics tree as JSON via the cmp-inspector MCP (testTags, text, clickables, bounds, nav state), derive a test plan from what actually rendered, and write the tests into the app's shipped harness (Maestro flows…
argent-test-ui-flow
Autonomously test an app UI (iOS or Android) by running interact-screenshot-verify loops using argent MCP tools. Use when testing UI flows, verifying login works, testing navigation, running end-to-end UI test scenarios, manual QA steps, visible UI changes, or visual behavior.
mobile-automation
Control Android and iOS devices, emulators and simulators — launch apps, tap, swipe, type, take screenshots, read the accessibility tree. Use when a task involves a mobile device or app, mobile UI testing, or reproducing a bug on a phone.
argent-create-flow
Create, record, edit, replay, or repair reusable Argent flow YAML files. Use when the user asks to record or replay a repeatable device path, set up profiling or an A/B comparison, or invoke the authoring engine behind argent-qa-flows. Also use before repeating three or more interactions. For one-off UI checks…
roborazzi
Use when working with Roborazzi screenshot tests on Android/JVM — setting up the Roborazzi Gradle plugin, running record/compare/verify tasks, writing tests with captureRoboImage or RoborazziRule, Compose Preview screenshot testing (ComposablePreviewScanner), Compose Multiplatform (iOS/desktop) screenshots, AI-powered…