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 agents/atpaawej/openboard/openclawgit clone --depth 1 https://github.com/atpaawej/openboardWrote 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/agents/atpaawej/openboard/openclaw)<a href="https://agentmods.dev/agents/atpaawej/openboard/openclaw"><img src="https://agentmods.dev/badge/agents/atpaawej/openboard/openclaw.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00450 |
| Opus 5 | $0.00000 | $0.00225 |
| Sonnet 5 | $0.00000 | $0.00090 |
| Haiku 4.5 | $0.00000 | $0.00045 |
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 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.
What it actually says
OpenClaw Integration Guide
OpenClaw connects to external tools and environments using the Model Context Protocol (MCP) over stdio.
1. Installation
Install OpenBoard globally via npm:
npm install -g openboard
2. OpenBoard Startup
Start the local OpenBoard web dashboard and server:
openboard start
For AI agent operations via MCP, OpenClaw runs openboard mcp directly over stdio.
3. MCP Configuration
Configuration File (~/.openclaw/config.json)
Add OpenBoard under mcpServers in your OpenClaw configuration file:
{
"mcpServers": {
"openboard": {
"command": "openboard",
"args": ["mcp"]
}
}
}
4. Verification
Apply changes and verify tool registration:
openclaw gateway restart
openclaw mcp list
Verify that openboard is active and all 13 tools are available.
5. Example Workflows & Prompts
Multi-Step Deployment Topology Workflow
User:
List my OpenBoard whiteboards.
OpenClaw:
[Calls list_boards]
Found 2 boards: "Sprint Planning", "Deployment Architecture".
User:
Inspect the canvas on "Deployment Architecture".
OpenClaw:
[Calls get_canvas_state and get_canvas_screenshot on the target board]
Retrieved 5 shapes. Kubernetes cluster is currently disconnected from Redis.
User:
Connect the Kubernetes cluster to Redis with an arrow labeled "Cache Reads/Writes".
OpenClaw:
[Calls create_shapes with arrow binding from k8s_cluster to redis_cache]
Created arrow connecting Kubernetes to Redis with label "Cache Reads/Writes".
6. Troubleshooting
- Restart gateway: Always run
openclaw gateway restartafter editingconfig.json. - Binary discovery: Ensure
openboardis installed globally (npm install -g openboard). - Clean stdio: OpenBoard ensures stdout contains only JSON-RPC protocol frames.
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.
- 3d ago First seen · 95 lines · 0 tokens per session scan A 53428bb85060
openclaw is an agent published in the GitHub repository atpaawej/openboard (3 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 450 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 agents, from other repositories
sverklo-explore
Drop-in replacement for Claude Code's built-in Explore subagent. Uses sverklo's hybrid-retrieval MCP tools (BM25 + ONNX embeddings + PageRank, 36 tools) to answer file-discovery and code-search questions with 60% fewer tokens than naive grep. Use this when you need to locate definitions, trace references, understand…
brain-os-mode
Use for any Brain OS task delegated to a subagent — reading entity state, checking active decisions, running focus/patterns/retro analysis, or proposing changes that need to honor active decisions. Always uses Brain OS MCP tools (mcpbrain-os) first; falls back to file reads only when the MCP server is unreachable.…
engineer
Use this agent when you need to implement features, fix bugs, or write code anywhere in the Code Insights monorepo. This includes CLI commands, dashboard components (Vite + React SPA), Hono server routes, SQLite schema changes, provider implementations, LLM provider integration, UI work with shadcn/ui, and any…
technical-architect
Use this agent for architectural decisions, type alignment, SQLite schema changes, code review synthesis, and when the implementation path requires architectural guidance. This agent serves as the technical authority across the Code Insights monorepo. Examples: Context: A change to types needs to be reflected in the…
product-manager
Use this agent for product development coordination, tracking tasks (GitHub Issues or local markdown), sprint planning, progress reporting, and development ceremony management. This PM does NOT use Jira.
devtools-cofounder
Use this agent for strategic product decisions, competitive positioning, developer experience critique, go-to-market strategy, and feature viability assessment. Peer to technical-architect — brings market lens where TA brings system lens. Does NOT write code or create PRs. Advisory only — delegates implementation to…