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 skills add korbinjoe/TeemAI --skill whiteboardgit clone --depth 1 https://github.com/korbinjoe/TeemAIWrote 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/korbinjoe/teemai/whiteboard)<a href="https://agentmods.dev/skills/korbinjoe/teemai/whiteboard"><img src="https://agentmods.dev/badge/skills/korbinjoe/teemai/whiteboard.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.1 | $0.00114 | $0.01087 |
| Opus 5 | $0.00057 | $0.00544 |
| Sonnet 5 | $0.00023 | $0.00217 |
| Haiku 4.5 | $0.00011 | $0.00109 |
Grade A, and why
whiteboard 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 8d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
War-Room Write Instructions
whiteboard is the shared key-information board for all Agents in the current Chat.
The system auto-writes artifact (code outputs) and handoff (task dispatches) via hooks,
and auto-extracts goal and progress at turn end.
You only need to manually call wb-write.sh in these scenarios:
- Important technical decisions (
decision) — auto-extraction may not be accurate enough - Blocking issues (
open_question) — needs explicit articulation - Hard constraints (
constraint) — needs precise description
Entry Type Quick Reference
| Type | Auto/Manual | Description |
|---|---|---|
goal |
Auto (Stop hook, first turn extraction) | Lead's objective after receiving user request |
decision |
Manual | Technical/design decisions affecting other Agents |
artifact |
Auto (PostToolUse hook) | Reusable code/docs/deliverables produced |
progress |
Auto (Stop hook completion signal) | A milestone completed |
open_question |
Manual | Blocking issue requiring external decision |
constraint |
Manual | Hard constraints discovered (dependency, performance, security) |
handoff |
Auto (PostToolUse hook) | Explicitly passing a task to another Agent |
Don't write: routine thinking, process details, info derivable from code/git, private state irrelevant to other Agents.
Environment Variables (Injected)
| Variable | Description |
|---|---|
AGENT_API_BASE |
teemai-server HTTP address |
TEEMAI_CHAT_ID |
Current chat ID |
TEEMAI_INSTANCE_ID |
Your instance ID (injected as by field) |
Commands
Write Entry
bash {SKILL_DIR}/scripts/wb-write.sh <type> "<summary>" [tags] [refs-json]
type:goal | decision | artifact | progress | open_question | constraint | handoffsummary: ≤120 characters, one sentence that makes it clear (server rejects longer)tags: optional, comma-separated (e.g.,db,migration)refs-json: optional, JSON string (e.g.,'{"files":["a.ts"],"agents":["shield"]}')
What ships with it
6 files beside SKILL.md 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.
- 8d ago First seen · 114 lines · 114 tokens per session scan A 344ed00b5d63
whiteboard is a skill published in the GitHub repository korbinjoe/TeemAI (2 stars, last pushed 2mo ago), licensed MIT. It adds 114 tokens to every session and 1,087 once invoked, about $0.0006 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
starting-a-new-project
Use when the workspace is empty — no code yet — and the user brings a raw idea: the brand-new branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for features in an existing project — use brainstorming instead.
agent-spec-estimate
An effort-estimation method for agent-spec Task Contracts, which are structured descriptions of software work. It estimates work in rounds, meaning cycles of an AI agent doing and checking tasks.
agent-spec-intent-compiler
Use when converting PRD or issue prose into KLL requirements, running the intent compiler plan, or reverse-interviewing a human to resolve requirement ambiguity before task spec generation.
agent-spec-wiki
Use when initializing, checking, enriching, or reviewing agent-spec code live wiki pages, sourcefiles trace, or Rust architecture inventory.
todos
This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.