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/aoreshkov/kotlin-lib-mcp/migratenpx skills add aoreshkov/kotlin-lib-mcp --skill migrategit clone --depth 1 https://github.com/aoreshkov/kotlin-lib-mcpWrote 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/aoreshkov/kotlin-lib-mcp/migrate)<a href="https://agentmods.dev/skills/aoreshkov/kotlin-lib-mcp/migrate"><img src="https://agentmods.dev/badge/skills/aoreshkov/kotlin-lib-mcp/migrate.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.00032 | $0.00539 |
| Opus 5 | $0.00016 | $0.00269 |
| Sonnet 5 | $0.00006 | $0.00108 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
migrate 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.
What it actually says
Upgrade impact report
Arguments: $ARGUMENTS — group:artifact plus the two versions to compare. If the target
version is missing, use get_latest_version. If the source version is missing, read the one the
project currently depends on from gradle/libs.versions.toml, the build script, or pom.xml.
Steps:
fetch_libraryboth coordinates:group:artifact:<from>andgroup:artifact:<to>.list_packageson both. Packages that appear or disappear are the loudest signal — report them first.list_declarations(public) per shared package on both versions. Page through withmaxResults/offset; do not truncate silently — if you stopped early, say where.- Classify every difference:
- Removed — gone in the new version. Breaking.
- Changed — same FQ name, different signature (
get_api_signatureon both). Breaking if the parameter list, receiver, nullability or generics moved. - Added — new surface. Worth mentioning only where it replaces something removed.
- For each removed or changed symbol, search the workspace for real usages (Grep on the simple name, then confirm the import). A break nobody calls is a footnote, not a task.
get_kdocon the replacement candidates — deprecation notices and@since/@seetags in the new version usually name the intended migration path.search_sourceon the old name in the new version often finds the renamed symbol directly.get_dependencieson both, so a transitive bump that comes along for the ride is not a surprise.
Report as:
- Verdict line — how many breaking changes actually touch this codebase.
- Table: symbol · what changed · files affected · suggested replacement.
- Notes: API additions worth adopting, dependency-tree changes, packages added/removed.
- What you did not check — pages you stopped short of, packages skipped, anything only reachable through reflection or a service loader, which this diff cannot see.
Do not edit any code as part of this report. Land the analysis first; the user decides what to change.
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 · 42 lines · 32 tokens per session scan A 25d99bfdf851
migrate is a skill published in the GitHub repository aoreshkov/kotlin-lib-mcp (8 stars, last pushed yesterday), licensed Apache-2.0. It adds 32 tokens to every session and 539 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-31.
Other skills, from other repositories
compose-animations
Use when writing or reviewing Jetpack Compose motion: visibility enter/exit, animating one property toward a target, color or size transitions, multiple properties from one state, switching composable content, or choosing between AnimatedVisibility, animateAsState, rememberTransition, AnimatedContent, and Crossfade.
compose-focus-navigation
Use when writing or reviewing Jetpack Compose UI for TV, keyboard, desktop, accessibility focus, D-pad navigation, FocusRequester, focusProperties, key events, or initial focus behavior.
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.
using-chrisbanes-skills
Use when debugging, benchmarking, or profiling leads into Kotlin or Jetpack Compose source before the cause is known, or when one task spans multiple Kotlin or Compose concerns, especially plain Kotlin Flow or navigation delivery plus sealed branching.
kotlin-concurrency-and-flow
Use when writing or reviewing Kotlin coroutine scope ownership, raw Thread or Executor work, init launches, non-suspending launch APIs, runBlocking, cancellation, StateFlow, SharedFlow, Channel, stateIn, SharingStarted, state updates, or one-shot events.
kotlin-api-design
Use when designing or reviewing Kotlin function ownership, member or extension functions, factories, single-field domain types, value classes, data classes, Kotlin Multiplatform expect/actual declarations, or platform service boundaries.