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.
git clone --depth 1 https://github.com/TheophilusChinomona/claude-openclaw-pluginWrote 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/theophiluschinomona/claude-openclaw-plugin/oc-workspace)<a href="https://agentmods.dev/commands/theophiluschinomona/claude-openclaw-plugin/oc-workspace"><img src="https://agentmods.dev/badge/commands/theophiluschinomona/claude-openclaw-plugin/oc-workspace/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/theophiluschinomona/claude-openclaw-plugin/oc-workspace"><img src="https://agentmods.dev/badge/commands/theophiluschinomona/claude-openclaw-plugin/oc-workspace.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00013 | $0.01220 |
| Opus 5 | $0.00006 | $0.00610 |
| Sonnet 5 | $0.00003 | $0.00244 |
| Haiku 4.5 | $0.00001 | $0.00122 |
Grade A, and why
oc-workspace 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 10d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/oc-workspace Command
Manage multi-user workspace access — list approved users, handle pairing, check session isolation, and audit security.
Arguments
The user provides: $ARGUMENTS
Parse:
- subcommand (required):
users,pair,sessions, oraudit - channel (optional, for
pair): channel name likewhatsapp,telegram,slack
Subcommands
users
List all approved users across channels with their agent routing.
- Read allowlist files:
# Find all allowlist files
ls ~/.openclaw/credentials/*-allowFrom.json 2>/dev/null
- For each file, read and display approved senders:
cat ~/.openclaw/credentials/whatsapp-allowFrom.json 2>/dev/null
cat ~/.openclaw/credentials/telegram-allowFrom.json 2>/dev/null
- Get current bindings:
openclaw agents list --bindings
- Get DM policies:
openclaw config get channels
- Present a consolidated table:
Channel | DM Policy | Approved Users | Routed To
------------|------------|----------------|----------
whatsapp | pairing | +1555123... | family
telegram | allowlist | tg:111111111 | admin
| | tg:222222222 | team
pair [channel]
List and manage pending pairing requests.
- If a channel is specified:
openclaw pairing list <channel>
- If no channel specified, check all common channels:
openclaw pairing list whatsapp 2>/dev/null
openclaw pairing list telegram 2>/dev/null
openclaw pairing list discord 2>/dev/null
openclaw pairing list slack 2>/dev/null
openclaw pairing list signal 2>/dev/null
- Also check device pairing:
openclaw devices list 2>/dev/null
- Present pending requests with instructions:
Pending DM Pairing:
whatsapp: ABCD1234 from +15551230001 (3 min ago)
telegram: EFGH5678 from tg:999999999 (12 min ago)
Pending Device Pairing:
(none)
To approve: openclaw pairing approve <channel> <CODE>
To approve device: openclaw devices approve <requestId>
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.
- 10d ago First seen · 198 lines · 13 tokens per session scan A 659b37cddff9
oc-workspace is a command published in the GitHub repository TheophilusChinomona/claude-openclaw-plugin (2 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 1,220 once invoked, about $0.0001 per session on Opus 5. 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-31.
Other commands, from other repositories
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.