Borrowing it
Nothing to install: this file belongs to aoreshkov/kotlin-lib-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/aoreshkov/kotlin-lib-mcp/main/.claude/skills/release/SKILL.mdgit 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/release)<a href="https://agentmods.dev/skills/aoreshkov/kotlin-lib-mcp/release"><img src="https://agentmods.dev/badge/skills/aoreshkov/kotlin-lib-mcp/release/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/aoreshkov/kotlin-lib-mcp/release"><img src="https://agentmods.dev/badge/skills/aoreshkov/kotlin-lib-mcp/release.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.00057 | $0.01163 |
| Opus 5.5 | $0.00023 | $0.00465 |
| Sonnet 5.5 | $0.00011 | $0.00233 |
| Haiku 4.5 | $0.00006 | $0.00116 |
Grade A, and why
release 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 1mo 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cut a release
The release workflow (.github/workflows/release.yml) is triggered by a v* tag and its
first step is a hard version-match guard: if the tag doesn't match the version in both
source-of-truth files, the whole release (GitHub release + GHCR image + MCP registry
publish) fails. This skill makes the two files agree before the tag is pushed.
The advertised MCP
Implementationversion is not a third file to bump: it is build-derived fromgradle.properties(server/build.gradle.ktsbakesproject.versioninto a resource read byServerVersion) and asserted byServerVersionTest, so it can never drift and needs no separate guard.
1. Determine the new version
Use $ARGUMENTS if given. Otherwise read the current version from gradle.properties
(version=), decide the bump with the user (semver), and confirm. Call the new value
<VERSION> (no v prefix inside files; the git tag is v<VERSION>).
2. Bump the version in BOTH guarded files
The tag guard checks these exact patterns (keep the formatting identical):
gradle.properties— the lineversion=<VERSION>(guard:^version=<VERSION>$). This is the single source of truth; the runtime MCP version is derived from it (see the note above), so there is no third file to bump.server.json— the top-level"version": "<VERSION>"(guard:jq .version == <VERSION>). Note: the workflow later also rewritesserver.json.versionand.packages[0].identifierfrom the tag, but the guard still requires the committed value to match, so set it here.
Miss either and the release job aborts at the guard step. Grep to confirm both:
grep -n "version=" gradle.properties
grep -n '"version"' server.json
On a MAJOR or MINOR bump, also repin the plugin. plugin/.mcp.json pins the image to the
<major>.<minor> tag (ghcr.io/aoreshkov/kotlin-lib-mcp:0.5), which follows patches on its own
but not a minor bump. Update that tag and bump plugin/.claude-plugin/plugin.json .version
(its own semver, independent of the server's) so installed plugins actually receive the update —
the community catalog re-pins from the repo automatically. Patch releases need neither.
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.
- 1mo ago First seen · 93 lines · 57 tokens per session scan A 1284ae70977f
release is a skill published in the GitHub repository aoreshkov/kotlin-lib-mcp (13 stars, last pushed 2d ago), licensed Apache-2.0. It adds 57 tokens to every session and 1,163 once invoked, about $0.0002 per session on Opus 5.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
release-kotlin-library
Use when preparing, publishing, or checking readiness for a Kotlin library release, including verifying its gradle-maven-publish-plugin prerequisite, reconciling changelogs and API snapshots, and checking publication.
release-note
A local workspace for producing release-note work. Its files go under `.local/v-release-note/`, which is not meant to be committed to version control.
bump-library-version
A step-by-step process for changing a software library's version number. It chooses a target version, previews the change, applies it, and performs a basic check afterward.
shepherd
Use when asked to shepherd, babysit, monitor, or poll open pull requests or merge requests, including triaging review feedback, CI failures, and routine follow-up.
deliver-spec
Use when explicitly asked to deliver an approved GitHub or local spec through a reviewed pull request, or when a Project controller delegates one claimed implementation ticket.
release-new-version
Use when the user wants to release a new Zafiro version — drafting bilingual release notes, deciding the next version number, bumping app/build.gradle.kts, tagging, and publishing to GitHub (main repo, optionally the Xposed repo).