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/imagegit 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.03703 |
| Opus 5 | $0.00000 | $0.01852 |
| Sonnet 5 | $0.00000 | $0.00741 |
| Haiku 4.5 | $0.00000 | $0.00370 |
Grade B, and why
image scanned grade B with 2 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
crabbox run --id <slug> --shell -- 'command -v ssh git rsync curl jq && test -d /work/crabbox' Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
crabbox run --id <slug> --shell -- 'command -v ssh git rsync curl jq && test -d /work/crabbox' How it starts
The opening of the file, as written. The whole thing — 329 lines — stays where its author put it; the contents beside it link to each section on GitHub.
image
crabbox image holds the trusted-operator controls for provider base images:
creating runner images, promoting an AWS AMI or Azure OS disk snapshot as a
brokered default, inspecting Fast Snapshot Restore, and deleting stale images.
Use it for shared base images and explicit image cleanup, not for per-scenario
state. To save one prepared lease and fork that exact scenario later, use
crabbox checkpoint.
crabbox image create --id cbx_... --name my-runner-20260501-1246 --wait
crabbox image promote ami-1234567890abcdef0
crabbox image promote ami-1234567890abcdef0 --target macos --region us-east-1 --type mac2.metal
crabbox image promote snapshot-devtools --provider azure --target linux --region westeurope
crabbox image fsr-status ami-1234567890abcdef0 --region us-west-2 --fsr-az us-west-2a
crabbox image delete ami-1234567890abcdef0 --region eu-west-1
crabbox image delete ami-external --catalog-only
crabbox image delete ami-1234567890abcdef0 --retire-promotions --region eu-west-1
crabbox image delete prepared-snapshot --retire-promotions --provider azure --region westeurope
crabbox image delete my-managed-image --provider azure --region westeurope
crabbox image delete my-machine-image --provider gcp --region europe-west1-b --project example-project
crabbox image delete 123456789 --provider hetzner --region fsn1
Every image subcommand except direct Hetzner snapshot deletion requires a
configured coordinator (broker) and admin-token auth. Set broker.adminToken or CRABBOX_COORDINATOR_ADMIN_TOKEN
locally; the Worker validates it against CRABBOX_ADMIN_TOKEN. Without an admin
token the command exits early with admin command requires broker.adminToken or CRABBOX_COORDINATOR_ADMIN_TOKEN. These commands are intentionally unavailable
to normal GitHub browser-login users.
Image bytes live in the provider account, never in git or coordinator durable
state. AWS images are AMIs backed by EBS snapshots; Azure promotion uses
managed OS disk snapshots; GCP images are Compute Engine machine images.
Crabbox stores promoted AWS and Azure metadata in provider-specific scopes so
future brokered leases resolve a matching default. Hetzner snapshots/images live in the
Hetzner project and are selected through image/CRABBOX_HETZNER_IMAGE;
Crabbox has no Hetzner create/promote lifecycle commands. Direct native
checkpoints own the supported Hetzner snapshot creation and fork path.
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 · 329 lines · 0 tokens per session scan B a4b936700ca3
image 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 3,703 tokens. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). 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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.