unshare

A Crabbox command that revokes access previously granted to users or an organization on a shared remote lease.

In plain words
What is it for?
It can remove one or more users, organization-wide access, or all sharing rules by lease ID or slug.
Why use it?
It removes sharing rules when access should no longer be available, while requiring the appropriate lease permissions.

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/unshare
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 625 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.00625
Opus 5 $0.00000 $0.00313
Sonnet 5 $0.00000 $0.00125
Haiku 4.5 $0.00000 $0.00063

Measured 3d ago against content hash 092988c7d7a1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

unshare 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.

docs/commands/unshare.md · 69 lines

How it starts

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

unshare

crabbox unshare removes sharing rules from a coordinator-backed lease. It is the inverse of crabbox share: use it to revoke access you granted to individual users, to the lease's org, or to clear every rule at once.

Sharing lives on the broker, so unshare requires a configured coordinator. You must be the lease owner, hold a manage share on the lease, or use an admin session to change its sharing.

Usage

crabbox unshare --id swift-crab --user github:12345
crabbox unshare --id swift-crab --org
crabbox unshare --id swift-crab --all
crabbox unshare swift-crab --all --json

The lease is identified by --id (its cbx_… id or slug). As a convenience the first positional argument is treated as the id, so crabbox unshare swift-crab is equivalent to --id swift-crab.

You must pass at least one of --user, --org, or --all; otherwise the command exits with a usage error.

What each flag removes

  • --user <owner> revokes one owner's access. Repeat the flag to remove several users in a single call. Use github:<numeric-id> for GitHub users; values are matched case-insensitively.
  • --org removes org-wide access, so the lease is no longer shared with everyone in the owning org.
  • --all clears every sharing rule (all users and any org grant) in one step.

When --all is set the other selectors are ignored. Otherwise --user and --org can be combined to remove specific users and the org grant together.

Output

unshare prints the resulting sharing state after the change. The text form lists the org grant followed by each remaining user:

org=off
user=github:67890 role=use

role is use (run on the lease) or manage (run plus change sharing). org=off means no org-wide grant remains, and users=none is printed when no individual shares are left. Pass --json to emit the same state as a {"share": …} object for scripting.

Flags

--id <lease-id-or-slug>   Lease to modify (or pass as the first positional arg).
--user <owner>            Owner identity to remove; repeatable.
--org                     Remove the org-wide grant.
--all                     Remove every sharing rule.
--json                    Print the resulting share state as JSON.

Read the full file on GitHub · 69 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. 3d ago First seen · 69 lines · 0 tokens per session scan A 092988c7d7a1

Subscribe to this mod's changes

unshare 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 625 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.