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 skills/helixdata/gopherhole-clients/plugin-openclawnpx skills add helixdata/gopherhole-clients --skill plugin-openclawgit clone --depth 1 https://github.com/helixdata/gopherhole-clientsWhat 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.00854 |
| Opus 5 | $0.00000 | $0.00427 |
| Sonnet 5 | $0.00000 | $0.00171 |
| Haiku 4.5 | $0.00000 | $0.00085 |
Grade A, and why
plugin-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.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
A2A Channel Plugin
Enables Clawdbot to communicate with other AI agents via the A2A (Agent-to-Agent) protocol.
Overview
This plugin allows bidirectional communication between Clawdbot and other A2A-compatible agents (like MarketClaw). Messages flow both ways:
- Outbound: Clawdbot can send messages to connected agents
- Inbound: Other agents can send messages to Clawdbot, which routes them through the normal reply pipeline
Configuration
Add to your Clawdbot config:
channels:
a2a:
enabled: true
agentId: nova # Our identifier (default: openclaw)
agentName: Nova # Display name
bridgeUrl: ws://localhost:8080/a2a # A2A bridge/hub (optional)
agents: # Direct agent connections (optional)
- id: marketclaw
url: ws://localhost:7891/a2a
name: MarketClaw
auth:
token: secret-token # Auth token (optional)
reconnectIntervalMs: 5000 # Reconnect delay (default: 5000)
requestTimeoutMs: 300000 # Request timeout (default: 5 min)
Protocol
Messages follow this format (compatible with MarketClaw's A2A implementation):
interface A2AMessage {
type: 'message' | 'response' | 'chunk' | 'status';
taskId: string; // UUID for request/response matching
contextId?: string; // Optional conversation thread
from?: string; // Sender agent ID
content?: {
parts: [{ kind: 'text', text: string }]
};
status?: 'working' | 'completed' | 'failed' | 'canceled';
error?: string;
}
Tool: a2a_agents
The plugin registers an a2a_agents tool for interacting with connected agents:
// List connected agents
{ action: 'list' }
// Returns: { agents: [{ id, name, connected }] }
// Send message to agent (MUST use full agent ID, not name!)
{ action: 'send', agentId: 'agent-70153299', message: 'What stocks are trending?' }
// Returns: { success: true, response: { text, status, from } }
⚠️ Agent ID Required
What ships with it
16 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- A2A-FIX-GUIDE.md 3.7 KB
- index.ts 9.1 KB runs code
- openclaw.plugin.json 4.6 KB
- package-lock.json 353 KB
- package.json 1.2 KB
- README.md 1.3 KB
- src/channel.ts 14 KB runs code
- src/connection.test.ts 8.0 KB runs code
- src/connection.ts 16 KB runs code
- src/gateway-client.ts 10 KB runs code
- src/logger.ts 3.0 KB runs code
- src/types.ts 1.7 KB runs code
- test-image.mjs 935 B runs code
- test-image2.mjs 1.3 KB runs code
- tsconfig.json 430 B
- vitest.config.ts 175 B runs code
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.
- yesterday First seen · 107 lines · 0 tokens per session scan A 285103e5bf1d
plugin-openclaw is a skill published in the GitHub repository helixdata/gopherhole-clients (1 stars, last pushed 23d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 854 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.