Borrowing it
Nothing to install: this file belongs to 100yenadmin/boardstate. 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/100yenadmin/boardstate/main/AGENTS.mdgit clone --depth 1 https://github.com/100yenadmin/boardstateWrote 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/100yenadmin/boardstate/agents-md)<a href="https://agentmods.dev/instructions/100yenadmin/boardstate/agents-md"><img src="https://agentmods.dev/badge/instructions/100yenadmin/boardstate/agents-md/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/instructions/100yenadmin/boardstate/agents-md"><img src="https://agentmods.dev/badge/instructions/100yenadmin/boardstate/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.02557 | $0.02557 |
| Opus 5.5 | $0.01023 | $0.01023 |
| Sonnet 5.5 | $0.00511 | $0.00511 |
| Haiku 4.5 | $0.00256 | $0.00256 |
Grade A, and why
boardstate AGENTS.md 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 2mo 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agents & Boardstate
Boardstate is agent-native in two directions:
| Direction | What it means | Packages |
|---|---|---|
| Agents build the board | Any AI composes tabs, widgets, bindings, and custom sandboxed widgets through the boardstate_* tool set |
@boardstate/mcp, @boardstate/agent |
| The board acts on the world | The board consumes external MCP servers: their reads become live data, their mutations become operator-confirmed actions | @boardstate/broker, @boardstate/server |
This file covers how to set each surface up, the full tool catalog, the conventions that make agent-built boards good, and the rules for coding agents working on this repo.
1. Give any AI the board (@boardstate/mcp)
The MCP server exposes the complete dashboard tool set to any MCP client — Claude Desktop,
Claude Code, or anything else that speaks MCP. State persists to $BOARDSTATE_STATE_DIR
(default ~/.boardstate), so the same board is shared by the CLI, the MCP server, and any
host you run.
Claude Code (one command):
claude mcp add boardstate -- npx -y @boardstate/mcp
Claude Desktop (claude_desktop_config.json):
{
"mcpServers": {
"boardstate": { "command": "npx", "args": ["-y", "@boardstate/mcp"] }
}
}
Watch the board the agent is building — add --serve and open the printed page; it
live-updates as tools land:
npx @boardstate/mcp --serve 4400
Inside MCP-Apps-capable clients, boardstate_board_view renders the live board directly
in the conversation.
The tool catalog
| Group | Tools |
|---|---|
| Read & discover | boardstate_workspace_get · boardstate_widget_catalog · boardstate_data_read · boardstate_board_view |
| Tabs | boardstate_tab_create · boardstate_tab_update · boardstate_tab_delete · boardstate_tabs_reorder · boardstate_layout_set |
| Widgets | boardstate_widget_add · boardstate_widget_update · boardstate_widget_move · boardstate_widget_remove |
| Custom widgets | boardstate_widget_scaffold (sandboxed; lands as a pending card) · boardstate_widget_approve (operator surfaces only) |
| Whole-document | boardstate_workspace_replace (full-document write, sanitized + capability-reconciled) · boardstate_undo |
| Quality | boardstate_design_review (screenshot + critique the board you just built) |
| External tools | boardstate_tool_search (SEARCH the connector catalog / REQUEST grants — see §3) |
| Errors | boardstate_error (structured failure 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.
- 2mo ago First seen · 187 lines · 2,557 tokens per session scan A 1c42d3ce4008
boardstate AGENTS.md is an instructions file published in the GitHub repository 100yenadmin/boardstate (24 stars, last pushed 1mo ago), licensed MIT. It adds 2,557 tokens to every session, about $0.0102 per session on Opus 5.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 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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.