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/mmyslin/sideboardWrote 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/mmyslin/sideboard/sideboard)<a href="https://agentmods.dev/plugins/mmyslin/sideboard/sideboard"><img src="https://agentmods.dev/badge/plugins/mmyslin/sideboard/sideboard/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/mmyslin/sideboard/sideboard"><img src="https://agentmods.dev/badge/plugins/mmyslin/sideboard/sideboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
sideboard 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 1mo 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": "sideboard",
"displayName": "Sideboard",
"version": "0.5.4",
"description": "Your GitHub Issues as a live roadmap board pinned beside Claude Code chat. Runs a local 127.0.0.1 board server and adds SessionStart/UserPromptSubmit hooks so the pane follows your active project.",
"author": {
"name": "Mark Myslin",
"url": "https://github.com/mmyslin"
},
"homepage": "https://github.com/mmyslin/sideboard",
"repository": "https://github.com/mmyslin/sideboard",
"license": "MIT",
"keywords": [
"roadmap",
"kanban",
"github-issues",
"board",
"project-management"
]
}
What it installs
The manifest is a name and a version. 1 skill, 4 commands, 2 hooks travel with it, and installing the plugin installs all of them — 152 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.
- 1mo ago First seen · 21 lines scan A 4ce8e37115c9
sideboard is a plugin published in the GitHub repository mmyslin/sideboard (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
recursive-spine
GitHub issues+milestones tracking convention and project spine: recursive-spine-method, recursive-spine-bootstrap, recursive-spine-migrate, recursive-spine-digest, recursive-spine-pollinate, recursive-spine-scaffold, recursive-spine-handover, recursive-spine-nudge. State lives where it's queryable, not where it merges.
mdpm
Markdown Project Manager — a lightweight, markdown-native project tracking system for Claude Code. Tasks live as .md files with YAML frontmatter; status is a directory. Optional Jira/Wrike sync via MCP.
pmo
Enterprise program management office: portfolio governance, program and project delivery, dependencies and delivery risk, benefits realization, and adoption.
operations
Program management, process design, vendor and supplier management, and operational delivery.
people
Org design, hiring and interviewing, compensation and leveling, and workforce planning.
revenue
Outbound, sales enablement, revenue operations, pricing and packaging, activation, retention, and referrals.