Borrowing it
Nothing to install: this file belongs to Brandon-Born/bga-mcp. 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/Brandon-Born/bga-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/Brandon-Born/bga-mcpWrote 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/brandon-born/bga-mcp/agents-md)<a href="https://agentmods.dev/instructions/brandon-born/bga-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/brandon-born/bga-mcp/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.1 | $0.01053 | $0.01053 |
| Opus 5 | $0.00526 | $0.00526 |
| Sonnet 5 | $0.00211 | $0.00211 |
| Haiku 4.5 | $0.00105 | $0.00105 |
Grade A, and why
bga-mcp 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 6d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working in bga-mcp
Instructions for any coding agent working in this repository, in the AGENTS.md format. This file is canonical; CLAUDE.md points here so Claude Code reads the same rules. Change this file, not a copy of it.
bga-mcp is a local, read-only MCP server that inspects and validates BoardGameArena game projects. It reads a developer's project from disk and reports cross-file defects. It never writes to a project. Network access is off by default; explicitly enabled documentation and experimental Studio reads use the reviewed policy boundaries recorded in the threat model.
docs/BACKLOG.md is the executable source of truth for planned work. CONTRIBUTING.md states the contribution rules; everything below is in addition to them.
Look up the BGA documentation before implementing a framework behavior
This project's entire value is that it models the BGA framework correctly. A rule built on a plausible-sounding assumption produces confident false positives in a developer's project, which is worse than reporting nothing.
So, before writing or changing any code that reads, parses, validates, or names a BGA construct — file layouts, state machines, action wiring, notifications, database access, metadata keys, client APIs, Studio behavior:
- Read the official documentation for that construct first. Start at the Studio file reference and follow it to the specific page. Fetch the page. Do not work from memory, from an existing fixture, or from the shape of the surrounding code.
- Quote what it actually says in the backlog item, the code comment, or the commit message, and record the page URL under Sources.
- Read the deprecation and migration wording carefully. The framework almost never removes an old form. "Deprecated", "legacy usage", and "you can then delete" mean both forms exist in real projects and both must be read. Assume the older form is still out there.
- Do not assume two options are exhaustive or coupled. BGA migrations happen one file at a time. Two documented forms of five different files are more than two project shapes. This exact assumption — that a project is either wholly legacy or wholly modern — shipped and was wrong; see BGA-122.
- When the documentation is silent or ambiguous, say so. Record it as an open question in the backlog item and make the code report unsupported syntax. Never guess and never let a guess become a rule that fires.
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.
- 6d ago First seen · 53 lines · 1,053 tokens per session scan A 57ed2aac4b33
bga-mcp AGENTS.md is an instructions file published in the GitHub repository Brandon-Born/bga-mcp (0 stars, last pushed 12d ago), licensed Apache-2.0. It adds 1,053 tokens to every session, about $0.0053 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
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.
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).
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
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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.