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/kamiazya/whiteboardWrote 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/kamiazya/whiteboard/marketplace)<a href="https://agentmods.dev/plugins/kamiazya/whiteboard/marketplace"><img src="https://agentmods.dev/badge/plugins/kamiazya/whiteboard/marketplace/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/kamiazya/whiteboard/marketplace"><img src="https://agentmods.dev/badge/plugins/kamiazya/whiteboard/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
whiteboard-marketplace 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 23d 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": "whiteboard-marketplace",
"owner": {
"name": "kamiazya",
"url": "https://github.com/kamiazya"
},
"metadata": {
"description": "Claude Code plugin distribution for the @kamiazya/whiteboard collaborative diagramming MCP.",
"version": "0.0.20"
},
"plugins": [
{
"name": "whiteboard",
"source": {
"source": "github",
"repo": "kamiazya/whiteboard",
"ref": "stable"
},
"description": "Collaborative whiteboard for Claude Code. Wraps the @kamiazya/whiteboard-mcp server and exposes the bundled /drawing-visuals, /coauthoring-visuals, and /auditing-workspaces skills.",
"version": "0.0.20",
"author": {
"name": "kamiazya",
"url": "https://github.com/kamiazya"
},
"homepage": "https://github.com/kamiazya/whiteboard",
"repository": "https://github.com/kamiazya/whiteboard",
"license": "Apache-2.0",
"keywords": [
"json-canvas",
"diagramming",
"mcp",
"whiteboard",
"claude-code",
"codex"
],
"category": "productivity",
"tags": [
"diagramming",
"mcp",
"json-canvas",
"visualization"
]
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.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.
- 23d ago Changed · +12 lines 6ae7aefb5b01
- 1mo ago Changed af9bf53250d1
- 1mo ago First seen · 34 lines scan A 76bb11a43753
whiteboard-marketplace is a plugin published in the GitHub repository kamiazya/whiteboard (10 stars, last pushed yesterday), licensed Apache-2.0. 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
motion-design-skills
Motion design fundamentals, engines, and brand elements as installable skills for AI coding agents — timing, typography, color, composition, After Effects, Remotion, logos, and backgrounds.
aio-visual-diff
Verify AI-built UI against design via measurement-driven diff — extracts computed CSS and bounding boxes through Chrome DevTools MCP, diffs against Figma reference or a frozen baseline, and feeds numerical deltas back to the agent. No screenshot eyeballing.
ui-input-skills
Form systems, search, and filter components for user input and data collection.
hyperstack
Disciplined MCP server + skill system. 16 plugins and 121 tools covering designer (6 personalities, 13 page templates, 9 presets), shadcn/ui, design tokens, ui/ux, React Flow v12, Motion v12, Lenis, React 19, Echo, Go, Rust, product-manager, marketing, reflect, and optimizer. 29 skills with adversarial enforcement…
stark-figma-drive
Exporta frames do Figma e faz upload automatico para o Google Drive do cliente.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.