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.
npx agentmods add skills/commonstackai/clawbox/clawbox-release-publishnpx skills add CommonstackAI/ClawBox --skill clawbox-release-publishgit clone --depth 1 https://github.com/CommonstackAI/ClawBoxWrote 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/skills/commonstackai/clawbox/clawbox-release-publish)<a href="https://agentmods.dev/skills/commonstackai/clawbox/clawbox-release-publish"><img src="https://agentmods.dev/badge/skills/commonstackai/clawbox/clawbox-release-publish.svg" alt="Measured on agentmods" 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.00092 | $0.00987 |
| Opus 5 | $0.00046 | $0.00494 |
| Sonnet 5 | $0.00018 | $0.00197 |
| Haiku 4.5 | $0.00009 | $0.00099 |
Grade A, and why
clawbox-release-publish 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ClawBox Release Publish
Use this skill to run the current ClawBox release process end to end.
Read first
docs/releasing.md.github/release-notes-template.mddocs/releases/package.jsonscripts/release-version.mjsscripts/sync-version.mjs.github/workflows/release.ymlgit status --short --branch
If the user also asks to create the commit or push the branch/tag, read .agents/skills/clawbox-git-commit-push/SKILL.md.
Workflow
- Inspect the worktree before starting. Stop if unrelated dirty changes would be mixed into the release.
- Fetch tags with
git fetch --tagsbefore generating a version. The UTC day sequence is based on local tags. - Run
npm run release:version. This updatespackage.json,package-lock.json,src-tauri/tauri.conf.json, andsrc-tauri/Cargo.toml. - Read back the selected version with
node -p "require('./package.json').version"and use that exact value for the release commit and tag. - If the user wants curated release notes, copy
.github/release-notes-template.mdtodocs/releases/v<version>.mdand fill it in before the release commit. If that file is missing, GitHub falls back to auto-generated notes. - Run the standard release validation set unless the user explicitly scopes it down:
npm run scan:reponpm run audit:licensesnpm run audit:depsnpm run build:frontendnpm run build:backendcargo check --manifest-path src-tauri/Cargo.toml
- If the user wants the release prepared but not published, stop after reporting the version, changed files, release notes status, and validation status.
- If the user wants the release published, create a focused commit for the release files, create tag
v<version>, push the branch, then push the tag.
Expected commands
Prepare the next release version:
git fetch --tags
npm run release:version
Validate the release:
npm run scan:repo
npm run audit:licenses
npm run audit:deps
npm run build:frontend
npm run build:backend
cargo check --manifest-path src-tauri/Cargo.toml
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 88 lines · 92 tokens per session scan A 4985572c7389
clawbox-release-publish is a skill published in the GitHub repository CommonstackAI/ClawBox (22 stars, last pushed 4mo ago), licensed MIT. It adds 92 tokens to every session and 987 once invoked, about $0.0005 per session on Opus 5. 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.
Other skills, from other repositories
changelog-generation
Changelog generation skill for ZeroClaw releases. Use this skill when the user wants to generate a changelog, prepare release notes, or summarize what changed between versions. Trigger on: 'generate changelog', 'changelog for v0.7.x', 'prepare release notes', 'what changed since ', 'write the changelog'…
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, and create a PR. Use for an explicit /ship invocation or when the user requests the full ship, release, or deploy workflow. For an ordinary commit, push, or pull-request publishing request, use the built-in…
release-publish
Publish a new AlphaClaw release to npm and GitHub. Use when the user asks to cut a release, publish a version, write release notes, draft a release tweet, or close issues addressed in a release. Covers git history analysis, release note drafting, npm publishing, GitHub release creation, issue closing, and tweet…
release-analysis
Analyze an upstream product, dependency, or platform release for downstream impact on the current repo. Use when the user gives a package or repo name such as openclaw or GOG-CLI, or asks about release notes, changelogs, tags, dependency bumps, or upstream announcements. Resolve the GitHub repository, read the latest…
release-openclaw-maintainer
Prepare or verify OpenClaw stable, beta, and extended-stable releases, including backport discovery, changelogs, release notes, publish commands, and artifacts.
release-openclaw-ci
Run, watch, debug, and summarize OpenClaw full release CI, release checks, live provider gates, install/update proofs, and release-secret preflights.