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.
git clone --depth 1 https://github.com/windaddict/switchboard-streamdeckWrote 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/commands/windaddict/switchboard-streamdeck/release)<a href="https://agentmods.dev/commands/windaddict/switchboard-streamdeck/release"><img src="https://agentmods.dev/badge/commands/windaddict/switchboard-streamdeck/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/commands/windaddict/switchboard-streamdeck/release"><img src="https://agentmods.dev/badge/commands/windaddict/switchboard-streamdeck/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00017 | $0.00845 |
| Opus 5.5 | $0.00007 | $0.00338 |
| Sonnet 5.5 | $0.00003 | $0.00169 |
| Haiku 4.5 | $0.00002 | $0.00085 |
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 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 — 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 statusis clean and onmain;git pull --rebase.npm run typecheck && npm test && npm run buildall pass (streamdeck validateruns inbuild).- 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, Team9CHGJ6ZAE6). Requires the one-time Account-Holder Developer ID cert (Xcode → Settings → Accounts → Manage Certificates → + → Developer ID Application). Then commit the freshly signedbin/macos/{scroll,tile,axcheck}— those exact bytes are what Apple notarized.
2. Version bump + docs
- Set
package.jsonversiontoX.Y.Z. - Set the manifest
VersiontoX.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.pyif actions were added/renamed; commit the hero. - Commit (
release: prep vX.Y.Z …) andgit push origin main.
3. Pack the artifacts
npm run build— rebuilds ONLYbin/plugin.js. Never runnpm run build:helperhere (re-signing changes helper hashes and breaks notarization).npm run pack && npm run pack:zip→dist/com.movingavg.switchboard.streamDeckPluginanddist/com.movingavg.switchboard.sdPlugin.zip.shasum -a 256 dist/com.movingavg.switchboard.sdPlugin.zip— note the hash.
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 · 64 lines · 17 tokens per session scan A 1d3fa7b977e3
release is a command published in the GitHub repository windaddict/switchboard-streamdeck (6 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.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.
Other commands, from other repositories
changelog
Generate changelog from session work with Problem/Solution format.
release
Increment version (SemVer), commit, and tag for release.
publish
Release a new package version — semver bump from commits, tag, registry publish, GitHub Release.
bump
Full dependency and toolchain bump — deps to latest major, Node pins, GitHub Actions, audit, validate, commit.
land
Resolve and squash merge one named, currently authorized pull request.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.