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 agentmods add commands/openclaw/crabbox/cleanupgit clone --depth 1 https://github.com/openclaw/crabboxWhat 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.00000 | $0.01820 |
| Opus 5 | $0.00000 | $0.00910 |
| Sonnet 5 | $0.00000 | $0.00364 |
| Haiku 4.5 | $0.00000 | $0.00182 |
Grade A, and why
cleanup 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 2d 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cleanup
crabbox cleanup sweeps direct-provider machines and local provider state that
Crabbox created but no longer tracks. It is a safety net for direct (non-brokered)
mode only; brokered fleets manage expiry through the coordinator instead.
crabbox cleanup --dry-run
crabbox cleanup
crabbox cleanup --provider namespace-devbox --dry-run
crabbox cleanup --provider namespace-devbox
crabbox cleanup --provider hostinger --dry-run
crabbox cleanup --provider coder --dry-run
crabbox machine cleanup is preserved as a compatibility alias and behaves
identically.
Behavior
Cleanup refuses to run when a coordinator is configured:
machine cleanup is disabled when a coordinator is configured; coordinator TTL alarms own brokered cleanup
Sweeping provider resources behind a coordinator can race live brokered leases, so brokered expiry is owned entirely by the coordinator's TTL alarm. See Lifecycle cleanup.
What cleanup does depends on the selected provider:
- Direct cloud/VM and delegated providers with cleanup (for example
hetzner,aws,azure,gcp,proxmox,xcp-ng,hostinger,parallels,cloudflare,blaxel,local-container,multipass) enumerate the machines they own and decide, per machine, whether to delete it. hostingeris stop-only: cleanup skips VPSs that are not positively identified as Crabbox-owned and stops matching VPSs; it does not delete VPSs or cancel Hostinger subscriptions.blaxelstarts from local Blaxel claims scoped to the configured API URL and workspace, verifies remote ownership labels before deleting, and keeps missing claims unless--blaxel-forget-missingis explicitly set.namespace-devboxremoves only Crabbox-owned local Namespace SSH files; it does not delete remote Devboxes.namespace-instancedestroys only Namespace Compute instances carrying Crabbox ownership labels and an exact local claim for the same instance, tenant, and configured scope; labeled but unclaimed instances are skipped. Claims for instances already gone are removed.xcp-ngdeletes eligible VMs only when an exact local claim matches the normalized pool endpoint, account, lease, slug, and immutable VM UUID. Labeled but unclaimed or wrong-pool VMs are skipped, and failed deletion preserves the claim for a safe retry.vercel-sandboxsweeps only localvsbx_...claims in the configured project/team/scope. It deletes idle-expired Crabbox-owned Vercel Sandboxes and keeps missing-or-inaccessible claims unless--vercel-sandbox-forget-missingis explicit.cloudflare-dynamic-workerschecks local Dynamic Workers claims against the loader and removes only stale local claims whose loader metadata is missing or terminal. It does not enumerate or delete every Dynamic Worker in the Cloudflare account.cloudflare-sandboxsweeps only localcfsbx_...claims in the active provider scope. It deletes idle-expired Crabbox-owned sandboxes and keeps missing-or-inaccessible claims unless--cloudflare-sandbox-forget-missingis explicit.nomadsweeps only localcbx_...claims in the active Nomad namespace, region, and task scope. It deregisters idle-expired or TTL-expired Crabbox-owned jobs, removes stale local claims for missing jobs, and skips active claims.coderlists workspaces with Crabbox ownership evidence, such as the configured workspace prefix or Crabbox labels in Coder JSON, but mutates only workspaces that also have a local Crabbox claim with cleanup metadata. It uses the release action persisted in each local claim: new delete-on-release claims delete, stop-on-release claims stop, and older claims without that metadata default to stop.- Providers that have nothing to sweep return an error rather than acting. For
example
provider=ssh(static / bring-your-own hosts) reports:
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.
- 2d ago First seen · 178 lines · 0 tokens per session scan A 4eb644216521
cleanup is a command published in the GitHub repository openclaw/crabbox (1,343 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,820 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.