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/jobgit 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.01368 |
| Opus 5 | $0.00000 | $0.00684 |
| Sonnet 5 | $0.00000 | $0.00274 |
| Haiku 4.5 | $0.00000 | $0.00137 |
Grade A, and why
job 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
job
Run named, repo-local jobs defined in your Crabbox config.
A job bundles lease routing, optional GitHub Actions hydration, a command, and a
cleanup policy under one name, then expands into the equivalent warmup,
actions hydrate, run, and stop commands at runtime. Crabbox owns lease
lifecycle, dirty-checkout sync, execution, timing/log output, and cleanup; the
repository owns the command string, toolchain setup, test environment, and
workflow names.
For the concept and authoring guidance, see jobs.
Subcommands
| Command | Description |
|---|---|
crabbox job list |
List configured jobs and their key routing fields. |
crabbox job run <name> |
Run a configured job. |
Running crabbox job with no subcommand is equivalent to crabbox job list.
job list
crabbox job list
Prints each configured job, sorted by name, with its provider, target,
hydrate_actions, and stop policy. Prints no jobs configured when the
merged config defines no jobs.
job run
crabbox job run <name>
crabbox job run --dry-run <name>
crabbox job run --id <lease-or-slug> <name>
crabbox job run --stop never <name>
crabbox job run --github-runner <name>
job run takes exactly one positional argument: the job name. The job must
exist in the merged config and must define a command (or set syncOnly).
When --id is omitted, job run first creates a lease (via warmup --keep)
using the job's routing fields, then runs the job against it. When --id is
supplied, the job runs against that existing lease.
Blacksmith Testbox does not support noSync: true. Such jobs exit 2 before
warmup, hydration, run, or stop, without generating keys or changing claims.
This also applies to --dry-run and existing leases. Omit noSync (or set it
to false) to let Blacksmith manage source sync, or choose a provider that
supports skipping sync. Job provider overrides and existing-lease routing
determine which provider's policy applies.
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 · 149 lines · 0 tokens per session scan A 4fc07b2b255a
job 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,368 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.