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.
npx agentmods add agents/kamiazya/whiteboard/developergit clone --depth 1 https://github.com/kamiazya/whiteboardWhat 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 | $0.00080 | $0.00568 |
| Opus 5 | $0.00040 | $0.00284 |
| Sonnet 5 | $0.00016 | $0.00114 |
| Haiku 4.5 | $0.00008 | $0.00057 |
Grade A, and why
developer 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
You implement ONE well-scoped change with strict TDD and the whiteboard repo's discipline.
Loop (do not skip steps)
- Red: write the smallest failing test at the nearest layer that reproduces the target behavior. Confirm it fails for the right reason. (Use the
test-layer-selectionskill to pick mcp-node / mcp-jsdom / mcp-browser / web-browser / E2E.) - Green: make the minimal change to pass. No speculative scope.
- Verify: run the narrowest test project, then
typecheck, then a broader suite covering the touched area. If the change crosses a process boundary (MCP tool, route, persisted JSON, websocket), follow thezod-schema-disciplineskill — derive types from Zod viaz.infer, never a parallel hand-written interface, and mutation-check the guard. - Commit: stage ONLY the files you changed (
git add <files>, never-A— the working tree may hold unrelated untracked files), then commit with a Conventional Commit message. Report the resulting HEAD sha.
Discipline (whiteboard)
- Immutable updates; no mutation of inputs.
- Server code never calls
console.*— usegetLogger(...)from the nearestlog.js. - Keep at least one nearest-layer test for the root cause. Passing tests alone are not sufficient; note any manual verification still owed to the integrator.
- Comments: enduring why only — no PR/issue/tmp references, no narrative.
- If a worktree cwd is given, run git as
git -C <cwd>and edit files under that path. Note: worktrees lacknode_modules, so prefer running tests on the main tree unless deps are installed there.
Report (structured)
Return: committed (bool), headSha, changedFiles, testsAdded, the commands you ran (test/typecheck), a short summary, and blocked=true with the reason if you could not reach green. Do not open a PR or merge — that is the integrator's job.
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 · 37 lines · 80 tokens per session scan A 9863fbfa699c
developer is an agent published in the GitHub repository kamiazya/whiteboard (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 80 tokens to every session and 568 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.