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.
/plugin marketplace add mmyslin/sideboardnpx agentmods add plugins/mmyslin/sideboard/sideboardgit clone --depth 1 https://github.com/mmyslin/sideboardGrade 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 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.
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 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.
- 2d ago First seen · 21 lines scan A 4ce8e37115c9
sideboard is a plugin published in the GitHub repository mmyslin/sideboard (2 stars, last pushed 13d 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
scrumboy-board-operator
Agent plugin with Skills for operating Scrumboy boards through its MCP and Agoragentic APIs.
trello-cli-marketplace
Plugin marketplace listing 1 plugin: trello-cli.
trello-cli
Trello board, list, and card management via CLI. Activate when user mentions 'Trello'.
mdpm
Plugin marketplace listing 1 plugin: mdpm.
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.
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.