What is clawbox-release-publish?

A release procedure for the ClawBox desktop application. It uses the UTC date and existing tags to choose a version, update project files, validate the release, and publish a matching Git tag.

It is for preparing, validating, versioning, tagging, and publishing ClawBox releases, including writing release notes when requested.

Desktop releases require the same version in several files and must follow a consistent tagging process. This procedure reduces mismatches and helps the release workflow create a GitHub Release.

clawbox-release-publish — Skill for Codex by CommonstackAI/ClawBox

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.

Any agent

npx skills add CommonstackAI/ClawBox --skill clawbox-release-publish

Clone the repo

git clone --depth 1 https://github.com/CommonstackAI/ClawBox

Made for: Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/commonstackai/clawbox/clawbox-release-publish/github.svg)](https://agentmods.dev/skills/commonstackai/clawbox/clawbox-release-publish)

Your own site

<a href="https://agentmods.dev/skills/commonstackai/clawbox/clawbox-release-publish"><img src="https://agentmods.dev/badge/skills/commonstackai/clawbox/clawbox-release-publish/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.

Your own site · 80×15

<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="Reviewed on agentmods" width="80" height="20"></a>

Per session 92 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 987 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. 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.

Model	Per session	Once invoked
Fable 5.1	$0.00092	$0.00987
Opus 5.5	$0.00037	$0.00395
Sonnet 5.5	$0.00018	$0.00197
Haiku 4.5	$0.00009	$0.00099

Measured 2mo ago against content hash 4985572c7389, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

.agents/skills/clawbox-release-publish/SKILL.md · 88 lines

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.md
docs/releases/
package.json
scripts/release-version.mjs
scripts/sync-version.mjs
.github/workflows/release.yml
git 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 --tags before generating a version. The UTC day sequence is based on local tags.
Run npm run release:version. This updates package.json, package-lock.json, src-tauri/tauri.conf.json, and src-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.md to docs/releases/v<version>.md and 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: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
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

Read the full file on GitHub · 88 lines

Files

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.

agents/openai.yaml 205 B

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.

2mo ago First seen · 88 lines · 92 tokens per session scan A 4985572c7389

Subscribe to this mod's changes

clawbox-release-publish is a skill published in the GitHub repository CommonstackAI/ClawBox (22 stars, last pushed 6mo ago), licensed MIT. It adds 92 tokens to every session and 987 once invoked, about $0.0004 per session on Opus 5.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.

Git and workflow Releases agent-skills ai assistant openclaw

github

GitHub CLI for issues, PRs, CI/check logs, comments, reviews, releases, repos, and gh api queries.

openclaw/openclaw · 28 tokens

ship

Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy", "push to main", "create a PR", "merge and push", or "get it deployed". Proactively invoke this skill (do NOT push/PR directly) when the user says code is…

GCWing/BitFun · 105 tokens

pm-release

A release-planning workflow for preparing software to go live, including checks, deployment choices, timing, and rollback conditions.

konglong87/superPM · 60 tokens

git-workflow

Guides you through Git workflows — branching strategies, commit conventions, merge conflict resolution, and release management. Use when working with Git repositories or when the user asks about version control best practices.

ownpilot/OwnPilot · 42 tokens

make-release

A release workflow for the Holix GitHub repository. It prepares a pull request, checks that automated tests pass, merges it, and creates the next numbered release.

javded-itres/Holix · 77 tokens

openakita/skills@changelog-generator

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Use this skill whenever the user mentions changelogs, release notes, version updates, "what changed", product updates, app…

openakita/openakita · 81 tokens