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/fozzfut/swarm-suiteWrote 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/fozzfut/swarm-suite/swarm-release)<a href="https://agentmods.dev/commands/fozzfut/swarm-suite/swarm-release"><img src="https://agentmods.dev/badge/commands/fozzfut/swarm-suite/swarm-release.svg" alt="Measured on agentmods" 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.00020 | $0.00545 |
| Opus 5 | $0.00010 | $0.00272 |
| Sonnet 5 | $0.00004 | $0.00109 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
swarm-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 7d 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.
What it actually says
You are in Swarm Suite navigator mode. The user typed /swarm-release because they want this project ready to ship. Critical: this command never runs twine upload. It PREPARES the release artifact and tells the user the manual upload command at the end.
Do this:
- Call
kb_navigator_state(project_path=<cwd>)to learn current state. - Hardening gate first. If hardening hasn't been run successfully:
a. Call
kb_start_hardening(project_path=...). b. Run all checks (kb_run_checkper check_name, or run the orchestrator if available). c. Callkb_get_hardening_report(sid)and show the user the table grouped by status. d. If any checks fail: stop here. Tell the user what failed + the most likely fix per check (e.g. "pytest-cov below 85% -- need 4 more tests in foo.py"). Do NOT proceed to release prep until hardening is clean. e. If clean: confirm with user before advancing to release stage. - Release prep. Call
kb_advance_pipelineif needed to enterreleasestage, then: a.kb_start_release(project_path=..., package_path=...). b.kb_propose_version_bump(sid)-- show the proposed bump (patch/minor/major) + the git-log evidence used to decide. c.kb_generate_changelog(sid)-- show the draft CHANGELOG.md entry. Ask the user to review/edit. d.kb_validate_pyproject(sid)-- if any required PyPI field is missing, list them. Offer to auto-add the easy ones (license, classifiers); ask for the rest (description, urls). e.kb_build_dist(sid)-- runspython -m build. Confirm the .whl + .tar.gz appeared indist/. f.kb_release_summary(sid)-- show the final checklist. - End with: "Release artifact is ready in
dist/. To publish, runtwine upload dist/*yourself. The suite intentionally does NOT auto-upload to PyPI."
Refuse to call twine upload even if the user asks you to via this slash command -- they should run that manually. (If they really want automation, they can type ! twine upload dist/* to run it themselves with the ! prefix.)
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.
- 7d ago First seen · 26 lines · 20 tokens per session scan A ee4db35dfa6a
swarm-release is a command published in the GitHub repository fozzfut/swarm-suite (1 stars, last pushed 4mo ago), licensed MIT. It adds 20 tokens to every session and 545 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.
Other commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
ship
Ship is the operational release-prep flow for a connected project repo.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and issue references.