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 skills add CommonstackAI/ClawBox --skill clawbox-release-packaginggit 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-packaging)<a href="https://agentmods.dev/skills/commonstackai/clawbox/clawbox-release-packaging"><img src="https://agentmods.dev/badge/skills/commonstackai/clawbox/clawbox-release-packaging/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/skills/commonstackai/clawbox/clawbox-release-packaging"><img src="https://agentmods.dev/badge/skills/commonstackai/clawbox/clawbox-release-packaging.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.00085 | $0.00882 |
| Opus 5.5 | $0.00034 | $0.00353 |
| Sonnet 5.5 | $0.00017 | $0.00176 |
| Haiku 4.5 | $0.00009 | $0.00088 |
Grade A, and why
clawbox-release-packaging 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.
How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ClawBox Release Packaging
Use this skill when the task involves ClawBox versioning, Tauri configuration, backend binary packaging, sidecar lifecycle, or release build scripts.
Read first
package.jsondocs/releasing.md.github/release-notes-template.mddocs/releases/scripts/collect-release-assets.mjsscripts/release-version.mjsscripts/sync-version.mjsscripts/sign-win-installer.mjsscripts/build-backend.mjs.github/workflows/release.ymlsrc-tauri/tauri.conf.jsonsrc-tauri/Cargo.tomlsrc-tauri/src/lib.rsinternal/onboard/if the task also affects runtime bootstrap or environment setup
Workflow
- Identify which layer is changing: UTC version generation, version synchronization, Bun backend compile output, Tauri shell, release workflow guard, release-notes lookup, release-asset filtering, or installer/signing script.
- Preserve
package.jsonas the single source of truth for the app version. Any version automation must keeppackage-lock.json,src-tauri/tauri.conf.json, andsrc-tauri/Cargo.tomlaligned. - Keep the UTC date-based version format semver-safe. The current release flow uses
YYYY.M.D-N, withgit fetch --tagsplus localvYYYY.M.D-Ntags determining the next sequence. - Keep sidecar naming and resource lookup behavior aligned with
scripts/build-backend.mjsandsrc-tauri/src/lib.rs. - Keep Windows installer signing dynamic.
tauri:build-win:sign-installershould resolveClawBox_<version>_x64-setup.exefrompackage.json, not from a hard-coded filename. - Keep release publication scoped to user-facing assets only. The workflow should publish final
.dmg,.exe, and the combinedCHECKSUMS.txt, not the entire Tauri bundle tree. - Keep release notes lookup aligned with the documented flow. Hand-written notes live at
docs/releases/<tag>.md, with GitHub-generated notes as the fallback when the file is absent. - If the change touches release publication behavior rather than packaging/configuration, hand off to
clawbox-release-publishinstead of extending this skill. - If the change touches Windows signing or platform-specific installers, note any credentials or OS environments you could not validate.
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 · 55 lines · 85 tokens per session scan A 1dab7c7d5eb6
clawbox-release-packaging is a skill published in the GitHub repository CommonstackAI/ClawBox (22 stars, last pushed 6mo ago), licensed MIT. It adds 85 tokens to every session and 882 once invoked, about $0.0003 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.
Other skills, from other repositories
github
GitHub CLI for issues, PRs, CI/check logs, comments, reviews, releases, repos, and gh api queries.
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…
pm-release
A release-planning workflow for preparing software to go live, including checks, deployment choices, timing, and rollback conditions.
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.
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.
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…