Borrowing it
Nothing to install: this file belongs to sageox/agentx. 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/sageox/agentx/main/.claude/commands/release.mdgit clone --depth 1 https://github.com/sageox/agentxWrote 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/sageox/agentx/release)<a href="https://agentmods.dev/commands/sageox/agentx/release"><img src="https://agentmods.dev/badge/commands/sageox/agentx/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/sageox/agentx/release"><img src="https://agentmods.dev/badge/commands/sageox/agentx/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.01152 |
| Opus 5.5 | $0.00000 | $0.00461 |
| Sonnet 5.5 | $0.00000 | $0.00230 |
| Haiku 4.5 | $0.00000 | $0.00115 |
Grade A, and why
release scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Manually trigger: `curl https://proxy.golang.org/github.com/sageox/agentx/@v/vX.Y.Z.info` How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release agentx Go Module
Release a new version of the agentx Go module library.
Process
1. Pre-flight Checks
Verify the repository is ready for release.
# Check current branch is main
git branch --show-current
# Check for uncommitted changes
git status --porcelain
# Ensure we're up to date with remote
git fetch origin
git status -uno
Requirements:
- Must be on
mainbranch - Working directory must be clean (no uncommitted changes)
- Local branch must be up to date with remote
2. Run Tests and Linting
Ensure all quality checks pass.
# Run full check suite
make check
All tests must pass before proceeding.
3. Determine Version Number
Check the current version and recent changes.
# List existing tags
git tag -l 'v*' | sort -V | tail -5
# View recent commits since last tag
git log $(git describe --tags --abbrev=0 2>/dev/null || echo "HEAD~20")..HEAD --oneline
Version Guidelines (Semantic Versioning):
- MAJOR (1.0.0): Breaking API changes
- MINOR (0.X.0): New features, backward compatible
- PATCH (0.0.X): Bug fixes, backward compatible
4. Review and Update CHANGELOG.md
Analyze changes since the last release.
# View detailed changes
git log $(git describe --tags --abbrev=0 2>/dev/null || echo "HEAD~20")..HEAD --pretty=format:"%h %s"
# View files changed
git diff $(git describe --tags --abbrev=0 2>/dev/null || echo "HEAD~20")..HEAD --stat
Update CHANGELOG.md with:
- New version header with today's date
- Categorize changes under: Added, Changed, Deprecated, Removed, Fixed, Security
- Keep descriptions concise but informative
Example entry:
## [0.3.0] - 2026-02-15
### Added
- New agent support for XYZ coding assistant
### Changed
- Improved detection accuracy for environment variables
### Fixed
- Race condition in hook manager initialization
5. Commit CHANGELOG Updates
git add CHANGELOG.md
git commit -m "chore: prepare release vX.Y.Z"
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 · 182 lines · 0 tokens per session scan A b534499b5b71
release is a command published in the GitHub repository sageox/agentx (4 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,152 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
iterate
Iteration delivery — delivery check + archive + commit & tag + bump version.
cargo-publish
Command "cargo-publish" from olorehq/olore, covering cargo-publish(1), name, synopsis, description and options.
release
create a release PR (auto-detects previous tag).
release-tag
Create and push a version tag after a release PR has been merged.
release
Publish a release branch.
ship
Prepare a release branch.