Borrowing it
Nothing to install: this file belongs to ClawForgeAI/clawforge. 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/ClawForgeAI/clawforge/main/.claude/commands/release.mdgit clone --depth 1 https://github.com/ClawForgeAI/clawforgeWrote 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/clawforgeai/clawforge/release)<a href="https://agentmods.dev/commands/clawforgeai/clawforge/release"><img src="https://agentmods.dev/badge/commands/clawforgeai/clawforge/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/clawforgeai/clawforge/release"><img src="https://agentmods.dev/badge/commands/clawforgeai/clawforge/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.00356 |
| Opus 5.5 | $0.00000 | $0.00142 |
| Sonnet 5.5 | $0.00000 | $0.00071 |
| Haiku 4.5 | $0.00000 | $0.00036 |
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 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.
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
Release Workflow
Guide through the changeset-based release process for the @clawforgeai/clawforge plugin.
Note: Only the plugin/ package is published to npm. Server and admin are excluded (see .changeset/config.json).
Instructions
Determine the release stage from: $ARGUMENTS
If no argument given, ask the user which step they need:
Step 1: Create changeset (create)
- Ask what changed and whether it's a patch, minor, or major bump
- Run
pnpm changeset - The user selects
@clawforgeai/clawforgeand bump type interactively - Review the generated
.changeset/*.mdfile - Commit the changeset file
Step 2: Check pending changesets (check)
- List files in
.changeset/directory (exclude config.json and README.md) - Read each changeset file and summarize pending version bumps
- Report current plugin version from
plugin/package.json
Step 3: Version bump (version)
- Run
pnpm version-packagesto apply changesets - Review changes to
plugin/package.jsonversion andCHANGELOG.md - Commit the version bump
Step 4: Verify before publish (verify)
- Run
pnpm --filter @clawforgeai/clawforge build - Run
pnpm --filter @clawforgeai/clawforge test - Report build and test results
Note: Actual npm publishing happens via the GitHub Actions release workflow (.github/workflows/release.yml) when the "Version Packages" PR is merged to main.
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.
- 2mo ago First seen · 40 lines · 0 tokens per session scan A 33779a375b59
release is a command published in the GitHub repository ClawForgeAI/clawforge (17 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 356 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-09-04.
release compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| releaseClawForgeAI/clawforge | Command | 17 | yesterday | MIT | A | 0 | Claude Code |
| deployNickRomanek/clawbridge | Command | 23 | 19d ago | Apache-2.0 | A | 0 | Claude Code |
| rebase_promptfotoetienne/gru | Command | 11 | 1mo ago | Apache-2.0 | A | 0 | Claude Code |
| commit-push-prpablo-albaladejo/kaiord | Command | 11 | 4d ago | MIT | A | 14 | Claude Code |
| nyann:shipthettwe/nyann | Command | 7 | 6d ago | MIT | A | 63 | Claude Code |
| nyann:releasethettwe/nyann | Command | 7 | 6d ago | MIT | A | 37 | Claude Code |
| explore-releasejuan294/cc-rpi | Command | 5 | 3d ago | MIT | A | 0 | Claude Code |