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 instructions/zkbys/whiteboard/agents-mdgit clone --depth 1 https://github.com/zkbys/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/instructions/zkbys/whiteboard/agents-md)<a href="https://agentmods.dev/instructions/zkbys/whiteboard/agents-md"><img src="https://agentmods.dev/badge/instructions/zkbys/whiteboard/agents-md.svg" alt="Measured on agentmods" height="20"></a>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 | $0.01474 | $0.01474 |
| Opus 5 | $0.00737 | $0.00737 |
| Sonnet 5 | $0.00295 | $0.00295 |
| Haiku 4.5 | $0.00147 | $0.00147 |
Grade C, and why
whiteboard AGENTS.md scanned grade C with 1 finding 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 4d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
find . -name "__pycache__" -type d -prune -exec rm -rf {} + How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
This file is the first thing a new Codex/agent thread should read before editing this repository.
Canonical Workspace
Work only in the current Git checkout. Resolve it instead of assuming a developer-machine path:
git rev-parse --show-toplevel
Remote:
https://github.com/zkbys/whiteboard.git
Do not edit or publish files from the parent experimental workspace unless the user explicitly asks for historical reference work. In particular, do not treat these old folders as the active source:
../whiteboard-infographic-prototype-v0.*../integration-smoke-test-*../integration-full-run-*../optimization-sync-calibration-test/../orchestrator-runs/../reference-video-analysis/../visual-hammer-v0.1/
Start Every New Thread With
cd "$(git rev-parse --show-toplevel)"
git status --short --branch
git pull --ff-only
Then read, as needed:
README.mdorREADME.en.mddocs/PROJECT_STRUCTURE.mddocs/ARCHITECTURE.mddocs/VERSION_AUDIT.md- the
SKILL.mdfor the module being changed - the matching
references/contracts.mdwhen changing JSON contracts or paths
Current Pipeline Boundary
The only user-facing Skill is skills/whiteboard-video/. It bundles the following directories as internal runtime modules during installation; do not install them as six separate user Skills.
Keep the module responsibilities separated:
- B
ip-cognition-script-polisher: script shaping only. - C
ip-hand-drawn-infographic-planner: semantic board planning only; no bbox, camera, cursor, or animation coordinates. - Creator
hand-drawn-infographic-creator: image-generation prompts and review notes only. - D
hand-drawn-infographic-video-board: board PNG control layer, bbox calibration, annotation manifests, and motion plans. - E
whiteboard-infographic-video-renderer: narration, measured timing, tokenized action sync, HyperFrames, preview MP4, and keyframes. - Orchestrator
whiteboard-infographic-pipeline-orchestrator: full run order, handoff rules, validation, and acceptance reporting.
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.
- 4d ago First seen · 170 lines · 1,474 tokens per session scan C 1797207113ac
whiteboard AGENTS.md is an instructions file published in the GitHub repository zkbys/whiteboard (59 stars, last pushed 1mo ago), licensed MIT. It adds 1,474 tokens to every session, about $0.0074 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.