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 ashtanko/kotlin-app-template --skill kotlin-control-flowgit clone --depth 1 https://github.com/ashtanko/kotlin-app-templateWrote 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/ashtanko/kotlin-app-template/kotlin-control-flow)<a href="https://agentmods.dev/skills/ashtanko/kotlin-app-template/kotlin-control-flow"><img src="https://agentmods.dev/badge/skills/ashtanko/kotlin-app-template/kotlin-control-flow/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/ashtanko/kotlin-app-template/kotlin-control-flow"><img src="https://agentmods.dev/badge/skills/ashtanko/kotlin-app-template/kotlin-control-flow.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.00044 | $0.01585 |
| Opus 5 | $0.00022 | $0.00792 |
| Sonnet 5 | $0.00009 | $0.00317 |
| Haiku 4.5 | $0.00004 | $0.00159 |
Grade A, and why
kotlin-control-flow 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 12d 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kotlin control flow
Purpose
Use this skill to write or review the shape of Kotlin branching code. Treat it as a refactoring procedure, not as a style preference.
The target state is simple: the classified value is obvious, branch-local predicates stay with their branch, smart casts remain usable, and the compiler proves exhaustiveness for closed domains.
Procedure
Apply these checks in order.
1. Name the subject
Find the value the code is classifying. If every branch asks a question about the same value, make that value the when subject.
// Replace repeated checks against `state` with a subject `when`.
val action = when (state) {
State.SignedOut -> Action.ShowSignIn
is State.SignedIn -> Action.ShowHome(state.user)
}
If there is no single subject, keep a subjectless when or an if chain.
2. Pick the branch primitive
Use this decision table before editing:
| If the code has... | Use... |
|---|---|
| One value being classified | when (subject) |
| Unrelated boolean conditions | Subjectless when or if/else |
| A primary match plus an extra branch-local predicate | Guard condition |
| Invalid input before the main path | Early return, require, or check |
| A closed enum, Boolean, sealed type, or nullable closed type returning a value | Exhaustive when expression |
| Open external input or a real fallback | Explicit else |
3. Move branch-local predicates into guard conditions
When a branch first matches a type/value and then checks an extra predicate, use a guard condition (requires the Kotlin version in gradle/libs.versions.toml — see ../../reference/coding-conventions.md for this project's pinned language level):
return when (event) {
is Event.Message if event.isUnread -> Row.Highlighted(event.message)
is Event.Message -> Row.Normal(event.message)
Event.Empty -> Row.Empty
}
Apply guards only when all of these are true:
- The
whenhas a subject. - The branch has a primary condition (
is Type, enum entry, object, value, range, etc.). - The extra condition belongs only to that branch.
- A later branch still handles the same primary condition, or the expression remains exhaustive some other way.
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.
- 12d ago First seen · 195 lines · 44 tokens per session scan A 5b6b2af86efb
kotlin-control-flow is a skill published in the GitHub repository ashtanko/kotlin-app-template (41 stars, last pushed 4d ago), licensed Apache-2.0. It adds 44 tokens to every session and 1,585 once invoked, about $0.0002 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
kotlin-coroutines-skill
Load, when a developer writes, reviews, or debugs Kotlin coroutine code and needs help spotting concurrency bugs — GlobalScope leaks, runBlocking in suspend, missing Flow catch, hardcoded or wrong dispatchers, unhandled timeouts, cancellation and structured-concurrency mistakes — or asks how to make async Kotlin…
compose-side-effects
Use when writing or reviewing Jetpack Compose code with LaunchedEffect, DisposableEffect, SideEffect, rememberCoroutineScope, rememberUpdatedState, snapshotFlow, snackbar, navigation, focus requests, analytics, or event Flow collection.
kotlin-control-flow
Use when writing or reviewing Kotlin branching and control flow: when expressions, guard conditions, sealed type exhaustiveness, smart casts, nullable branching, early returns, or replacing complex if/else chains.
deliver-android-feature
Implement an Android feature from a specification or acceptance criteria through architecture, production code, formatting, unit tests, JVM integration tests, local Compose behavior tests, screenshot matrices, managed-device integration tests, end-to-end coverage, and final verification. Use when adding or…
kotlin-multiplatform-expect-actual
Use when designing Kotlin Multiplatform expect/actual or interface boundaries for platform services, native SDKs, source sets, Compose Multiplatform UI, permissions, files, settings, sensors, or platform interop.
kotlin-types-value-class
Use when writing or reviewing Kotlin type declarations to choose @JvmInline value class over data class where appropriate, including Compose stability implications.