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/cursorgit clone --depth 1 https://github.com/atpaawej/openboardWhat 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.00731 |
| Opus 5 | $0.00000 | $0.00365 |
| Sonnet 5 | $0.00000 | $0.00146 |
| Haiku 4.5 | $0.00000 | $0.00073 |
Grade A, and why
cursor 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 2d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor IDE Integration Guide
Cursor supports Model Context Protocol (MCP) servers configured via JSON configuration files or Cursor Settings.
1. Installation
Install OpenBoard globally via npm:
npm install -g openboard
2. OpenBoard Startup
Launch the local OpenBoard web dashboard and server:
openboard start
For AI agent operations via MCP, Cursor executes openboard mcp directly over stdio.
3. MCP Configuration
Configuration File Setup
Cursor reads MCP server definitions from:
- Global Configuration:
~/.cursor/mcp.json - Project Configuration:
.cursor/mcp.json(inside project root)
Add the openboard server under mcpServers:
{
"mcpServers": {
"openboard": {
"command": "openboard",
"args": ["mcp"]
}
}
}
Cursor UI Setup
- Open Cursor Settings (
Cmd+,on macOS orCtrl+,on Linux/Windows). - Navigate to Tools & MCP (or Features > MCP depending on Cursor version).
- Click Add New MCP Server.
- Set Name to
openboard, Type tocommand, and Command toopenboard mcp. - Verify the green active status indicator.
Note: For official Cursor MCP details, refer to Cursor Documentation.
4. Verification
In Cursor Composer or Agent Chat, ask:
What MCP tools are available from openboard?
Cursor should list all 13 tools including list_boards, create_board, create_shapes, get_canvas_state, get_canvas_screenshot, and update_shapes.
5. Example Workflows & Prompts
Multi-Step Architecture Diagramming in Cursor Composer
User:
List my OpenBoard whiteboards.
Cursor Agent:
[Calls list_boards]
Found 2 boards: "Core Architecture", "Data Pipeline".
User:
Create a new board called "Payment Flow".
Cursor Agent:
[Calls create_board with { name: "Payment Flow" }]
Created board "Payment Flow" (ID: "board_e43f11").
User:
Draw a checkout service that sends events to Kafka and writes to Postgres.
Cursor Agent:
[Calls create_shapes on "board_e43f11" with 3 boxes and 2 directional arrows]
Added Checkout Service, Kafka Queue, and Postgres DB with connected bindings.
User:
Inspect the canvas and verify all shape coordinates and arrow links.
Cursor Agent:
[Calls get_canvas_state and get_canvas_screenshot]
Verified all 3 shapes and 2 arrow bindings. Visual layout confirmed.
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.
- 2d ago First seen · 116 lines · 0 tokens per session scan A a058746ea1ea
cursor is an agent published in the GitHub repository atpaawej/openboard (3 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 731 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…