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/historygit 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/history)<a href="https://agentmods.dev/commands/openclaw/crabbox/history"><img src="https://agentmods.dev/badge/commands/openclaw/crabbox/history.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 | $0.00000 | $0.00579 |
| Opus 5 | $0.00000 | $0.00290 |
| Sonnet 5 | $0.00000 | $0.00116 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
history 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 4d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
history
crabbox history lists recorded remote command runs from the broker. Each run is
created by crabbox run (and run-backed flows such as
crabbox job run or capsule replay) and persists its state, phase,
exit code, duration, and telemetry on the coordinator. This command requires a
configured broker; without one it returns an error.
crabbox history
crabbox history --lease cbx_0a1b2c3d4e5f
crabbox history --owner [email protected]
crabbox history --org example-org --json
crabbox history --state failed --limit 100
Flags
--lease <lease-id> Filter to runs on a single lease.
--owner <email> Filter to runs owned by an email.
--org <name> Filter to runs scoped to an org.
--state <state> Filter by state: running, succeeded, or failed.
--limit <n> Maximum runs to return (default 50, broker-capped at 500).
--json Print the raw run records as JSON.
Output
The default output prints one line per run with the run ID, lease ID, lease slug, state, phase, exit code, duration, start time, an optional resource summary, and the executed command:
run_a1b2c3d4 cbx_0a1b2c3d4e5f swift-crab succeeded phase=command.finished exit=0 duration=42.1s started=2026-05-29T10:15:04Z resources=load=0.42 mem=38% disk=12% command=npm test
Missing values render as - (for example a still-running run has no exit code).
The resources=… segment appears only when a coordinator-backed Linux run
captured telemetry. --json emits the full run
records, including the start/end telemetry snapshots, JUnit result summaries, and
classification fields (blockedStage, retryLikely) when present.
Use a run ID from this list with logs, events, or
attach to inspect a specific run.
Related docs
- logs — print captured run logs.
- events — print phase and stream events.
- attach — follow a live run's events.
- results — parsed test-result summaries.
- History and logs — concept overview.
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.
- 4d ago First seen · 54 lines · 0 tokens per session scan A 60d0ddd1045a
history is a command published in the GitHub repository openclaw/crabbox (1,362 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 579 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.
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.