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/github-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/github-release)<a href="https://agentmods.dev/skills/baijum/ukulele-companion/github-release"><img src="https://agentmods.dev/badge/skills/baijum/ukulele-companion/github-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/github-release"><img src="https://agentmods.dev/badge/skills/baijum/ukulele-companion/github-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 8 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00053 | $0.00708 |
| Opus 5.5 | $0.00021 | $0.00283 |
| Sonnet 5.5 | $0.00011 | $0.00142 |
| Haiku 4.5 | $0.00005 | $0.00071 |
Grade A, and why
github-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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Release
For normal releases, use
/releaseinstead — it creates the tag, bumps both platform versions, builds, and uploads in one workflow. This skill is for creating a tag without building.
Create a version tag on main and a GitHub release with release notes summarizing changes since the previous tag.
Prerequisites
ghCLI authenticated (gh auth status)- Working tree is clean (
git statusshows no uncommitted changes) - You are on the
mainbranch and up to date with origin
Workflow
Step 1: Verify clean state
git status
git branch --show-current
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.10.1).
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.10.1 -> 10.0.0 |
| Feature | Bump minor, reset patch to 0 | 9.10.1 -> 9.11.0 |
| Bugfix | Bump patch | 9.10.1 -> 9.10.2 |
Ask the user to confirm the new version before proceeding.
Step 3: Create and push the tag
Create an annotated tag on HEAD and push it:
git tag -a v<version> -m "v<version>"
git push origin v<version>
Step 4: Generate release notes
Review commits since the previous tag to build the release notes:
git log <previous-tag>..v<version> --oneline
Summarize the changes into categories (Add, Fix, Update, Refactor, etc.) matching the project's commit format.
Step 5: Create GitHub release
Use the gh CLI to create the release. Do not attach any binary files -- binaries are distributed through the Play Store and App Store.
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 · 90 lines · 53 tokens per session scan A 601fa22c9d31
github-release is a skill published in the GitHub repository baijum/ukulele-companion (14 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 708 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-30.
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.
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.
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).
github
Search repositories, view issues, check PRs on GitHub. Use when: user asks about GitHub repos, issues, PRs, or wants to search GitHub. Don't use when: user wants general web search (use research skill) or asks about git concepts without GitHub context.