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/shardgit 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.01795 |
| Opus 5 | $0.00000 | $0.00898 |
| Sonnet 5 | $0.00000 | $0.00359 |
| Haiku 4.5 | $0.00000 | $0.00179 |
Grade A, and why
shard 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 3d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
shard
crabbox shard forks a checkpoint into --count leases
concurrently, runs the command on every fork in parallel through the normal
crabbox run pipeline, and merges the collected JUnit results into
one suite verdict. It is the parallel counterpart of
checkpoint fork --count: the same fork flow and
{{index}}/{{total}}/{{lease}}/{{slug}} placeholders, but shards run at
the same time and their test results fold into
a single answer with one aggregate exit code.
crabbox shard --count 8 --from chk_abc123 --results-auto -- pnpm test -- --shard '{{index}}/{{total}}'
crabbox shard --count 4 --from chk_deps --junit junit.xml --fail-on-test-failures -- go test ./...
crabbox shard --count 3 --from chk_abc123 --fail-fast --quiet -- pnpm vitest --shard '{{index}}/{{total}}'
The command template owns the sharding: crabbox never splits tests itself.
--count is always explicit, the plan is printed before any lease is
provisioned, and a repo config cap (shard.maxCount) bounds what a checkout
may request. Requires an SSH lease provider that supports checkpoint fork;
delegated providers are rejected. Provider-native snapshot fan-out stays on
checkpoint fork --snapshot.
Lease lifecycle
Every shard forks its own lease from the checkpoint and runs with an injected
--id, so sync, history, logs, artifacts, and results behave exactly as for
run. Forks exist only for the duration of their shard: each lease is
released when its shard finishes, on failure, and on Ctrl-C, always with a
fresh context so cleanup survives cancellation. A shard that fails to
provision does not orphan its siblings; the others run to completion and
release normally. Pass --keep to retain all forked leases instead.
For a coordinator-managed brokered native checkpoint, each shard acquires its own short-lived, generation-bound use claim before provisioning. Claims renew while provider readiness is pending, complete independently after successful lease creation, and abort on cancellation or failure. Active claims block checkpoint expiry/deletion; only successful completion advances its coordinator-owned last-use time. Shards can hydrate the checkpoint directly from the coordinator if the local metadata cache is absent.
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.
- 3d ago First seen · 144 lines · 0 tokens per session scan A 9c2eccde6bb0
shard is a command published in the GitHub repository openclaw/crabbox (1,343 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,795 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.