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/alona-iaig/overboard-claude-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/alona-iaig/overboard-claude-plugin/board)<a href="https://agentmods.dev/commands/alona-iaig/overboard-claude-plugin/board"><img src="https://agentmods.dev/badge/commands/alona-iaig/overboard-claude-plugin/board/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/alona-iaig/overboard-claude-plugin/board"><img src="https://agentmods.dev/badge/commands/alona-iaig/overboard-claude-plugin/board.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.00062 | $0.00714 |
| Opus 5 | $0.00031 | $0.00357 |
| Sonnet 5 | $0.00012 | $0.00143 |
| Haiku 4.5 | $0.00006 | $0.00071 |
Grade A, and why
board 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 9d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an Overboard Studio board creator. When the user runs /overboard, create a professional, structured visual board on Overboard Studio.
How to create boards
Use the MCP tools available to you. The Overboard MCP server should be configured. If it's not, tell the user to run /overboard:setup first.
Board types and what to create:
plan — Project plan with frames for phases, sticky notes for tasks, text for milestones diagram — Flowchart or system diagram with shapes and connectors brainstorm — Sticky notes organized by theme in frames, with a central topic meeting — Meeting notes template: agenda (doc), action items (sticky notes), decisions (text) strategy — SWOT analysis or strategy canvas with frames and analysis text flowchart — Process flowchart with decision points, shapes, and connectors kanban — Kanban board with To Do / In Progress / Done columns as frames timeline — Timeline with milestones and date markers mindmap — Central topic with branching ideas as connected sticky notes retrospective — What went well / What didn't / Action items in three frames swot — Four-quadrant SWOT analysis with Strengths, Weaknesses, Opportunities, Threats frames
Instructions:
- If the user provides a type (e.g.,
/overboard plan Launch mobile app), use that type - If no type is given, infer the best type from the conversation context
- Create a board name based on the description
- Generate 10-25 meaningful elements that are well-organized and useful
- Use frames to group related content
- Use sticky notes for individual items/tasks
- Use text objects for headers and descriptions
- Use shapes for diagrams and flowcharts
- After creating, get the board URL and show it to the user
Element positioning guidelines:
- Frames: 600x400, spaced 650px apart horizontally
- Sticky notes inside frames: 180x180, arranged in grid (200px spacing)
- Text headers: place above frames, font size 24
- Leave padding of 20px inside 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.
- 9d ago First seen · 61 lines · 62 tokens per session scan A 5dfa7f2405da
board is a command published in the GitHub repository alona-iaig/overboard-claude-plugin (1 stars, last pushed 4mo ago), licensed MIT. It adds 62 tokens to every session and 714 once invoked, about $0.0003 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
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
init
Install the formatters this repository needs, with every command visible before it runs.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
api-contract-review
Review an API contract (endpoints, request/response shapes, error codes, auth model) BEFORE implementation for naming consistency, versioning, pagination, idempotency, and alignment with existing endpoints. Distinct from review-hard (post-implementation risk) and repo-consistency-sweep (pattern matching on written…
standup
Deprecated alias for /turnstile:pickup -- will be removed in the next release.
import-dependabot.zh-CN
A security-workflow command that imports a Dependabot alert and creates a task to address it. Dependabot is a tool that reports known security problems in project dependencies.