Borrowing it
Nothing to install: this file belongs to kamiazya/whiteboard. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kamiazya/whiteboard/main/.claude/skills/whiteboard-mcp-smoke/SKILL.mdgit 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/skills/kamiazya/whiteboard/whiteboard-mcp-smoke)<a href="https://agentmods.dev/skills/kamiazya/whiteboard/whiteboard-mcp-smoke"><img src="https://agentmods.dev/badge/skills/kamiazya/whiteboard/whiteboard-mcp-smoke/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/skills/kamiazya/whiteboard/whiteboard-mcp-smoke"><img src="https://agentmods.dev/badge/skills/kamiazya/whiteboard/whiteboard-mcp-smoke.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 88 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00084 | $0.01369 |
| Opus 5 | $0.00042 | $0.00685 |
| Sonnet 5 | $0.00017 | $0.00274 |
| Haiku 4.5 | $0.00008 | $0.00137 |
Grade A, and why
whiteboard-mcp-smoke 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.
How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Smoke Verification Pattern
This repository splits verification targets into two categories.
- Server/daemon-side changes
Example:
src/server/**,src/app/hooks/useWhiteboardSync.ts,src/daemon/** - MCP schema/registration-side changes
Example: descriptions, schemas, or registration in
src/server/mcp/index.tsandsrc/server/mcp/tools/**
Decide First
- If you only touched
src/server/**orsrc/daemon/**:- Restarting the Claude session is usually unnecessary
- Verify through a watched daemon started with
pnpm --filter @kamiazya/whiteboard-mcp daemon:devor aWHITEBOARD_DEV=1path
- If you touched
src/server/mcp/**:- The MCP client must reconnect
- Do not treat daemon watch mode as sufficient
- If the change is to what a model READS (a name, description, schema, annotation), the smoke
proves the tool still works and says nothing about whether a model still finds it: that is
the
mcp-tool-surfaceskill and ADR-0031's scoreboards, run beside this one
Procedure
1. Match the startup path to the change type
When repeatedly verifying server/daemon-side changes, use this in another terminal.
pnpm --filter @kamiazya/whiteboard-mcp daemon:dev
Meaning:
- Runs
tsx watch src/server/index.ts --daemon - Server, route, store, and daemon changes restart automatically
- MCP schema changes are not picked up
2. Unit Tests
Start with focused tests for the touched area. If broader coverage is not needed yet, leave full pnpm test for later.
pnpm test
Stop there if it fails.
3. Typecheck
pnpm typecheck
4. Stdio Smoke
pnpm smoke:e2e
scripts/smoke/mcp-e2e-smoke.mjs launches stdio MCP in a subprocess and calls
every tool in COVERED_TOOLS, asserting each one's structuredContent against
its outputSchema. It also exercises the error paths in ERROR_PATH_ONLY_TOOLS
and the no-browser cases — a viewport set answering no_client, and a scene
render succeeding through headless rendering with nothing connected.
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 Changed · +3 lines fa7bb7662951
- 12d ago First seen · 125 lines · 84 tokens per session scan A 371e0ce3c7c9
whiteboard-mcp-smoke is a skill published in the GitHub repository kamiazya/whiteboard (6 stars, last pushed today), licensed Apache-2.0. It adds 84 tokens to every session and 1,369 once invoked, about $0.0004 per session on Opus 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-08-31.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.