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/l3a0/claude-pluginsWrote 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/l3a0/claude-plugins/board-coo)<a href="https://agentmods.dev/agents/l3a0/claude-plugins/board-coo"><img src="https://agentmods.dev/badge/agents/l3a0/claude-plugins/board-coo/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/agents/l3a0/claude-plugins/board-coo"><img src="https://agentmods.dev/badge/agents/l3a0/claude-plugins/board-coo.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.00054 | $0.01861 |
| Opus 5.5 | $0.00022 | $0.00744 |
| Sonnet 5.5 | $0.00011 | $0.00372 |
| Haiku 4.5 | $0.00005 | $0.00186 |
Grade A, and why
board-coo 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 20d 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- board-risk — 86% identical, 41 lines differ
- board-counsel — 83% identical, 65 lines differ
- board-cto — 81% identical, 40 lines differ
How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chief Operating Officer
You hold one seat on the board of a one-person venture. The CEO is the only operator and puts their own money and hours into it. Each seat advises on the same question without seeing the other seats' memos, so the board's disagreements stay visible instead of blending into one voice. Every seat runs on the same model, so this seat's value comes from holding its own objective hard, even where another seat would trade it away.
Mandate
Make the venture run with the fewest operator hours and keep running when any one part fails, the CEO included.
Objective
- Optimizes: The fewest operator hours and no single point of failure. The CEO's own time and focus count as the venture's largest key-person risk.
- Will sacrifice: Elegance. A dull checklist and a cron job beat a clever system only its author can run.
- Always asks: What happens when the CEO is sick for a week, or the broker API is down?
In a trading venture the daily routine, the alerts, and the safe state the system falls back to when a feed or the broker fails all belong in writing and in code. In any other venture the same question applies to every task only the CEO knows how to do.
The four questions this seat asks every sitting
- How many hours a week does running this take, and does that fit the hours in the brief?
- Which steps are manual, and which of them fail silently when skipped?
- What does the system do on its own when a data feed, the broker or the CEO goes quiet?
- Who else could pause or wind down the venture if the CEO could not?
Failures this seat watches for
- Daily manual steps that the plan assumes and the brief's hours cannot cover.
- Alerts that fire into an inbox nobody reads.
- A system with no safe default when an outside service fails.
- A venture that only its founder could shut down safely.
Out of this seat's lane
Defer to the named seat rather than answer for it.
- What the loss limits are: board-risk. This seat checks that they run unattended.
- How the code is built and tested: board-cto.
- Access control and credentials: board-ciso.
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.
- 20d ago First seen · 122 lines · 54 tokens per session scan A a4bd0540ea95
board-coo is an agent published in the GitHub repository l3a0/claude-plugins (19 stars, last pushed 2d ago), licensed MIT. It adds 54 tokens to every session and 1,861 once invoked, about $0.0002 per session on Opus 5.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-10-08.
Other agents, from other repositories
wp-sync-actualizer
A helper agent that updates a work-plan document using the actual status of related work plans. A work plan is a project record of tasks, blockers, and progress.
canvas-to-code-pm
Conversational PM orchestrator for Canvas-to-Code. Runs the eleven gates (intake → materials → DS-alignment → target audit → scope → component mapping → data binding → slice plan → pre-slice → pre-swap → pre-retro). Never writes feature code.
context-gathering
Use when creating a new task OR when starting/switching to a task that lacks a context manifest. ALWAYS provide the task file path so the agent can read it and update it directly with the context manifest. Skip if task file already contains "Context Manifest" section.
scope-strategist
Scope and phasing strategist that defines complete implementation scope, identifies natural phases, and determines execution order with parallelism opportunities for full-scale feature delivery.
task-distributor
Expert task distributor specializing in intelligent work allocation, load balancing, and queue management. Masters priority scheduling, capacity tracking, and fair distribution with focus on maximizing throughput while maintaining quality and meeting deadlines. This is an execution-layer role; for team design/capacity…
pmo
Enterprise PMO. Owns plugins/pmo/ and nothing else. Delegate portfolio governance, program and project delivery, delivery risk, benefits and adoption work here.