ClawSweeper is a maintenance bot for OpenClaw repositories that periodically reviews open issues and pull requests and identifies candidates for closure, repair, or guarded automerging. It is intended for repository maintainers running their own configured instance. The catalogue entries are skills and an instruction for its review and maintenance workflows.
Borrowing it
Nothing to install: this file belongs to openclaw/clawsweeper. 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/openclaw/clawsweeper/main/.agents/skills/crabbox/SKILL.mdgit clone --depth 1 https://github.com/openclaw/clawsweeperWrote 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/clawsweeper/crabbox)<a href="https://agentmods.dev/skills/openclaw/clawsweeper/crabbox"><img src="https://agentmods.dev/badge/skills/openclaw/clawsweeper/crabbox/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/clawsweeper/crabbox"><img src="https://agentmods.dev/badge/skills/openclaw/clawsweeper/crabbox.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Privilege Escalation · line 605 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
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.00039 | $0.09814 |
| Opus 5.5 | $0.00016 | $0.03926 |
| Sonnet 5.5 | $0.00008 | $0.01963 |
| Haiku 4.5 | $0.00004 | $0.00981 |
Grade B, and why
crabbox scanned grade B 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 2mo 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo ln -sf \"\$PWD/<cli-entry>\" /usr/local/bin/<expected-command> How it starts
The opening of the file, as written. The whole thing — 860 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Crabbox
Provider Selection Contract
Provider selection is configuration resolution, not testing policy. Run
crabbox config show from the exact worktree being tested; a session may have
started in another checkout whose repository config or skill text is stale. A
request to "use Crabbox" does not authorize a provider override. When the user
does not name a backend, omit --provider and preserve the resolved provider,
including values supplied by user config or CRABBOX_PROVIDER.
Test scope, expected duration, and hydration failures do not select a provider. Override the resolved provider only when the user explicitly names a different backend. If that provider cannot perform the requested test, report the blocker instead of silently selecting another backend.
Use the Crabbox wrapper for validation execution, environment lifecycle, sync, logs/results, cache inspection, and lease cleanup.
Crabbox is the transport/orchestration surface. The actual backend can be:
- local Docker isolation:
provider=local-container, lease ids likecbx_... - brokered AWS Crabbox: direct provider,
provider=aws, lease ids likecbx_...,syncDelegated=false - Blacksmith Testbox through Crabbox: delegated provider,
provider=blacksmith-testbox, ids liketbx_...,syncDelegated=true
The provider-specific sections below document capabilities and commands after
configuration or an explicit user request has selected a backend. They are not
provider-selection policy. Their validation commands intentionally omit
--provider; add it only to carry out an explicit user override of the resolved
configuration.
Provider identity must remain attached to a lease after creation. A lease created through the resolved configuration can keep using provider-neutral commands while that configuration is unchanged. If the user explicitly overrode the provider, or the resolved configuration has changed since the lease was created, pass the provider reported by Crabbox to every later command that targets that lease, including hydrate, rerun, desktop/WebVNC, status, inspect, SSH, and stop. This preserves resource identity; it does not select a provider for unrelated work.
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.
- 2mo ago First seen · 860 lines · 39 tokens per session scan B 9196381cb2ad
crabbox is a skill published in the GitHub repository openclaw/clawsweeper (2,004 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 9,814 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
quality-gate
Orchestrates the QUALITY pipeline stage for egregore work items, running code review, unbloat, and test updates. Use when running quality checks before a PR.
plugin-review
Review plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits.
afrexai-api-architect
Design, build, test, document, and secure production-grade APIs. Covers the full lifecycle from schema design through deployment, monitoring, and versioning. Use when designing new APIs, reviewing existing ones, generating OpenAPI specs, building test suites, or debugging production issues.
afrexai-react-production
Complete methodology for building production-grade React applications with architecture decisions, component design, state management, performance optimization, testing, and deployment.
Vibe Coding Mastery
The complete operating system for building software with AI. From first prompt to production deployment — prompting frameworks, architecture patterns, testing strategies, debugging playbooks, and production graduation checklists. Works with Claude Code, Cursor, Windsurf, Copilot, and any AI coding tool.
arxiv-agentic-verifier
Source Paper: Scaling Agentic Verifier for Competitive Coding (ID: 4a4c4dae6a5145ebc4d62eb2d64b0f0f) Type: Code Verification / Test Generation.