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 skills/100yenadmin/boardstate/using-boardstatenpx skills add 100yenadmin/boardstate --skill using-boardstategit clone --depth 1 https://github.com/100yenadmin/boardstateWhat 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.00067 | $0.01370 |
| Opus 5 | $0.00034 | $0.00685 |
| Sonnet 5 | $0.00013 | $0.00274 |
| Haiku 4.5 | $0.00007 | $0.00137 |
Grade A, and why
using-boardstate 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 3d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Boardstate as an agent
You are composing a board: one validated JSON document of tabs, widgets, layout, and
data bindings. Every mutation you make goes through boardstate_* tools; a human may be
editing the same document live. Full reference: AGENTS.md.
If the tools aren't connected yet
claude mcp add boardstate -- npx -y @boardstate/mcp # Claude Code
npx @boardstate/mcp --serve 4400 # + a live page of the board
Claude Desktop: add {"mcpServers":{"boardstate":{"command":"npx","args":["-y","@boardstate/mcp"]}}}.
State persists to $BOARDSTATE_STATE_DIR (default ~/.boardstate).
Bare-API harnesses (GLM, OpenAI-compatible, custom loops): either embed
@boardstate/agent — its system prompt already includes these conventions — or paste this
file into your system prompt and bridge the MCP tools yourself.
The composing loop
- Orient:
boardstate_workspace_get— see what exists before adding to it. - Catalog first:
boardstate_widget_catalogreturns a schema-valid example for every builtin. Copy a real example and modify it. Guessing props is the #1 cause of rejected calls; a rejection means re-read the catalog entry, not retry harder. - Compose:
boardstate_tab_create→boardstate_widget_add. Grid is 12 columns:x + w ≤ 12, heights are rows (h1–20). Prefer 2–4 substantial widgets over many tiny ones; stat cards in a row of 3–4 (w:3–4), charts and tables wide (w:6–12). - Bind live data, don't paste snapshots:
static(inline fixtures ≤ 8 KB) ·file(host state dir) ·rpc(whitelisted host method) ·stream(live push — tickers, logs) ·computed(derive from other bindings) ·mcp(granted external tool, reads only). If a value will change, it belongs in a binding. - Review your work:
boardstate_design_reviewscreenshots and critiques the board — run it after composing and fix what it flags. Thenboardstate_widget_update({tab, id, patch}) orboardstate_widget_moveto tighten the layout.
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.
- 3d ago First seen · 95 lines · 67 tokens per session scan A b846fdc1c750
using-boardstate is a skill published in the GitHub repository 100yenadmin/boardstate (9 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 1,370 once invoked, about $0.0003 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
surface
Surface-native display for AI agents, driven by the surface CLI. Use when the user says "surface this", "show me X", or "put it on my display/screen"; wants a live interactive UI, chart, or tool they act on; needs a question answerable from any device; or asks you to react to what they click — even while you're…
xcatcher
Fetch fresh or recent public X (Twitter) posts from one or many named account handles through Xcatcher, with structured JSON results and optional x402 v2 USDC pay-per-crawl access on Base. Use for account monitoring, social intelligence, OSINT, tweet/post collection, timeline snapshots, or requests to scrape, crawl…
install-isingq-mcp
Install, update, connect, or diagnose IsingQ tools through standard MCP, Codex Plugin, or the native DeepSeek Harness Plugin. Use when a user wants IsingQ available in an Agent Host.
use-404-directory
Preflight a specific Polymarket observation or contemplated Yes/No action for settlement, timing, liquidity, slippage, geoblock, and execution risk; also assess an unfamiliar third-party Agent tool before installation or first use. Use when an exact Polymarket market reference or actual external-tool action is…
cowork-review
Worker-prompt lifecycle and the Architect/Analyst review gates — prompt frontmatter (status, reviewround, outputstatus), the draft→in-review→approved loop, the append-only review logs, the output gate (review-output → promote), and the tasks/{todo,run,done} transitions. Use when drafting, reviewing, or executing a…
onboarding
Onboard a code project into RoadBoard — analyze the cloned repo and populate RoadBoard (project, phase, tasks, memory and the architecture graph / Atlas) via the RoadBoard MCP tools, then render the per-repo CLAUDE.md. Use when the user asks to onboard a project, or when a project that has a repo is not yet onboarded…