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-pr-maintainergit 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-pr-maintainer)<a href="https://agentmods.dev/skills/openclaw/clawhub/clawhub-pr-maintainer"><img src="https://agentmods.dev/badge/skills/openclaw/clawhub/clawhub-pr-maintainer/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-pr-maintainer"><img src="https://agentmods.dev/badge/skills/openclaw/clawhub/clawhub-pr-maintainer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 48 Skill instructs the agent to never refuse or to always comply. Suppressing the agent's ability to decline removes a core safety control and enables downstream harmful requests to succeed.Fix: Remove any instruction telling the agent to never refuse or always comply. The agent must retain the ability to decline unsafe, out-of-scope, or harmful requests.
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.00050 | $0.02158 |
| Opus 5.5 | $0.00020 | $0.00863 |
| Sonnet 5.5 | $0.00010 | $0.00432 |
| Haiku 4.5 | $0.00005 | $0.00216 |
Grade A, and why
clawhub-pr-maintainer 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 1mo 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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ClawHub PR Maintainer
Use this skill for maintainer-facing ClawHub GitHub workflow, not for ordinary implementation work.
Start With Live GitHub State
- Use
gh pr vieworgh issue viewagainstopenclaw/clawhub; verify live state before commenting, labeling, closing, or recommending merge. - For PRs, read title, body, author, labels, comments, files, commits, status checks, review state, and linked issues.
- Surface author identity briefly: GitHub name/login and account age when useful. Treat identity as triage signal, never as proof by itself.
Common read-only commands:
gh pr view <number> --repo openclaw/clawhub --json title,body,author,labels,comments,files,commits,statusCheckRollup,reviewDecision,url,additions,deletions,changedFiles
gh issue view <number> --repo openclaw/clawhub --json title,body,author,labels,comments,state,url
gh api users/<login> --jq '{login,name,created_at,type}'
Review Evidence Bar
- For bug fixes, require symptom evidence, a plausible root cause in the touched code path, and either a regression test or focused manual proof.
- For UI changes, require screenshots or video when the behavior is meaningfully visual. Use tests as supplemental evidence, not a substitute for visible proof.
- Do not merge or recommend merge based only on PR prose, AI rationale, or green CI when the changed behavior has not been exercised.
- For contributor-provided screenshots/videos/logs, inspect the artifact
directly and state what it proves. Do not rerun
proof:uijust to inspect existing evidence.
Structure PR Review Output
- Start every PR review with 1-3 plain sentences explaining what the change does and why it matters.
- Show size near the top as
LOC: +x/-y (N files), using live PR stats or local diff stats. - Then list findings first. If none, say
No blocking findingsorNo findings. - Always answer: affected ClawHub surface, bug or behavior being changed, evidence checked, and best-fix verdict.
- For bug/regression fixes, include a compact
Provenance:line when a bounded history pass identifies it. Separate code author, PR author, merger/committer, current PR author, PR number, and date when those differ. If the blamed PR was merged by automation, identify the human trigger when practical; otherwise say trigger unknown.
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.
- 1mo ago Changed · -3 lines 9fcd404fe50b
- 2mo ago First seen · 206 lines · 50 tokens per session scan A 6bcbd6a6471f
clawhub-pr-maintainer is a skill published in the GitHub repository openclaw/clawhub (9,547 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 2,158 once invoked, about $0.0002 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.
clawhub-pr-maintainer compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| clawhub-pr-maintaineropenclaw/clawhub | Skill | 9.5k | today | MIT | A | 50 | Claude Code, Codex |
| adversarial-reviewiflytek/skillhub | Skill | 5.4k | yesterday | Apache-2.0 | A | 203 | Claude Code, Codex |
| mindosGeminiLight/MindOS | Skill | 704 | 14d ago | MIT | A | 136 | Claude Code |
| tech-lead/code-reviewechoVic/boss-skill | Skill | 547 | 5d ago | MIT | A | 52 | Claude Code |
| ultra-graph-theory8b-is/smart-tree | Skill | 272 | yesterday | MIT | A | 107 | Claude Code |
| superlintmgechev/skillgrade | Skill | 735 | 26d ago | MIT | A | 0 | Claude Code, Codex |
| pr-bodyalibaba/anolisa | Skill | 603 | 1mo ago | Apache-2.0 | A | 68 | Claude Code, Codex |