Borrowing it
Nothing to install: this file belongs to ghillb/swarmux. 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/ghillb/swarmux/main/.agents/skills/swarmux-release-playbook/SKILL.mdgit clone --depth 1 https://github.com/ghillb/swarmuxWrote 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/ghillb/swarmux/swarmux-release-playbook)<a href="https://agentmods.dev/skills/ghillb/swarmux/swarmux-release-playbook"><img src="https://agentmods.dev/badge/skills/ghillb/swarmux/swarmux-release-playbook/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/ghillb/swarmux/swarmux-release-playbook"><img src="https://agentmods.dev/badge/skills/ghillb/swarmux/swarmux-release-playbook.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.00043 | $0.00778 |
| Opus 5 | $0.00022 | $0.00389 |
| Sonnet 5 | $0.00009 | $0.00156 |
| Haiku 4.5 | $0.00004 | $0.00078 |
Grade A, and why
swarmux-release-playbook 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 11d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Playbook
Run only the minimum commands needed to publish a release.
Preflight First
Before triggering anything, inspect three states:
- Latest published tag.
gh release list --limit 1
- Version on
main.
gh api repos/$(gh repo view --json nameWithOwner -q .nameWithOwner)/contents/Cargo.toml?ref=main --jq .content | base64 -d | sed -n '1,20p'
- Open release PRs.
gh pr list --state open --search "release in:title"
Interpretation:
- If
main'sCargo.tomlversion is behind the latest published tag,mainhas not caught up to already-published state yet. - If an open release PR version is less than or equal to the latest published tag, that PR is stale/catch-up only. Merging it will not publish a new release; it only advances
mainto already-published state. - Only expect a publish after
mainreflects the latest published version and the next release PR targets a strictly newer version.
Release Now
- Run preflight first.
- If there is an open release PR whose version is less than or equal to the latest published tag, merge it first. Repeat preflight until any remaining open release PR targets a version greater than the latest published tag.
- If there is an open release PR whose version is greater than the latest published tag, merge that PR, then trigger release on
main.
gh workflow run Release --ref main
- If there is no open release PR and
main's version equals the latest published tag, trigger release onmainto letrelease-propen the next release PR. Then merge that PR and trigger release again. - Watch latest run.
gh run list --workflow Release --limit 1
gh run watch <run-id> --exit-status
- If run opened/updated release PR but no artifacts were published:
gh pr list --state open --search "release in:title"
Merge that release PR, then trigger release workflow again:
gh workflow run Release --ref main
- If the post-merge run still publishes nothing and the
releasejob log showsAlready published - Tag ... already exists, the merged release PR was stale/catch-up. Merge the newly opened release PR and triggerReleaseagain until a new tag is published.
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.
- 11d ago First seen · 81 lines · 43 tokens per session scan A f7796943227f
swarmux-release-playbook is a skill published in the GitHub repository ghillb/swarmux (5 stars, last pushed 5mo ago), licensed MIT. It adds 43 tokens to every session and 778 once invoked, about $0.0002 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.
Other skills, from other repositories
agentplane-release-and-packaging-operator
Use when preparing, validating, publishing, auditing, or recovering an Agentplane release, especially package build ordering, version parity, npm/GitHub/GHCR/external distribution publication, public install smoke tests, hosted publish evidence, or release CI failures.
release
Prepare code for release (version bumps, changelog, README updates) and create an annotated tag to trigger the GoReleaser workflow.
release-app-store-changelog
Create user-facing App Store release notes from git history. Use when asked to generate release changelog, App Store "What's New" text, or release notes based on git tags.
versioning-policy
SemVer rules for Squad's stable, preview, insider, and local package versions.
superplan-release
Use when someone asks whether the current product slice is ready to ship, publish, or recommend and the answer depends on a disciplined release-quality check.
codex-seo-release
Prepare Codex SEO release checks without publishing npm or creating Git tags. Use for V1 readiness, package inspection, changelog, license, schemas, migrations, and npm pack checks.