WaveeMusic: Skill for Claude Code

.claude/skills/releasing/SKILL.md

releasing is a skill for Claude Code from christosk92/WaveeMusic. It costs 107 tokens per session (3,684 once invoked), scanned A, original, MIT.

A local release procedure for publishing Wavee as a signed MSIX desktop package for Windows on ARM64 and x64. It covers version edits, rehearsal, building, signing, GitHub Releases, and updating the stable download feed.

In plain words
What is it for?
Use it to rehearse or publish a Wavee release, build and sign the installer, resume or abandon a failed release, or repoint the stable update feed.
Why use it?
It reduces release mistakes by defining the required script sequence and recovery options when a release stops after tagging or during publication.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions CLAUDE.md.

This is christosk92/WaveeMusic's own configuration. It tells Claude Code how to work on WaveeMusic itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything WaveeMusic configures →

Reuse

Borrowing it

Nothing to install: this file belongs to christosk92/WaveeMusic. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/christosk92/WaveeMusic/main/.claude/skills/releasing/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/christosk92/WaveeMusic

Made for: Claude Code.

Wrote 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.

agentmods badge for releasing

README.md
[![agentmods](https://agentmods.dev/badge/skills/christosk92/waveemusic/releasing/github.svg)](https://agentmods.dev/skills/christosk92/waveemusic/releasing)
Your own site
<a href="https://agentmods.dev/skills/christosk92/waveemusic/releasing"><img src="https://agentmods.dev/badge/skills/christosk92/waveemusic/releasing/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.

agentmods 80×15 button for releasing

Your own site · 80×15
<a href="https://agentmods.dev/skills/christosk92/waveemusic/releasing"><img src="https://agentmods.dev/badge/skills/christosk92/waveemusic/releasing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 107 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,684 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00107 $0.03684
Opus 5.5 $0.00043 $0.01474
Sonnet 5.5 $0.00021 $0.00737
Haiku 4.5 $0.00011 $0.00368

Measured 1mo ago against content hash 1be1deef8838, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

releasing 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.

.claude/skills/releasing/SKILL.md · 149 lines

How it starts

The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Releasing Wavee (signed MSIX, local only)

Wavee ships as a NativeAOT, packaged-Win32 full-trust MSIX (arm64 + x64, x64 via the MSVC HostArm64\x64 cross toolchain), signed by Azure Trusted Signing and published to GitHub Releases on this repo. There is no CI job: a CI checkout has no src/apps/Wavee.PlayPlay junction and would silently publish the public-only variant, so a release is cut on the dev box by ops/release/wavee-release.ps1.

Cut a release

# 1. hand edits: src/apps/Wavee/Wavee.Version.props (<WaveeVersion> semver, <WaveeCodename> one per MINOR - NEVER <WaveeBuild>),
#    CHANGELOG.md "## [X.Y.Z] - unreleased", ops/release/wavee/<semver>/whatsnew.json (+ media/)
# 2. rehearse
powershell -File ops\release\wavee-release.ps1 -DryRun -SkipTests
# 3. ship (14 phases; the feed is repointed LAST)
powershell -File ops\release\wavee-release.ps1
# failure after the tag was pushed -> re-run with -Resume; abandon -> -Abort; feed only -> -RepointFeed
Thing Value
Tag wavee-vX.Y.Z — created by the script, annotated, never deleted
Script chain ops/release/wavee-release.ps1 → ops/build/pack-wavee-msix.ps1 (one arch per call) + ops/build/Wavee.Build.psm1 + ops/release/Wavee.Release.psm1
Manifest / template ops/build/Wavee.AppxManifest.xml, ops/build/Wavee.AppInstaller.template.xml (silent: ShowPrompt="false")
Package identity cproducts.Wavee (publisher CN=cproducts, O=cproducts, L=Utrecht, S=Utrecht, C=NL — must equal the cert subject)
Version Wavee.Version.props; MSIX quad = M.m.p.<WaveeBuild> (the script bumps WaveeBuild)
Notes CHANGELOG.md + ops/release/wavee/<semver>/whatsnew.json, validated/rendered by Wavee.ReleaseTool
Version-release assets Wavee_<quad>_arm64.msix, Wavee_<quad>_x64.msix, Wavee-<quad>-win-<arch>-symbols.zip (one per arch: Wavee.pdb + Wavee.map.xml + SYMBOLS.txt), whatsnew.json, media, THIRD-PARTY-NOTICES.txt, MANIFEST.txt
Update feed rolling release wavee-stable → Wavee.arm64.appinstaller, Wavee.x64.appinstaller, whatsnew-index.json (--clobber, repointed last); every install has this URL baked in
Crash symbol maps phase symbols (between packX64 and sign), Publish-WaveeSymbolMap: Wavee.ReleaseTool symbol-map → Wavee.symmap per arch, uploaded with the crash Worker's own ops/crash/worker/node_modules/.bin/wrangler.cmd to wavee-crash/symbols/<quad>/win-<arch>.symmap — what the crash-ingest Worker resolves report RVAs against (and what it needs before it sends a Discord alert). The Store script's own symbols phase uploads symbols/<storeQuad>/win-<arch>.symmap
Crash ingest stamp URL defaults to https://crash.cproducts.dev; the key comes from op read "op://Personal/Wavee crash ingest key/credential" --account my.1password.eu unless -CrashIngestKey is passed — never logged, never written to release-state.json. Preflight crash ingest is HARD for stable/beta/store (only dev ships unstamped); after packing, stamp evidence (Assert-CrashIngestStamp) proves each Wavee.exe carries the URL and key. Same in wavee-store-submit.ps1 (docs/guide/releasing-wavee.md §5b)

Read the full file on GitHub · 149 lines

Changes

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.

  1. 1mo ago Changed · +49 lines 1be1deef8838
  2. 1mo ago Changed · +4 lines 0ce738aead2b
  3. 1mo ago Changed · +9 lines 21cd084dd4e2
  4. 2mo ago Changed · +9 lines d5510ba55a41
  5. 2mo ago First seen · 78 lines · 107 tokens per session scan A 50e762beeafc

Subscribe to this mod's changes

releasing is a skill published in the GitHub repository christosk92/WaveeMusic (80 stars, last pushed yesterday), licensed MIT. It adds 107 tokens to every session and 3,684 once invoked, about $0.0004 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.

Related

releasing compared with skills from other repositories

releasing next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
releasingchristosk92/WaveeMusicSkill80yesterdayMITA107Claude Code
aot-trimmingAaronontheweb/dotnet-skillsSkill1.3k9d agoMITA181Claude Code
blazing-fast-dotnetmanagedcode/dotnet-skillsSkill508yesterdayMITA72Claude Code, Codex
profilingmanagedcode/dotnet-skillsSkill508yesterdayMITA119Claude Code, Codex
software-developerclawdotnet/openclaw.netSkill532yesterdayMITA25Claude Code, Codex
roslyn-codelensMarcelRoozekrans/roslyn-codelens-mcpSkill70todayMITA104Claude Code
safe-github-pushmoorestech/moorestechSkill85todayApache-2.0A114Claude Code