release

A prescribed workflow for releasing the Switchboard application through GitHub and a Homebrew tap. It includes checks, signing, notarization, version changes, and builds.

In plain words
What is it for?
Use it to prepare and publish a signed, notarized Switchboard release.
Why use it?
It gathers the release steps and required checks into one repeatable process, helping catch failures before publishing.

Command for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/windaddict/switchboard-streamdeck/release
Clone the repo
git clone --depth 1 https://github.com/windaddict/switchboard-streamdeck

Made for: Claude Code.

Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 845 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00017 $0.00845
Opus 5 $0.00009 $0.00423
Sonnet 5 $0.00003 $0.00169
Haiku 4.5 $0.00002 $0.00085

Measured yesterday against content hash 1d3fa7b977e3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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

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/commands/release.md · 64 lines

How it starts

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

Cut a new Switchboard release end to end. Default the version to the next patch of the current package.json version unless the user specifies one in $ARGUMENTS (e.g. /release 1.2.0). Work from ~/code/switchboard.

Follow these steps in order. Stop and report if any check fails.

0. Preflight

  • git status is clean and on main; git pull --rebase.
  • npm run typecheck && npm test && npm run build all pass (streamdeck validate runs in build).
  • Decide the version X.Y.Z.

1. Helpers: only if a helper/*.swift changed since the last release

  • If unchanged: do nothing here — the committed bin/macos/* are already Developer ID signed + notarized; reuse them as-is.
  • If changed: bundle exec fastlane mac notarize_helpers (signs + notarizes via the App Store Connect API key, Team 9CHGJ6ZAE6). Requires the one-time Account-Holder Developer ID cert (Xcode → Settings → Accounts → Manage Certificates → + → Developer ID Application). Then commit the freshly signed bin/macos/{scroll,tile,axcheck} — those exact bytes are what Apple notarized.

2. Version bump + docs

  • Set package.json version to X.Y.Z.
  • Set the manifest Version to X.Y.Z.0 (com.movingavg.switchboard.sdPlugin/manifest.json) — this is the version the Stream Deck app displays. It drifted before (manifest said 1.2.0.0 while v1.1.0/v1.1.1 shipped); keep the two in lockstep.
  • Update README.md: action count and test count if they changed.
  • Run python3 scripts/make-hero.py if actions were added/renamed; commit the hero.
  • Commit (release: prep vX.Y.Z …) and git push origin main.

3. Pack the artifacts

  • npm run build — rebuilds ONLY bin/plugin.js. Never run npm run build:helper here (re-signing changes helper hashes and breaks notarization).
  • npm run pack && npm run pack:zipdist/com.movingavg.switchboard.streamDeckPlugin and dist/com.movingavg.switchboard.sdPlugin.zip.
  • shasum -a 256 dist/com.movingavg.switchboard.sdPlugin.zip — note the hash.

Read the full file on GitHub · 64 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. yesterday First seen · 64 lines · 17 tokens per session scan A 1d3fa7b977e3

Subscribe to this mod's changes

release is a command published in the GitHub repository windaddict/switchboard-streamdeck (5 stars, last pushed 9d ago), licensed MIT. It adds 17 tokens to every session and 845 once invoked, about $0.0001 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-31.