recall: Command for Claude Code

.claude/commands/release.md

release is a command for Claude Code from zippoxer/recall. It costs 0 tokens per session (654 once invoked), scanned C, original, MIT.

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.

In plain words
What is it for?
Use it to release a patch, minor, or major version of recall and verify its GitHub and Homebrew distribution files.
Why use it?
It coordinates the many steps involved in publishing a version, including pre-release tags, lockfiles, automated builds, downloadable files, and checksums.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is zippoxer/recall's own configuration. It tells Claude Code how to work on recall 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 recall configures →

Reuse

Borrowing it

Nothing to install: this file belongs to zippoxer/recall. 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/zippoxer/recall/main/.claude/commands/release.md
Clone the repo
git clone --depth 1 https://github.com/zippoxer/recall

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/zippoxer/recall/release/github.svg)](https://agentmods.dev/commands/zippoxer/recall/release)
Your own site
<a href="https://agentmods.dev/commands/zippoxer/recall/release"><img src="https://agentmods.dev/badge/commands/zippoxer/recall/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/zippoxer/recall/release"><img src="https://agentmods.dev/badge/commands/zippoxer/recall/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 654 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.00654
Opus 5.5 $0.00000 $0.00262
Sonnet 5.5 $0.00000 $0.00131
Haiku 4.5 $0.00000 $0.00065

Measured 2mo ago against content hash 79d8055342f2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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

  1. Read current version from Cargo.toml, compute next version based on bump type (patch/minor/major)

  2. Check git log since last tag to summarize changes for the commit message

  3. Delete any pre-release tags for the new version (e.g., vX.Y.Z-rc1) locally and on remote, if they exist

  4. Bump version in Cargo.toml

  5. Update flake.lock (if flake.nix exists):

    nix flake update
    
  6. 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
    
  7. Watch GitHub Actions build:

    gh run watch
    
  8. 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
    
  9. 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).

  10. 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
  1. Verify WinGet (automated via GitHub Actions):
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. 2mo 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 (198 stars, last pushed 9mo 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.

Related

release compared with commands from other repositories

release next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
releasezippoxer/recallCommand1989mo agoMITC0Claude Code
claudikins-kernel:shippovvo/claudikins-kernelCommand1276mo agoMITA25Claude Code
create-release-notecentminmod/my-claude-code-setupCommand2.7k1mo agoMITA0Claude Code
changelogtravisjneuman/.claudeCommand107yesterdayMITA16Claude Code
commitfusengine/agentsCommand3425d agoMITA31Claude Code
shipcomposio-community/awesome-claude-pluginsCommand2.0kyesterdaynoneA9Claude Code
versioningMarcel-Bich/marcel-bich-claude-marketplaceCommand12yesterdayMITA13Claude Code