Borrowing it
Nothing to install: this file belongs to baijum/ukulele-companion. 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/baijum/ukulele-companion/main/.cursor/skills/release/SKILL.mdgit clone --depth 1 https://github.com/baijum/ukulele-companionWrote 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/baijum/ukulele-companion/release)<a href="https://agentmods.dev/skills/baijum/ukulele-companion/release"><img src="https://agentmods.dev/badge/skills/baijum/ukulele-companion/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/baijum/ukulele-companion/release"><img src="https://agentmods.dev/badge/skills/baijum/ukulele-companion/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.00070 | $0.02994 |
| Opus 5 | $0.00035 | $0.01497 |
| Sonnet 5 | $0.00014 | $0.00599 |
| Haiku 4.5 | $0.00007 | $0.00299 |
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 10d 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 — 382 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release (Android + iOS)
Build and release both platforms from a single version tag. Bumps Android and iOS versions atomically in one commit, then builds and distributes both.
Prerequisites
ghCLI authenticated (gh auth status)- Working tree is clean, on
main, up to date with origin - Signing keystore via
keystore.propertiesat project root (Android) - Google Play service account key at
app/play-service-account.json(Android upload) - Xcode installed with code signing configured (iOS)
- JDK 17 for shared KMP framework build
Workflow
Step 1: Verify clean state
git status
git branch --show-current
gh auth status
Confirm the branch is main and there are no uncommitted changes. If the working tree is dirty, stop and ask the user to commit or stash first.
Step 2: Determine the next version
Read the latest existing tag:
git describe --tags --abbrev=0
The project uses semantic versioning (major.minor.patch) with a v prefix (e.g., v9.11.0).
If the user did not specify a version or release type, ask which type of release to create:
| Release type | What changes | Example |
|---|---|---|
| Major | Bump major, reset minor and patch to 0 | 9.11.0 -> 10.0.0 |
| Feature | Bump minor, reset patch to 0 | 9.11.0 -> 9.12.0 |
| Bugfix | Bump patch | 9.11.0 -> 9.11.1 |
Ask the user to confirm the new version before proceeding.
Step 3: Run quality gates
All gates must pass before any version bumping or tagging.
3a. Run lint
./gradlew lintDebug
If lint fails, stop and fix the errors first.
3b. Run unit tests
./gradlew testDebugUnitTest
3c. Run instrumented tests
Check for a running emulator (adb devices) and run:
./gradlew connectedAndroidTest
If any test fails, stop the release and fix the failures first. Do not proceed to version bumping until all gates pass.
Step 4: Bump both platform versions in one commit
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.
- 10d ago First seen · 382 lines · 70 tokens per session scan A 5b7bff88d92d
release is a skill published in the GitHub repository baijum/ukulele-companion (14 stars, last pushed 7d ago), licensed MIT. It adds 70 tokens to every session and 2,994 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-30.
Other skills, from other repositories
release-kotlin-library
Use when preparing, publishing, or checking readiness for a new Kotlin library version in a repository using gradle-maven-publish-plugin, including release changelog reconciliation, API snapshots, and publication verification.
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).
findeck-release
A document-review workflow that works on one specification document and only the higher-level or reference documents configured for it. It supports reference and revise actions and records history with reference-specific snapshots.
sceneview-ios
Build 3D and AR apps on Apple platforms (iOS, macOS, visionOS) with SceneViewSwift — the SwiftUI wrapper around RealityKit. Use whenever the user asks for "3D in SwiftUI", "AR with ARKit in SwiftUI", a model viewer for iOS, or any Apple-platform 3D/AR app where the dependency is the SceneViewSwift Swift Package from…
sceneview
Build 3D and AR apps with the SceneView SDK in Jetpack Compose, SwiftUI (iOS/macOS/visionOS via SceneViewSwift), Web (Filament.js), Flutter and React Native. Use whenever the user asks for "3D in Compose", "AR with ARCore in Compose", a model viewer, or any cross-platform 3D/AR app where the dependency is…
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.