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/fmilioni/agents-board/agents-mdgit clone --depth 1 https://github.com/fmilioni/agents-boardWrote 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/fmilioni/agents-board/agents-md)<a href="https://agentmods.dev/instructions/fmilioni/agents-board/agents-md"><img src="https://agentmods.dev/badge/instructions/fmilioni/agents-board/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.02085 | $0.02085 |
| Opus 5 | $0.01043 | $0.01043 |
| Sonnet 5 | $0.00417 | $0.00417 |
| Haiku 4.5 | $0.00209 | $0.00209 |
Grade A, and why
agents-board 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 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agents Board
Project management for coding agents, exposed over MCP. Codex, Claude Code and Cursor can use the system to organize their own development (auto-inception). International product.
Skills
Two skills ship from a single host-neutral package, plugins/agents-board — Codex reads .codex-plugin/plugin.json, Claude Code reads .claude-plugin/plugin.json + .mcp.json, Cursor reads .cursor-plugin/plugin.json + mcp.json, and all three load the same skills/:
agents-board— how to use the board: bind the repo to its project (recordprojectId+ the auth flag in.agents-board.local.md), read and search it, keep a card's status honest, comment, write docs, work the inbox, attach diffs and images.plan— turn a new demand into sprints/stories/cards: clarify, offer research, clarify again, get approval, then write cards a zero-context agent can execute. All card creation goes through here.
The plugin deliberately stops at the board's edge. It ships no implementation, review, worktree or orchestration workflow — how code gets written is the user's process, with whatever skills they prefer. A change to a skill must not smuggle one back in.
Let the skills drive. What to do (active sprint, cards, backlog, comments, docs) is the source of truth and lives in the MCP, not here — query it through the Agents Board MCP tools. Don't duplicate state into this file.
Bind this repo to your board (local, not committed)
This is an open-source repo — every clone tracks its own work on its own Agents Board instance, so the project↔MCP binding is deliberately not committed here. Put yours in a gitignored .agents-board.local.md at the repo root. The coding agent must read it when it exists. For example:
This project in the MCP:
- **slug**: `<your-slug>`
- **keyPrefix**: `<KEY>` (cards are `<KEY>-1`, `<KEY>-2`…)
- **projectId**: `<your-project-id>`
Auth (diff capture) is **ON / OFF** in this deployment.
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 · 84 lines · 2,085 tokens per session scan A 3277e1428aa2
agents-board AGENTS.md is an instructions file published in the GitHub repository fmilioni/agents-board (0 stars, last pushed 4d ago), licensed MIT. It adds 2,085 tokens to every session, about $0.0104 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 instructions, from other repositories
ESAA-Core AGENTS.md
Instructions for elzobrito/ESAA-Core, covering agents.md — contrato operacional codex/esaa, 1. autoridade e termos, 2. cli e runner, ou configure o runner uma vez por sessão and 3. concorrência.
idd-skill idd-resume.instructions.md
Instructions for kurone-kito/idd-skill, covering idd — resume phase, required inputs, step 0 — route classifier, operator-present release and step 1 — identify claim state.
tmetric-minimal-mcp CLAUDE.md
Claude Code instructions for guglielmo/tmetric-minimal-mcp, covering claude.md, development commands, project architecture, file structure and core architecture patterns.
shelly-forge CLAUDE.md
Claude Code instructions for mslavov/shelly-forge, covering documentation usage guidelines, critical: framework-first reading order, 📚 mandatory reading order, pre-task protocol and post-task protocol.
vibelive AGENTS.md
AGENTS.md instructions for pooriaarab/vibelive, covering agents.md, repository context, pull requests, cloud agents (cursor) and install & test.
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).