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/claimsgit 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.00651 |
| Opus 5 | $0.00000 | $0.00326 |
| Sonnet 5 | $0.00000 | $0.00130 |
| Haiku 4.5 | $0.00000 | $0.00065 |
Grade A, and why
claims 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
claims
crabbox claims list prints the lease claims stored on the current machine. It
is a read-only, credential-free inventory: it does not load provider
configuration, initialize a provider backend, contact a provider, refresh a
claim, or remove stale state.
crabbox claims list
crabbox claims list --json
Human output is headed unverified local state because a structurally valid
claim may be stale. Provider-scoped crabbox list remains the command
for provider-backed machine inventory.
JSON
--json emits this versioned envelope, including empty arrays when no claims or
problems exist:
{
"version": 1,
"source": "local-claims",
"claims": [],
"problems": []
}
Each claim contains only these public fields:
{
"leaseId": "cbx_abcdef123456",
"slug": "blue-lobster",
"provider": "aws",
"repoRoot": "/path/to/repo",
"pond": "",
"targetOS": "linux",
"windowsMode": "",
"claimedAt": "2026-08-16T10:00:00Z",
"lastUsedAt": "2026-08-16T10:05:00Z",
"idleTimeoutSeconds": 1800
}
Cloud and resource identifiers, provider scope, hosts and endpoints, SSH details, labels, login and registration URLs or IDs, credentials, cache metadata, revisions, and fixed-create internals are never included. Claims are sorted by lease ID, provider, and slug.
Malformed files do not hide valid claims. For this read-only inventory, each
local claim file has an inclusive 1 MiB implementation limit. Files that exceed
the limit while being read use claim_too_large and are never read into memory
in full; other concurrent changes remain read_error. This inventory limit does
not change the runtime claim loader. Each problem has stable file, code, and
message fields. Supported codes are
invalid_filename, invalid_json, claim_too_large, empty_lease_id,
lease_id_mismatch, read_error, and invalid_claim. Unsafe or overlong
filenames are represented by a short SHA-256 fingerprint instead of their
contents. Non-regular claim paths use non_regular_file. At most 100 problem
entries are emitted; the final
problems_truncated entry reports when additional files were omitted. Problems
are sorted by file reference and code.
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 · 80 lines · 0 tokens per session scan A a250a8f9acb6
claims 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 651 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
git
Git operations with intelligent commit messages and workflow optimization.
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.