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/kevinmhorvath/theboardroomWrote 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/plugins/kevinmhorvath/theboardroom/theboardroom)<a href="https://agentmods.dev/plugins/kevinmhorvath/theboardroom/theboardroom"><img src="https://agentmods.dev/badge/plugins/kevinmhorvath/theboardroom/theboardroom/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/plugins/kevinmhorvath/theboardroom/theboardroom"><img src="https://agentmods.dev/badge/plugins/kevinmhorvath/theboardroom/theboardroom.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
theboardroom 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.
What it actually says
{
"name": "theboardroom",
"displayName": "TheBoardroom",
"version": "1.0.0",
"description": "An AI executive board of directors (CEO, CFO, COO, CLO, CISO sub-agent personas) that vets business ideas, debates them from each role's perspective, and delivers an integrated Go/No-Go board memo. Built to help executives pressure-test initiatives before presenting to a real board.",
"author": {
"name": "Kevin Horvath",
"email": "[email protected]"
},
"keywords": ["board", "executive", "sub-agents", "go-no-go", "strategy", "risk", "ciso", "vetting"],
"homepage": "https://github.com/kevinmhorvath/theboardroom",
"license": "MIT"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 174 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json 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.
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 · 14 lines scan A 1df67c9b2134
theboardroom is a plugin published in the GitHub repository kevinmhorvath/theboardroom (2 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
security
Threat modeling, security architecture review, incident response, vulnerability management, and access and identity. Reviewer-class: blocking findings are not overrulable by the department under review.
data-analytics
Data governance, warehouse and semantic modeling, business intelligence, and AI/ML governance.
executive
Direction, capital and attention allocation, cross-functional arbitration, strategy validation, and the method for structuring the organization itself.
revenue
Outbound, sales enablement, revenue operations, pricing and packaging, activation, retention, and referrals.
rudder-core
Cross-tool RudderStack domain knowledge: data catalog, data graphs, tracking plans, instrumentation planning, instrumentation debugging, and destination delivery debugging.
neatcontext marketplace
Save Claude Code work as reusable, domain-aware context.