AlphaClaw is a browser-based management layer for OpenClaw, an AI-agent gateway, that guides setup and monitors running agents. It helps users configure multiple agents, manage integrations, recover gateway failures, and observe activity from one dashboard.
Borrowing it
Nothing to install: this file belongs to chrysb/alphaclaw. 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/chrysb/alphaclaw/main/.agents/skills/release-publish/SKILL.mdgit clone --depth 1 https://github.com/chrysb/alphaclawWrote 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/chrysb/alphaclaw/release-publish)<a href="https://agentmods.dev/skills/chrysb/alphaclaw/release-publish"><img src="https://agentmods.dev/badge/skills/chrysb/alphaclaw/release-publish.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00072 | $0.02448 |
| Opus 5 | $0.00036 | $0.01224 |
| Sonnet 5 | $0.00014 | $0.00490 |
| Haiku 4.5 | $0.00007 | $0.00245 |
Grade A, and why
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 8d 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Publish
End-to-end workflow for publishing an AlphaClaw release. Produces release notes in the OpenClaw release format, publishes to npm, creates a GitHub release, closes addressed issues, and drafts a tweet.
Workflow
Phase 1: Gather History
- Identify the previous stable tag (
git tag --sort=-v:refname). - Determine the target version. If on a beta prerelease, the stable version is
the base (e.g.
0.6.0-beta.3→0.6.0). Confirm with the user if unclear. - Collect all commits since the last stable tag:
git log v<prev>..HEAD --oneline --no-merges git log v<prev>..HEAD --no-merges --format="----%nCommit: %h%nSubject: %s%n%b" - Identify external contributors:
git log v<prev>..HEAD --all --format="%an" | sort | uniq -c | sort -rn - Find merged PRs and contributor credits:
git log v<prev>..HEAD --all --merges --format="%s" - Check open issues on the repo that may be addressed:
Cross-reference issue descriptions against the commit log to identify fixes.gh issue list --repo chrysb/alphaclaw --state open
Phase 2: Draft Release Notes
Present a draft to the user before publishing. Use this structure:
## AlphaClaw <version>
### What's New
* **Feature name**: concise description of what it does and why it matters.
### Fixes
* **Short label**: what was broken and how it's fixed. Reference issues
(`Fixes #N`) and PRs (`(#N)`) inline. Credit external contributors
(`Thanks @handle.`).
### Contributors
* @handle
Style rules
- Each bullet starts with a bold short label followed by a colon.
- Describe the what and why, not the implementation details.
- Keep What's New and Fixes user-facing: describe behavior, not code structure (no "decomposed into folder-based components", "co-located hooks", etc.). Omit implementation-only changes from the release notes.
- Use active voice ("add", "fix", "remove"), not past tense.
- Reference GitHub issues with
Fixes #N(auto-closes) or#N(link only). - Reference PRs with
(#N). - Credit external contributors with
Thanks @handle.at the end of the bullet. - List all credited contributors in a Contributors section at the bottom.
- Fold reverted commits into their replacement — don't list revert + re-land.
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.
- 8d ago First seen · 251 lines · 72 tokens per session scan A 5c8c03a0fcb2
release-publish is a skill published in the GitHub repository chrysb/alphaclaw (1,474 stars, last pushed 5d ago), licensed MIT. It adds 72 tokens to every session and 2,448 once invoked, about $0.0004 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
draft-release-notes
Author the committed release-notes file for a Prisma 8 release (stable or 8.0.0-rc.N) by enumerating the merged PRs since the previous release v tag (stable or -rc.N), resolving opaque TML-NNNN: titles via Linear context (never copied verbatim), triaging public-worthiness, and writing categorized notes — breaking…
publish-npm-version
Cuts the next release of Prisma 8: bumps the root package.json version (on the v8 RC line: 8.0.0-rc.N → rc.N+1), propagates it to every workspace package, and opens a PR titled "chore(release): bump to ". When the maintainer merges the PR, the Publish to npm workflow runs automatically and ships the new version to npm…
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…
github-repo-management
Clone, create, fork, configure, and manage GitHub repositories. Manage remotes, secrets, releases, and workflows. Works with gh CLI or falls back to git + GitHub REST API via curl.
install
This skill should be used when the user asks to "install pikiclaw", "build and install", "deploy locally", "update local binary", "release", or "publish".
publish-plugins
(project) Use when editing any file under skills/ or plugins/ to bump the plugin version and check the manifests.