openclaw

An instruction set for installing and configuring Webcmd, a command-line tool for controlling browser-based work, for use with an OpenClaw agent.

In plain words
What is it for?
Use it to install Webcmd, check its requirements, add its skills, configure OpenClaw, and prepare browser automation.
Why use it?
It covers the setup details needed for the agent to handle dynamic websites that a basic page-fetching tool may not process correctly.

Agent

Part of the webcmd plugin — 1 skill, 10 agents shipped together

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 agents/agentrhq/webcmd/openclaw
Clone the repo
git clone --depth 1 https://github.com/agentrhq/webcmd

Or install webcmd, the plugin that ships this one along with the rest of its 1 skill, 10 agents.

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 1,018 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.01018
Opus 5 $0.00000 $0.00509
Sonnet 5 $0.00000 $0.00204
Haiku 4.5 $0.00000 $0.00102

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

Security

Grade A, and why

openclaw 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/agents/openclaw.md · 91 lines

How it starts

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

Agent prompt

Fetch and follow https://raw.githubusercontent.com/agentrhq/webcmd/main/start.md to set up Webcmd end to end.

Manual

Requirements

  • Node.js 20.6+
  • The webcmd npm CLI, installed globally or in the project
  • An OpenClaw Gateway + an agent session where exec is enabled
  • A browser runtime; confirm with webcmd doctor before browser work

Install and configure

Install Webcmd and its skills:

npm install -g @agentrhq/webcmd
webcmd doctor
webcmd skills add

When webcmd skills add prompts, choose the agents provider. It installs into ~/.agents/skills/ (user) or .agents/skills/ (project), both of which OpenClaw checks for skills. OpenClaw then surfaces webcmd-browser as a skill.

Restart the Gateway (or start a new session) after installing skills.

Override default tools

Deny web_fetch. It is an HTTP fetch with readable extraction and does not execute JavaScript, so it fails on exactly the dynamic sites Webcmd handles. In the Gateway config (~/.openclaw/openclaw.json):

{
  "tools": {
    "deny": ["web_fetch"]
  }
}

Keep the search toolsweb_search (backed by Brave, Gemini, Grok, Kimi, or Perplexity), x_search, and search_news. Webcmd has no search index of its own, so search stays the cheapest way to find URLs for Webcmd to read.

The browser tool is a single tool with subcommands (doctor, status, start, stop, tabs, open, focus, close, snapshot, screenshot, navigate, act). It reaches both localhost and the open web, so keep it for the app being edited and route open-web work to Webcmd. State that split in your OpenClaw system prompt or project instructions.

Worth raising with the user: OpenClaw's browser has a user profile that reuses their existing signed-in sessions, which overlaps directly with Webcmd's auth profiles. Its isolated openclaw profile does not.

The Gateway watches the config file and applies changes automatically. Denying these tools does not affect the exec tool, which is how webcmd is driven.

Read the full file on GitHub · 91 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 Changed · -1 lines b3f8cad01959
  2. 3d ago First seen · 92 lines · 0 tokens per session scan A d38a84e6b8a1

Subscribe to this mod's changes

openclaw is an agent published in the GitHub repository agentrhq/webcmd (1,558 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,018 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.