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/apinpx skills add aoreshkov/kotlin-lib-mcp --skill apigit 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/api)<a href="https://agentmods.dev/skills/aoreshkov/kotlin-lib-mcp/api"><img src="https://agentmods.dev/badge/skills/aoreshkov/kotlin-lib-mcp/api.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 | $0.00036 | $0.00404 |
| Opus 5 | $0.00018 | $0.00202 |
| Sonnet 5 | $0.00007 | $0.00081 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
api 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 4d 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
Public API summary
Arguments: $ARGUMENTS — a Maven coordinate, optionally followed by a package to scope to.
The version may be omitted (or latest) to use the latest stable release. If no coordinate was
given, ask for one instead of guessing.
Steps:
- If the arguments name a library the current project depends on, resolve the version from
gradle/libs.versions.toml, the build script, orpom.xmlrather than taking the latest. fetch_libraryon the coordinate.list_packagesto see the shape of the library and pick the packages worth covering — unless a package was given, in which case use it.list_declarationsper package (public visibility). Page withmaxResults/offsetrather than dumping everything at once.get_api_signature+get_kdocfor the declarations that matter — entry points, factories, the types a caller has to name. Skip the long tail.
Report as:
- One paragraph on what the library is for and how a caller enters it, grounded in the KDoc.
- A table or short list per package: declaration, kind, one-line purpose from the KDoc summary.
- Signatures verbatim for the entry points, in Kotlin, in a fenced block.
- The version you consulted, always. Mark any
bestEffortsignature as approximate. - For a Kotlin Multiplatform library, note the targets each symbol is available on.
Close with what you'd read next (get_source on an implementation, get_dependencies for the
classpath cost) rather than padding the summary.
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.
- 4d ago First seen · 34 lines · 36 tokens per session scan A 6b0bdc60fe9c
api is a skill published in the GitHub repository aoreshkov/kotlin-lib-mcp (8 stars, last pushed 6d ago), licensed Apache-2.0. It adds 36 tokens to every session and 404 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
to-plan
Use when one ready GitHub issue or an in-chat task needs a repository-aware implementation plan for a later implementation workflow.
compose-ui-testing-patterns
Use when writing or reviewing Jetpack Compose UI tests, screenshot tests, previews, semantics assertions, fake image loading, keyboard input, focus assertions, interaction state (hover/pressed/focused), or tests for plain state-driven UI composables.
gradle-run
Use when planning to execute Gradle through gradle, ./gradlew, or a custom gradlew wrapper script, or diagnosing a Gradle build, compact workflow ledger, repeated failure fingerprint, check, test, lint, warning, or failure even when no new Gradle run is appropriate.
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.