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/logingit 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.00939 |
| Opus 5 | $0.00000 | $0.00469 |
| Sonnet 5 | $0.00000 | $0.00188 |
| Haiku 4.5 | $0.00000 | $0.00094 |
Grade A, and why
login 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
login
crabbox login authenticates the CLI against a coordinator, stores the
resulting credentials in your user config, and verifies them with
GET /v1/whoami. The coordinator may run on Cloudflare or Node/PostgreSQL.
There is no built-in hosted broker. You must supply a broker URL with --url, or
have one already configured (crabbox config set-broker). Without a broker, the
command exits with an error.
Usage
crabbox login --url <broker-url>
This starts a GitHub OAuth login: Crabbox opens the login URL in your browser and
listens on a random 127.0.0.1 port for a one-use browser confirmation. The
broker releases the user-scoped bearer token only when the initiating terminal
presents both that confirmation and its private polling secret.
If the browser cannot open automatically, print the URL and open it manually in a browser on the same device. Cross-device completion intentionally fails closed because the browser must return to the initiating CLI's loopback listener:
crabbox login --url https://broker.example.com --no-browser
On success the command prints the resolved broker, default provider, GitHub identity, and the config path it wrote:
logged in broker=https://broker.example.com provider=aws [email protected] org=example-org config=/Users/alice/.config/crabbox/config.yaml
Flags
--url <url> broker URL (falls back to the configured broker)
--provider aws|azure|daytona|gcp|hetzner default managed provider to store with the broker
--no-browser print the same-device GitHub login URL instead of opening it
--token-stdin read a broker token from stdin (operator automation)
--json print machine-readable JSON
When --url is omitted, the configured broker URL is used; --provider likewise
falls back to the configured default provider when unset.
Operator automation with --token-stdin
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 · 110 lines · 0 tokens per session scan A b47fa2088120
login 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 939 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.