A release procedure for creating a new version of the recall project. It updates the Rust package version, records the changes, creates a Git tag, and prepares release checks.

Use it to release a patch, minor, or major version of recall and verify its GitHub and Homebrew distribution files.

It coordinates the many steps involved in publishing a version, including pre-release tags, lockfiles, automated builds, downloadable files, and checksums.

release — Command by zippoxer

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/zippoxer/recall/release

Clone the repo

git clone --depth 1 https://github.com/zippoxer/recall

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 654 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 1 finding. 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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00654
Opus 5	$0.00000	$0.00327
Sonnet 5	$0.00000	$0.00131
Haiku 4.5	$0.00000	$0.00065

Measured 3d ago against content hash 79d8055342f2, 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 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 3d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf /tmp/release && mkdir -p /tmp/release

.claude/commands/release.md · 66 lines

What it actually says

Release a new version of recall.

Bump type: $ARGUMENTS (patch if not specified)

Steps

Read current version from Cargo.toml, compute next version based on bump type (patch/minor/major)
Check git log since last tag to summarize changes for the commit message
Delete any pre-release tags for the new version (e.g., vX.Y.Z-rc1) locally and on remote, if they exist
Bump version in Cargo.toml
Update flake.lock (if flake.nix exists):
```
nix flake update
```

Commit and tag:

git add -A && git commit -m "vX.Y.Z: <summary of changes>"
git tag -a vX.Y.Z -m "vX.Y.Z: <summary of changes>"
git push && git push --tags

Watch GitHub Actions build:
```
gh run watch
```

Download release assets and compute SHA256:

rm -rf /tmp/release && mkdir -p /tmp/release
gh release download vX.Y.Z -R zippoxer/recall --pattern "*.tar.gz" -D /tmp/release
cd /tmp/release && shasum -a 256 *.tar.gz

Verify homebrew-tap was updated correctly by CI:
```
# Fetch the formula and verify hashes match
gh api repos/zippoxer/homebrew-tap/contents/Formula/recall.rb --jq '.content' | base64 -d
```
Compare the SHA256 hashes in the formula with the hashes from step 8:
- recall-macos-intel.tar.gz hash should match on_intel block
- recall-macos-arm64.tar.gz hash should match on_arm block
- recall-linux-x86_64.tar.gz hash should match on_linux block
If hashes don't match, fix manually in ~/code/homebrew-tap (clone if not present).
Verify Homebrew:

brew update && brew upgrade zippoxer/tap/recall

# Test with tmux
tmux new-session -d -s test -x 120 -y 40
tmux send-keys -t test 'recall test query' Enter
sleep 2 && tmux capture-pane -t test -p
tmux kill-session -t test

Verify WinGet (automated via GitHub Actions):
- Check for PR at https://github.com/microsoft/winget-pkgs/pulls?q=is:pr+zippoxer.recall
- The publish-winget job automatically submits a PR to winget-pkgs for non-prerelease versions
- PRs are typically merged within 24-48 hours by the winget-pkgs maintainers

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.

3d ago First seen · 66 lines · 0 tokens per session scan C 79d8055342f2

Subscribe to this mod's changes

release is a command published in the GitHub repository zippoxer/recall (197 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 654 tokens. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Git and workflow Releases claude claude-ai claudecode codex codex-cli openai-codex

release

Getting it into your agent

What it costs to keep this loaded

Grade C, and why

Recursive force deletehighDestructive command

What it actually says

Steps

What this file has done since we first saw it

Other commands, from other repositories

claudikins-kernel:ship

OPSX: Archive

release

updateversion

create-release-note

release