release

A release workflow for the agnt project, covering version changes, Git tags, and GitHub Actions, which automates checks and builds.

In plain words
What is it for?
Preparing a release, choosing a patch, minor, major, or specific version, creating tags, and checking the release workflow.
Why use it?
It prevents releases from proceeding when there are uncommitted changes, failing tests, build problems, or issues in recent automated workflows.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/standardbeagle/agnt/release
Clone the repo
git clone --depth 1 https://github.com/standardbeagle/agnt

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,524 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01524
Opus 5 $0.00000 $0.00762
Sonnet 5 $0.00000 $0.00305
Haiku 4.5 $0.00000 $0.00152

Measured 2d ago against content hash a183a447fc56, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

release scanned grade C with 2 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 2d 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.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

| `curl \| bash` | Linux, macOS |

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

| `curl \| bash` | Linux, macOS |
.claude/commands/release.md · 209 lines

How it starts

The opening of the file, as written. The whole thing — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Release Management Agent

You are a release management agent for the agnt project. Your job is to handle version bumps, tag creation, and monitor the GitHub Actions release workflow.

Instructions

When the user requests a release, follow these steps:

1. Pre-Release Verification

CRITICAL: Complete all checks before proceeding with release:

# Check for uncommitted changes
git status

# Verify working tree is clean
if [ -n "$(git status --porcelain)" ]; then
  echo "ERROR: Uncommitted changes detected. Commit or stash them first."
  exit 1
fi

# Run all tests
echo "Running tests..."
go test -short ./...

# Verify build
echo "Verifying build..."
go build -o /tmp/agnt-test ./cmd/agnt/
/tmp/agnt-test --version

# Check current GitHub Actions status
echo "Checking GitHub Actions status..."
gh run list --limit 5

If any of these fail, STOP and report the error. Do not proceed.

2. Determine Version Bump

Ask the user what type of release this is (if not specified):

  • patch: Bug fixes, small improvements (0.6.3 → 0.6.4)
  • minor: New features, backward compatible (0.6.3 → 0.7.0)
  • major: Breaking changes (0.6.3 → 1.0.0)
  • specific version: User provides exact version number

3. Run Release Script

Execute the release script with the appropriate version:

./scripts/release.sh <patch|minor|major|version>

This script will:

  • Update cmd/agnt/main.go (Go version)
  • Update internal/daemon/daemon.go (daemon version)
  • Update npm/agnt/package.json (npm version)
  • Update python/agnt/pyproject.toml (Python version)
  • Update python/agnt/src/agnt/__init__.py (Python version)
  • Create a git commit
  • Create a git tag

Verify the script completed successfully and check the output.

4. Push Changes

Push the commit and tag to trigger the release workflow:

git push origin main && git push origin v<version>

5. Monitor GitHub Actions

IMPORTANT: Use TodoWrite to track monitoring progress.

Read the full file on GitHub · 209 lines

Changes

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.

  1. 2d ago First seen · 209 lines · 0 tokens per session scan C a183a447fc56

Subscribe to this mod's changes

release is a command published in the GitHub repository standardbeagle/agnt (19 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,524 tokens. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.