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 writing-tests-with-kotlin-testgit 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/writing-tests-with-kotlin-test)<a href="https://agentmods.dev/skills/skydoves/android-testing-skills/writing-tests-with-kotlin-test"><img src="https://agentmods.dev/badge/skills/skydoves/android-testing-skills/writing-tests-with-kotlin-test/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/writing-tests-with-kotlin-test"><img src="https://agentmods.dev/badge/skills/skydoves/android-testing-skills/writing-tests-with-kotlin-test.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.00285 | $0.04479 |
| Opus 5 | $0.00143 | $0.02240 |
| Sonnet 5 | $0.00057 | $0.00896 |
| Haiku 4.5 | $0.00028 | $0.00448 |
Grade A, and why
writing-tests-with-kotlin-test 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Tests With kotlin.test — One Assertion API Across Every Target
kotlin.test is Kotlin's own thin test library: framework-agnostic assert* functions plus @Test/@BeforeTest/@AfterTest annotations that typealias onto whatever runner is on the classpath (JUnit4, JUnit5, TestNG, the JS/Native runners). Write import kotlin.test.* once and the same test source compiles in commonTest, on the JVM, and on every Kotlin Multiplatform target. This skill covers the API surface, the @OnlyInputTypes compile-time guard, the Asserter extension point, and the Gradle wiring. It is the assertion layer; the runner layer for Android instrumentation is ../../../jvm-tests/runner/configuring-junit4-on-android/SKILL.md.
When to use this skill
- The module is Kotlin Multiplatform and tests live in
commonTest— JUnit'sorg.junit.*is not available there;kotlin.testis. - The user wants one assertion vocabulary that reads the same on JVM, Android, JS, and Native.
- The user reaches for
assertFailsWith<IllegalStateException> { … },assertContentEquals(...),assertIs<Foo>(value),assertContains(list, x),expect(3) { compute() }, or@BeforeTest/@AfterTest. - A JVM module has
testImplementation(kotlin("test"))and the test "runs on JUnit but I never added JUnit" — explaining the capability-based resolution. kotlin.test.assertEqualsfailures render as a plainAssertionErrorwith no diff, and the user wants the JUnit-style comparison failure back.
When NOT to use this skill
- The user wants rich fluent assertions (
assertThat(x).isEqualTo(...), soft assertions, collection matchers) — that is AssertJ / Google Truth / Kotest assertions, deliberately out ofkotlin.test's minimal scope. - The user is writing an Android instrumentation test and asking about the runner (
@RunWith(AndroidJUnit4::class),AndroidJUnitRunner,androidx.test:*) — use../../../jvm-tests/runner/configuring-junit4-on-android/SKILL.mdand../../../instrumentation/runner/running-instrumented-tests-with-androidjunit4/SKILL.md. (You can still usekotlin.testassertions inside those tests.) - The user is testing coroutines /
Flow—runTest,TestScope,Dispatchers.setMainis../../../jvm-tests/coroutines/testing-coroutines-with-runtest/SKILL.md; Turbine is../../../jvm-tests/coroutines/testing-flows-with-turbine/SKILL.md. (kotlin.testsupplies theassert*calls inside those.) - The user wants Compose UI assertions (
assertIsDisplayed,assertTextEquals) — that is thecompose/assertions/skills, unrelated tokotlin.test.
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 · 213 lines · 285 tokens per session scan A cfe88ca89ff7
writing-tests-with-kotlin-test is a skill published in the GitHub repository skydoves/android-testing-skills (319 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 285 tokens to every session and 4,479 once invoked, about $0.0014 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.