Borrowing it
Nothing to install: this file belongs to strands-rl/strands-sglang. 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/strands-rl/strands-sglang/main/.claude/commands/create-release.mdgit clone --depth 1 https://github.com/strands-rl/strands-sglangWrote 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/strands-rl/strands-sglang/create-release)<a href="https://agentmods.dev/commands/strands-rl/strands-sglang/create-release"><img src="https://agentmods.dev/badge/commands/strands-rl/strands-sglang/create-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/strands-rl/strands-sglang/create-release"><img src="https://agentmods.dev/badge/commands/strands-rl/strands-sglang/create-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.00000 | $0.00764 |
| Opus 5.5 | $0.00000 | $0.00306 |
| Sonnet 5.5 | $0.00000 | $0.00153 |
| Haiku 4.5 | $0.00000 | $0.00076 |
Grade A, and why
create-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 2mo 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a new release: generate release notes, create a GitHub release (which triggers PyPI publish), and verify the pipeline.
The user optionally provides a version as $ARGUMENTS (e.g., 0.4.0). If not provided, determine the next version from the latest git tag and the nature of changes (patch for fixes/chores, minor for features, major for breaking changes).
Steps
1. Determine version
- Find the latest git tag:
git tag --sort=-v:refname | head -1 - If the user didn't provide a version, suggest one based on commits since the last tag.
- Confirm the version with the user before proceeding.
2. Generate release notes
- List commits since the last tag:
git log --oneline <last_tag>..HEAD - Categorize using conventional commit prefixes:
feat→ Featuresfix→ Bug Fixesrefactor→ Refactoringperf→ Performancedocs→ Documentationtest→ Testsbuild,ci,chore→ Maintenance (group together)- Breaking changes (any commit with
!after type, e.g.,feat!:) → Breaking Changes section at the top
- Skip: merge commits, commits that only touch
.claude/ordocs/plans/ - Write descriptions from the user's perspective, not the commit message verbatim.
- Omit empty sections. Group related commits into a single bullet point.
- Keep it concise — release notes are for users, not a git log dump.
3. Show the user the release notes for review
Present the full release notes in the body format below and ask the user to confirm before creating the release.
Body format:
## What's New
### Features
- Brief description of feature ([#PR](url) if applicable)
### Bug Fixes
- Brief description of fix
**Full Changelog**: https://github.com/strands-rl/strands-sglang/compare/<last_tag>...v<new_version>
4. Create the GitHub release
Once the user confirms, create the release using gh release create. This automatically creates the git tag.
gh release create v<version> --title "v<version>" --notes "<body>"
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.
- 2mo ago First seen · 75 lines · 0 tokens per session scan A de45e1909d65
create-release is a command published in the GitHub repository strands-rl/strands-sglang (79 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 764 tokens. 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.
Other commands, from other repositories
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.
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.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
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.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.