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/analysis-api-bumpnpx skills add aoreshkov/kotlin-lib-mcp --skill analysis-api-bumpgit 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/analysis-api-bump)<a href="https://agentmods.dev/skills/aoreshkov/kotlin-lib-mcp/analysis-api-bump"><img src="https://agentmods.dev/badge/skills/aoreshkov/kotlin-lib-mcp/analysis-api-bump.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.00067 | $0.01078 |
| Opus 5 | $0.00034 | $0.00539 |
| Sonnet 5 | $0.00013 | $0.00216 |
| Haiku 4.5 | $0.00007 | $0.00108 |
Grade A, and why
analysis-api-bump 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bump Kotlin + Analysis API (version-locked)
The Analysis API (standalone K2/FIR) is the single most version-fragile part of this repo.
Kotlin and every *-for-ide artifact must share the exact same version, and two runtime
deps (caffeine, intellijCoroutines) are pinned to match what the bundled IntelliJ core
expects. Getting this wrong shows up as NoSuchMethodError / NoClassDefFoundError at
runtime or as silent loss of type resolution — never a clean compile error. Follow the steps;
do not eyeball it.
1. Snapshot the current pins
Read gradle/libs.versions.toml and record:
kotlin— the shared version ref used by all of:analysisApi-standalone,analysisApi-highLevel,analysisApi-k2,analysisApi-lowLevelFir,analysisApi-implBase,analysisApi-platform,analysisApi-symbolLightClasses,kotlin-compiler, plus thekotlin-*/composeCompiler-*plugin artifacts.caffeine(comment: "runtime dep of the Analysis API-for-idejars; matches Kotlin's own pin").intellijCoroutines(comment: "JetBrains coroutines fork the bundled IJ core expects (KT-81457)").compose(comment: "aligned to Kotlin X.Y.Z") — Compose is Kotlin-coupled too.
Because every Analysis-API artifact uses version.ref = "kotlin", bumping the single
kotlin entry moves them all. The risk is not forgetting one artifact — it's the three
coupled satellites (caffeine, intellijCoroutines, compose) and undocumented API breaks.
2. Confirm the target and its coupled expectations (official sources)
For $ARGUMENTS (or the intended target Kotlin version), verify against official sources:
- kotlinlang.org release notes / Kotlin GitHub release: is this a stable release? Any Analysis API / standalone breaking changes called out?
- The
-for-ideartifacts exist for this version in the IntelliJ dependencies repo (https://www.jetbrains.com/intellij-repository/), not just on Maven Central. - Does the new Kotlin change the caffeine version its
-for-idejars expect? (Check the Kotlin build's own bundled version.) If so, update thecaffeinepin to match and update the comment. - Is KT-81457 fixed in this version, making the
intellijCoroutinesfork pin unnecessary? If yes, that's a chance to drop the fork; if not, keep the pin. - Compose Multiplatform ↔ Kotlin compatibility: pick the
composeversion aligned to the new Kotlin (JetBrains compatibility table) and update the# aligned to Kotlin …comment.
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 · 77 lines · 67 tokens per session scan A 53f485ba7db1
analysis-api-bump is a skill published in the GitHub repository aoreshkov/kotlin-lib-mcp (8 stars, last pushed yesterday), licensed Apache-2.0. It adds 67 tokens to every session and 1,078 once invoked, about $0.0003 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.