Borrowing it
Nothing to install: this file belongs to slayer/gcon. 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/slayer/gcon/master/.claude/commands/release.mdgit clone --depth 1 https://github.com/slayer/gconWrote 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/slayer/gcon/release)<a href="https://agentmods.dev/commands/slayer/gcon/release"><img src="https://agentmods.dev/badge/commands/slayer/gcon/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/slayer/gcon/release"><img src="https://agentmods.dev/badge/commands/slayer/gcon/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.00141 |
| Opus 5.5 | $0.00000 | $0.00056 |
| Sonnet 5.5 | $0.00000 | $0.00028 |
| Haiku 4.5 | $0.00000 | $0.00014 |
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 13d 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
Create Release
Create a new version tag and push it to trigger the release workflow.
Arguments
$ARGUMENTS- Version number (e.g., "0.1.0" or "v0.1.0")
Steps
- Validate the version argument is provided
- Normalize version format (ensure it starts with "v")
- Check that we're on the master branch
- Check that there are no uncommitted changes
- Fetch latest tags and verify the version doesn't already exist
- Create an annotated tag with the version
- Push the tag to origin
- Report success with link to the GitHub Actions workflow
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.
- 13d ago First seen · 19 lines · 0 tokens per session scan A 47ef083cf7a4
release is a command published in the GitHub repository slayer/gcon (8 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 141 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-10-02.
Other commands, from other repositories
publish
Publish oh-my-opencode to npm via GitHub Actions workflow.
rollback
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
ship
Deploy feature through automated staging validation to production with rollback testing.
ci
Run CI validation, create PRs, and merge on green.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.
devops
You are the DevOps Specialist -- the single authority on version control, CI/CD pipelines, platform operations (GitHub, Azure DevOps, GitLab), infrastructure, deployment, backup, and cleanup. If it touches git, pipelines, or production infrastructure, it's yours.