What is release-clawpatch?

A release checklist for publishing the clawpatch project as a public npm package. npm is the package registry commonly used to distribute JavaScript and Node.js software.

Use it to prepare, verify, commit, tag, and publish a clawpatch release while keeping registry credentials and one-time passwords private.

It reduces release mistakes by checking the version, changelog, repository state, authentication, tests, build, package contents, and publication steps.

release-clawpatch — Skill by openclaw

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.

agentmods

npx agentmods add skills/openclaw/clawpatch/release-clawpatch

Any agent

npx skills add openclaw/clawpatch --skill release-clawpatch

Clone the repo

git clone --depth 1 https://github.com/openclaw/clawpatch

Made for: Claude Code, Codex.

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

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

Security scan A 0 findings. Scan, not verified.

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	$0.00025	$0.01144
Opus 5	$0.00013	$0.00572
Sonnet 5	$0.00005	$0.00229
Haiku 4.5	$0.00003	$0.00114

Measured yesterday against content hash 07905df0bf8e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

release-clawpatch 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 yesterday.

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/release-clawpatch/SKILL.md · 86 lines

How it starts

The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Clawpatch Release

Scope

Release ~/Projects/clawpatch as the public npm package clawpatch.

Use $npm and $one-password rules for registry auth. Keep all op and npm secret work inside one persistent tmux session and temp npmrc. Never print tokens, passwords, or OTPs.

Workflow

Start clean on main.
- cd ~/Projects/clawpatch
- git status --short --branch
- git pull --ff-only
- Confirm target version is not already tagged or released: git tag --list "vX.Y.Z" and gh release view vX.Y.Z --repo openclaw/clawpatch.
- Confirm npm state: npm view clawpatch version dist-tags time --json.
Prep release files.
- Set package.json version to target.
- Change top changelog section from Unreleased to X.Y.Z - YYYY-MM-DD.
- Ensure release notes are the changelog body for that version and include all user-facing changes.
- Run pnpm install --lockfile-only; commit lockfile only if it actually changes.
Prove locally before publishing.
- Run pnpm typecheck && pnpm lint && pnpm format:check && pnpm test && pnpm build && pnpm pack:smoke.
- Fix failures before continuing.
Commit and push release prep.
- Commit with committer "chore(release): X.Y.Z" CHANGELOG.md package.json [pnpm-lock.yaml].
- git push origin main.
- Watch CI/CodeQL for the release commit:
  - gh run list --repo openclaw/clawpatch --branch main --commit <sha> --json databaseId,workflowName,status,conclusion,url,headSha
  - gh run view <run_id> --repo openclaw/clawpatch --json status,conclusion,url,jobs
- Do not publish until release-commit CI and CodeQL are green.
Publish npm.
- Use a temp npmrc, never the default user npmrc.
- First try npm whoami; if unauthenticated, use npm web login in the tmux session:
  - NPM_CONFIG_USERCONFIG="$tmp_npmrc" npm login --auth-type=web --registry=https://registry.npmjs.org/
  - Open/approve browser login if prompted.
- For publish, fetch a fresh OTP from the npmjs 1Password item inside the same tmux session.
- Publish with NPM_CONFIG_USERCONFIG="$tmp_npmrc" npm publish --access public --otp "$NPM_OTP".
- Clean temp npmrc/work dirs after publish.
- If publish says the version already exists, verify npm metadata and continue only if it matches the release commit/package contents.

Read the full file on GitHub · 86 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 206 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.

yesterday First seen · 86 lines · 25 tokens per session scan A 07905df0bf8e

Subscribe to this mod's changes

release-clawpatch is a skill published in the GitHub repository openclaw/clawpatch (810 stars, last pushed 4d ago), licensed MIT. It adds 25 tokens to every session and 1,144 once invoked, about $0.0001 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.

Code review Git and workflow Languages bot review

local-clawsweeper-review

Run local ClawSweeper exact-item or committed-range reviews without GitHub mutation.

openclaw/clawsweeper · 24 tokens

crabbox

Use the Crabbox wrapper for validation across Linux, macOS, Windows, and WSL2, including delegated Blacksmith Testbox proof. Report the actual provider and id.

openclaw/clawsweeper · 39 tokens

binance-tokenized-securities-info

Query Ondo tokenized US stock data on Binance Web3. Covers: supported stock token list, RWA metadata (company info, attestation reports), market and per-asset trading status (with corporate action codes for earnings, dividends, splits), real-time on-chain data (token price, holders, circulating supply, market cap), US…

ccxt/ccxt · 216 tokens

ccxt-csharp

CCXT cryptocurrency exchange library for C# and .NET developers. Covers both REST API (standard) and WebSocket API (real-time). Helps install CCXT, connect to exchanges, fetch market data, place orders, stream live tickers/orderbooks, handle authentication, and manage errors in .NET projects. Use when working with…

ccxt/ccxt · 94 tokens

new-exchange

Scaffold a new CCXT exchange integration in TypeScript, following the certified-exchange template. Walks through describe(), required unified methods, parsers, capability flags, sandbox setup, and static fixtures. Use when adding support for an exchange that does not exist yet under ts/src/.

ccxt/ccxt · 61 tokens

fiat

Query Binance fiat payment capabilities — supported countries, currencies, payment methods, limits, and crypto prices — via public APIs, plus authenticated order/payment history lookup. Use whenever users ask about buying or selling crypto with fiat, depositing or withdrawing fiat, fiat-crypto exchange rates, payment…

ccxt/ccxt · 79 tokens