Borrowing it
Nothing to install: this file belongs to jketreno/clare. 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/jketreno/clare/main/.claude/commands/release.mdgit clone --depth 1 https://github.com/jketreno/clareWrote 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/jketreno/clare/release)<a href="https://agentmods.dev/commands/jketreno/clare/release"><img src="https://agentmods.dev/badge/commands/jketreno/clare/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/jketreno/clare/release"><img src="https://agentmods.dev/badge/commands/jketreno/clare/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.00248 |
| Opus 5.5 | $0.00000 | $0.00099 |
| Sonnet 5.5 | $0.00000 | $0.00050 |
| Haiku 4.5 | $0.00000 | $0.00025 |
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.
What it actually says
/project:release — Publish release and sync README
Use this command when asked to cut or publish a release.
Instructions
- Read and follow
.github/skills/release.mdexactly. - Run
./scripts/release.sh --yes(or with explicit--versionwhen provided). - Verify release publication and uploaded assets.
- Update README "CLARE in 60 Seconds" to the new release:
- replace only content between
<!-- RELEASE_VERSION_START -->and<!-- RELEASE_VERSION_END --> - set version label + link to latest release tag
- include minimal installer commands with exact
clare-installer-vX.Y.Z.shfilename
- replace only content between
- Run
./clare/verify-ci.shbefore reporting complete.
Output format
## Release Result
Status: ✅ PASSED / ❌ FAILED
Version: vX.Y.Z
Release URL: https://github.com/jketreno/clare/releases/tag/vX.Y.Z
Assets:
- clare-installer-vX.Y.Z.sh
- clare-installer-vX.Y.Z.sha256
- clare-installer-vX.Y.Z.sha256.asc
README synced: yes/no
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 · 32 lines · 0 tokens per session scan A d6e6491404de
release is a command published in the GitHub repository jketreno/clare (5 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 248 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-31.
Other commands, from other repositories
land
Resolve and squash merge one named, currently authorized pull request.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.