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 convex-check-updatesgit 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/convex-check-updates)<a href="https://agentmods.dev/skills/openclaw/clawhub/convex-check-updates"><img src="https://agentmods.dev/badge/skills/openclaw/clawhub/convex-check-updates/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/convex-check-updates"><img src="https://agentmods.dev/badge/skills/openclaw/clawhub/convex-check-updates.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.00026 | $0.00365 |
| Opus 5 | $0.00013 | $0.00182 |
| Sonnet 5 | $0.00005 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
convex-check-updates scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
1. Run `curl -fsSL https://graceful-tiger-715.convex.site/check-updates.mjs -o /tmp/cu.mjs && node /tmp/cu.mjs` from the project root. What it actually says
check-updates
Detect stale Convex components in the current app against the anteater registry and, with explicit user consent, upgrade them one at a time behind a build gate (typecheck + next build). Each upgrade is gated and smoke-tested before the next.
Workflow
- Run
curl -fsSL https://graceful-tiger-715.convex.site/check-updates.mjs -o /tmp/cu.mjs && node /tmp/cu.mjsfrom the project root. - If COMPONENTS_UP_TO_DATE: tell the user; done.
- If COMPONENTS_STALE=: list each stale entry (component name, installed → current, summary, breaking flag) and ask the user before touching anything.
- On yes: install the new ref, apply each migration.steps change (delegate convex/ edits to convex-expert), run every migration.gate command.
- If any gate command fails: revert (git checkout -- . or reinstall old ref) and report; never leave the app half-migrated.
- Give the user the smoke check (migration.smoke) to run after each successful upgrade.
- Repeat for each stale component, one at a time.
Rules
- Never upgrade without an explicit user yes — not even a minor version.
- Gate each component individually before moving to the next.
- breaking:true upgrades require a snapshot (commit or branch) before applying.
- Do not auto-republish a live *.convex.app site after upgrading without user confirmation.
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.
- 9d ago First seen · 28 lines · 26 tokens per session scan A 11b4cc846610
convex-check-updates is a skill published in the GitHub repository openclaw/clawhub (9,407 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 365 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
api-and-namespace-design
API design conventions, namespace coordinate system, RBAC roles, ClawHub compatibility layer, OpenAPI contract sync rules, and CSRF/session handling.
backend-module-structure
Rules for the SkillHub backend Maven multi-module clean architecture. Ensures agents place new code in the correct module and respect dependency direction.
add-backend
Guide for adding a backend (Rust or Python) to the agent-sec-core security middleware. Use when creating new backends, integrating Rust or Python code into the security middleware, or extending with new backend actions.
backend/testing-guide
A guide for writing backend tests: small unit tests, tests that check connected parts such as an API and database, and end-to-end tests that follow a complete user flow.
architect/architecture-design
A guide to planning how a software system is organized, including its major parts, layers, folders, data, and API interfaces.
architect/data-api-design
A guide to designing data models and application programming interfaces (APIs), which are the rules software uses to exchange data.