actions

A command group for Crabbox that prepares a leased remote machine using the setup workflow from a repository's GitHub Actions configuration. GitHub Actions is GitHub's system for running automated build and deployment jobs.

In plain words
What is it for?
Use it to hydrate a leased box locally over SSH or through a GitHub self-hosted runner, register the runner, and dispatch the setup workflow.
Why use it?
It lets the machine use the repository's normal setup process before another command connects to it, including setups that need GitHub services or secrets.

Command

Install

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.

agentmods
npx agentmods add commands/openclaw/crabbox/actions
Clone the repo
git clone --depth 1 https://github.com/openclaw/crabbox
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,434 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.02434
Opus 5 $0.00000 $0.01217
Sonnet 5 $0.00000 $0.00487
Haiku 4.5 $0.00000 $0.00243

Measured yesterday against content hash ca2f70882fee, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

actions 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 yesterday.

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.

docs/commands/actions.md · 250 lines

How it starts

The opening of the file, as written. The whole thing — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.

actions

crabbox actions prepares a leased box from your repository's own GitHub Actions workflow, so repo-owned setup (toolchains, dependencies, caches, services) runs the same way CI does before crabbox run attaches.

Hydration has two modes:

  • Local hydration (default) runs the hydrate workflow over SSH on the leased box. Crabbox reads the workflow file from .github/workflows/, syncs the current checkout, executes supported setup steps in the persistent workspace, and waits for the ready marker. This path needs no GitHub repository write access.
  • GitHub runner hydration (--github-runner) registers the box as a self-hosted runner, dispatches the configured workflow with the canonical lease label, and waits for the workflow to write the marker. Use it when the workflow needs full GitHub Actions semantics — repository secrets, OIDC, service containers, or unsupported actions.

The companion commands actions register and actions dispatch expose the runner-registration and workflow-dispatch steps directly.

Subcommands

hydrate  --id <lease-id-or-slug> [--provider <provider>] [--target linux|macos|windows]
         [--windows-mode normal|wsl2] [--repo owner/name] [--workflow <file|name|id>]
         [--job <name>] [--ref <ref>] [--github-runner] [--wait-timeout 20m]
         [--keep-alive-minutes 90] [--reclaim] [--timing-json] [-f key=value] [--field key=value]

register --id <lease-id-or-slug> [--provider <provider>] [--target linux|macos|windows]
         [--windows-mode normal|wsl2] [--repo owner/name] [--name <runner-name>]
         [--labels <csv>] [--version latest] [--ephemeral=true] [--reclaim]

dispatch [--repo owner/name] [--workflow <file|name|id>] [--ref <ref>] [-f key=value] [--field key=value]

hydrate and register validate the current repo's lease claim before touching the box. Pass --reclaim to intentionally move a lease to the current repo. When local defaults point at another backend, repeat the same provider/target routing flags used to create the lease.

Read the full file on GitHub · 250 lines

Changes

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.

  1. yesterday First seen · 250 lines · 0 tokens per session scan A ca2f70882fee

Subscribe to this mod's changes

actions is a command published in the GitHub repository openclaw/crabbox (1,343 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,434 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.