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/logoutgit 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.00507 |
| Opus 5 | $0.00000 | $0.00253 |
| Sonnet 5 | $0.00000 | $0.00101 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
logout 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
logout
crabbox logout clears the stored broker token from your user config so the CLI
no longer authenticates to the broker.
crabbox logout
crabbox logout --json
What it changes
Logout edits only the user config file (the path printed by
crabbox config path). It clears both token fields the broker
reads:
- the broker section's
token, and - the top-level
coordinatorToken.
Everything else is left in place:
- the broker
urlandprovider, so a latercrabbox logincan reuse the configured endpoint; - the broker admin token (
broker.adminToken), if one is stored — logout does not touch it; - per-lease SSH keys, repo claims, and recorded run history.
On success it prints:
logged out config=/path/to/config.yaml broker_auth=missing
With --json it emits the resolved config path and the new auth state:
{ "config": "/path/to/config.yaml", "brokerAuth": "missing" }
Flags
| Flag | Description |
|---|---|
--json |
Print machine-readable JSON. |
After logout
- Broker-backed commands such as
crabbox whoami,crabbox run, andcrabbox warmupfail to authenticate against the broker because no token is sent. Re-runcrabbox login(orcrabbox login --token-stdin) to restore access. - Direct-provider mode keeps working when local provider credentials are present
(for example AWS SDK credentials or
HCLOUD_TOKEN), since direct mode talks to the cloud API and does not need a broker token.
When to use it
- A token has leaked or you want to rotate it.
- You are switching the operator identity on a shared workstation.
- You are exercising the unauthenticated path.
To remove everything — broker URL, provider, both tokens, and profile defaults — edit the user config file directly.
Related
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 · 72 lines · 0 tokens per session scan A 4e1d8ec7242f
logout 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 507 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.