Crabbox is a remote execution control plane that lets a local command run on managed cloud capacity, an SSH host, or another delegated sandbox while syncing code, streaming output, and recording evidence. It is for maintainers, contributors, teams, AI agents, and automation that need repeatable remote testing, builds, browser checks, or platform-specific validation. The catalogue add-ons provide commands and instructions for controlling Crabbox runs.
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/whoamigit clone --depth 1 https://github.com/openclaw/crabboxWrote 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/commands/openclaw/crabbox/whoami)<a href="https://agentmods.dev/commands/openclaw/crabbox/whoami"><img src="https://agentmods.dev/badge/commands/openclaw/crabbox/whoami.svg" alt="Measured on agentmods" height="20"></a>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.00000 | $0.00733 |
| Opus 5 | $0.00000 | $0.00367 |
| Sonnet 5 | $0.00000 | $0.00147 |
| Haiku 4.5 | $0.00000 | $0.00073 |
Grade A, and why
whoami 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
whoami
crabbox whoami calls the broker's /v1/whoami endpoint and prints the
identity the coordinator resolved for your request. Use it to confirm broker
auth is working before starting any long-running workflow.
crabbox whoami
crabbox whoami --json
whoami requires a configured coordinator (broker URL plus a token). If none
is configured it fails with exit code 2 and the message
whoami requires a configured coordinator. See login and
config for how the broker URL and token are stored.
Flags
--json- print the raw coordinator response as JSON instead of the human-readable line.
whoami takes no positional arguments.
Human output
user=github:12345 org=example-org auth=github broker=https://broker.example.com
The fields:
user- the resolved owner identity, as the coordinator sees it.org- the organization namespace, when set (empty otherwise).auth- the auth mode the coordinator accepted:githubfor signed login tokens,bearerfor shared automation tokens.broker- the coordinator URL the CLI is configured to use. This is a local field added by the CLI from your config, not returned by the broker.
JSON output
{
"owner": "github:12345",
"org": "example-org",
"auth": "github"
}
The JSON form is exactly the coordinator's /v1/whoami response: owner,
org, and auth. The broker URL is not included in JSON output.
How identity is resolved
When you log in through the browser flow, the broker issues a signed user
token (prefix cbxu_) that embeds your immutable github:<numeric-id> owner and
allowed-org membership. A verified GitHub email remains an eligibility check,
not ownership. For requests carrying that token the coordinator derives
owner/org from the token itself and reports auth=github.
Shared bearer-token automation has no embedded identity, so the broker reads
owner/org from the X-Crabbox-Owner and X-Crabbox-Org request headers
and reports auth=bearer. The CLI fills those headers from, in order of
precedence:
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 · 92 lines · 0 tokens per session scan A dcf88adacbdd
whoami is a command published in the GitHub repository openclaw/crabbox (1,368 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 733 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-09-03.
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.