agtrace: Command for Claude Code

.claude/commands/release.md

release is a command for Claude Code from lanegrid/agtrace. It costs 0 tokens per session (1,229 once invoked), scanned A, original, Apache-2.0.

A documented release procedure for agtrace, covering local version and changelog updates and the continuous-integration steps that publish packages and build release files. Continuous integration is an automated build system that runs after code is pushed.

In plain words
What is it for?
Use it to prepare a release, update versions and the changelog, create and push a tag, and let CI publish crates, npm packages, binaries, and the GitHub Release.
Why use it?
It separates local preparation from automated publishing and prevents a local package upload from blocking the whole release. It also records the required tools and starting repository state.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is lanegrid/agtrace's own configuration. It tells Claude Code how to work on agtrace itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agtrace configures →

Reuse

Borrowing it

Nothing to install: this file belongs to lanegrid/agtrace. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/lanegrid/agtrace/main/.claude/commands/release.md
Clone the repo
git clone --depth 1 https://github.com/lanegrid/agtrace

Made for: Claude Code.

Wrote 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.

agentmods badge for release

README.md
[![agentmods](https://agentmods.dev/badge/commands/lanegrid/agtrace/release/github.svg)](https://agentmods.dev/commands/lanegrid/agtrace/release)
Your own site
<a href="https://agentmods.dev/commands/lanegrid/agtrace/release"><img src="https://agentmods.dev/badge/commands/lanegrid/agtrace/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.

agentmods 80×15 button for release

Your own site · 80×15
<a href="https://agentmods.dev/commands/lanegrid/agtrace/release"><img src="https://agentmods.dev/badge/commands/lanegrid/agtrace/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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,229 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.01229
Opus 5.5 $0.00000 $0.00492
Sonnet 5.5 $0.00000 $0.00246
Haiku 4.5 $0.00000 $0.00123

Measured 1mo ago against content hash a043188222fe, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

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.

.claude/commands/release.md · 150 lines

How it starts

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

Release Procedure

This document describes the standard release process for agtrace.

How releasing works

The release is split between local steps and CI:

  • Local (cargo release): bump versions, update CHANGELOG, commit, tag, push. release.toml sets publish = false, so nothing is published from your machine.
  • CI (.github/workflows/release.yml, triggered by the v* tag push):
    • publish-crates: publishes all crates to crates.io in dependency order using the CARGO_REGISTRY_TOKEN repository secret
    • build-local/global-artifacts + host: cargo-dist builds binaries for all platforms and creates the GitHub Release
    • publish-npm: publishes the npm package

Do NOT publish to crates.io locally. No cargo login is needed. If a crate version is already on crates.io when CI runs, cargo publish fails with "already uploaded" and the whole release workflow (including the GitHub Release) is blocked.

Prerequisites

  • On main branch with clean working directory
  • Tools installed: git-cliff and cargo-release (brew install git-cliff cargo-release or cargo install git-cliff cargo-release)

Release Steps

0. Set Release Level

Choose the release level (patch, minor, or major):

# Set release level
RELEASE_LEVEL=patch  # or: minor, major

1. Dry-run (Verification)

Check what will happen without making changes (dry-run is the default):

cargo release --workspace ${RELEASE_LEVEL}

Confirm the version bump and the "Pushing main, vX.Y.Z to origin" plan.

2. Update CHANGELOG

Generate CHANGELOG entries for changes since the last release:

# Get the latest tag and calculate next version
LAST_TAG=$(git describe --tags --abbrev=0)
CURRENT_VERSION=${LAST_TAG#v}  # Remove 'v' prefix

# Calculate next version based on release level
IFS='.' read -r major minor patch <<< "$CURRENT_VERSION"
case "$RELEASE_LEVEL" in
  major) NEXT_VERSION="$((major + 1)).0.0" ;;
  minor) NEXT_VERSION="${major}.$((minor + 1)).0" ;;
  patch) NEXT_VERSION="${major}.${minor}.$((patch + 1))" ;;
esac

echo "Current version: $CURRENT_VERSION"
echo "Next version: $NEXT_VERSION"

# Generate changelog for commits since last tag with version and date
git cliff ${LAST_TAG}..HEAD --unreleased --tag v${NEXT_VERSION} --prepend CHANGELOG.md

Read the full file on GitHub · 150 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. 1mo ago First seen · 150 lines · 0 tokens per session scan A a043188222fe

Subscribe to this mod's changes

release is a command published in the GitHub repository lanegrid/agtrace (62 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,229 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.