ClawHub is a public registry where OpenClaw users publish, version, search, and install text-based agent skills and OpenClaw packages. It provides web browsing, a CLI-oriented API, moderation, vector search, and artifact hosting for code plugins, bundle plugins, and experimental whole-agent packages. The catalogue skills and agents are entries that can be discovered or used through this registry.
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 openclaw/clawhub --skill clawhub-production-releasegit clone --depth 1 https://github.com/openclaw/clawhubWrote 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/openclaw/clawhub/clawhub-production-release)<a href="https://agentmods.dev/skills/openclaw/clawhub/clawhub-production-release"><img src="https://agentmods.dev/badge/skills/openclaw/clawhub/clawhub-production-release/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/openclaw/clawhub/clawhub-production-release"><img src="https://agentmods.dev/badge/skills/openclaw/clawhub/clawhub-production-release.svg" alt="Reviewed on agentmods" width="80" 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.00062 | $0.00955 |
| Opus 5 | $0.00031 | $0.00477 |
| Sonnet 5 | $0.00012 | $0.00191 |
| Haiku 4.5 | $0.00006 | $0.00096 |
Grade A, and why
clawhub-production-release 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 11d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ClawHub Production Release
ClawHub production changes are manual-only. Merging to main does not deploy
the app or publish the CLI.
Safety Rules
- Run production workflows from
main. - Re-read the workflow and exact
mainSHA immediately before dispatch. - Require a successful
Deploy Testworkflow for that exact SHA before dispatching an app production deploy. This is an operator check until the production workflow enforces the gate directly. - Do not treat a green workflow alone as proof. Record the workflow URL, exact deployed SHA, and live-surface verification.
- Do not add one-off migrations or repairs to the deploy workflow. Run
operator-controlled data changes separately with
clawhub-convexandcreate-and-cleanup-migration. - Never start a production deploy or npm publish unless the user explicitly asked for that release action.
App Production Deploy
The workflow is .github/workflows/deploy.yml.
- Confirm the selected commit is on
origin/mainand record its SHA. - Find the successful Test deployment for that exact SHA and record its URL:
gh run list \
--repo openclaw/clawhub \
--workflow deploy-test.yml \
--branch main \
--commit <MAIN_SHA> \
--status success \
--limit 1
If no successful exact-SHA Test run exists, stop and fix or rerun Test before releasing production.
- Run the required pre-merge or release validation for the changed surface.
- Dispatch one target:
gh workflow run deploy.yml \
--repo openclaw/clawhub \
--ref main \
-f target=full \
-f allow_deleting_large_indexes=false
Choose full, backend, or frontend:
full: deploy Convex, wait for the matching Vercel production deployment, and run production smoke checks.backend: deploy Convex and run production HTTP smoke checks.frontend: wait for Vercel's production deployment for the selectedmainSHA, then run HTTP and UI smoke checks. The workflow does not callvercel deploy.
Set allow_deleting_large_indexes=true only after reviewing the Convex index
deletion and explicitly accepting it.
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.
- 11d ago First seen · 117 lines · 62 tokens per session scan A b3a03f1ae819
clawhub-production-release is a skill published in the GitHub repository openclaw/clawhub (9,410 stars, last pushed today), licensed MIT. It adds 62 tokens to every session and 955 once invoked, about $0.0003 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
devops/changelog-generation
A method for creating a CHANGELOG, a document that records what changed in each software release. It reads Git commit history and release-pipeline reports, then groups changes using common commit and changelog conventions.
github-release-notes-writer
Draft or update user-focused GitHub Release Notes from verified tags, commits, pull requests, existing releases, and supplied changelog baselines. Use when preparing prerelease or stable release notes, turning GitHub's generated What's Changed list into a curated narrative, documenting upgrades or breaking changes, or…
github-release-pr-writer
Draft or update GitHub release pull request descriptions from verified tags, commits, merged pull requests, and the release diff. Use when a PR prepares a version, aligns release metadata, promotes a prerelease, or needs a reviewer-focused release summary, exact change inventory, breaking-change section, or migration…
otel-changelog-pr-verifier
Verify whether CHANGELOG entries in an OpenTelemetry Go repository point to the correct pull requests and whether each (#NNNN) matches the described change. Use when checking a release PR, validating a CHANGELOG section, or screening only mismatched changelog-to-PR references.
launch-and-growth
Get an open-source project in front of the people who need it, and keep them. Use when preparing to announce a project, writing a Hacker News or Reddit or Product Hunt post, planning a launch, writing a blog post about a release, improving GitHub discoverability (topics, About, social preview), or when the user asks…
release-engineering
Version, changelog, tag, and publish a release. Use when cutting a release, setting up automated publishing to npm/PyPI/crates.io/Maven/Homebrew, deciding whether a change is major/minor/patch, writing release notes, adopting conventional commits or changesets, planning a 1.0, or handling a bad release that needs to…