Borrowing it
Nothing to install: this file belongs to tidal-music/tidal-sdk-ios. 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/tidal-music/tidal-sdk-ios/main/.agents/skills/prepare-release/SKILL.mdgit clone --depth 1 https://github.com/tidal-music/tidal-sdk-iosWrote 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/tidal-music/tidal-sdk-ios/prepare-release)<a href="https://agentmods.dev/skills/tidal-music/tidal-sdk-ios/prepare-release"><img src="https://agentmods.dev/badge/skills/tidal-music/tidal-sdk-ios/prepare-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/tidal-music/tidal-sdk-ios/prepare-release"><img src="https://agentmods.dev/badge/skills/tidal-music/tidal-sdk-ios/prepare-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.00050 | $0.01620 |
| Opus 5 | $0.00025 | $0.00810 |
| Sonnet 5 | $0.00010 | $0.00324 |
| Haiku 4.5 | $0.00005 | $0.00162 |
Grade A, and why
prepare-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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prepare Release (tidal-sdk-ios)
Releases are triggered automatically when a version bump on main is detected by .github/workflows/trigger-releases.yml. That workflow runs lint + unit tests, then drafts a GitHub release via create-release.yml. All you have to do is land a PR that bumps version.txt and updates CHANGELOG.md in sync.
The scripts that drive this live alongside the skill in scripts/ and are invoked from the same paths by CI.
What CI enforces
changelog-check.ymlruns on every PR that touchesversion.txt. It executesscripts/check-version-sync.sh, which fails unless the exact string inversion.txtappears somewhere inCHANGELOG.md.scripts/check-version-bump.shcompares HEAD vs HEAD~1 onmainusing semver (sort -V). A release is only triggered when the new version is strictly greater than the old one.
Workflow
- Check whether a release is even needed. Run
scripts/check-release-needed.shon a fresh checkout oforigin/main:
It uses the commit that last touchedgit fetch origin main && git checkout origin/main -- ./.agents/skills/prepare-release/scripts/check-release-needed.shversion.txtas the "last released" baseline (more reliable thangit tag, since GitHub releases here are drafted manually and tags lag behind), then reports:- non-merge commits landed since the last bump
- suggested bump type (
major/minor/patch) heuristically derived from those commit subjects - whether the TidalAPI OpenAPI spec version (
Sources/TidalAPI/Config/input/tidal-api-oas.json) is newer than the most recent(TidalAPI)line inCHANGELOG.md - whether
## [Unreleased]is empty despite work having landed (this happens because the auto-update workflow no longer writes there)
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 89 lines · 50 tokens per session scan A fcbb2923ee8b
prepare-release is a skill published in the GitHub repository tidal-music/tidal-sdk-ios (41 stars, last pushed today), licensed Apache-2.0. It adds 50 tokens to every session and 1,620 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-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.