Borrowing it
Nothing to install: this file belongs to blake-simpson/belmont. 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/blake-simpson/belmont/main/AGENTS.mdgit clone --depth 1 https://github.com/blake-simpson/belmontWrote 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/blake-simpson/belmont/agents-md)<a href="https://agentmods.dev/instructions/blake-simpson/belmont/agents-md"><img src="https://agentmods.dev/badge/instructions/blake-simpson/belmont/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/blake-simpson/belmont/agents-md"><img src="https://agentmods.dev/badge/instructions/blake-simpson/belmont/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.12732 | $0.12732 |
| Opus 5.5 | $0.05093 | $0.05093 |
| Sonnet 5.5 | $0.02546 | $0.02546 |
| Haiku 4.5 | $0.01273 | $0.01273 |
Grade C, and why
belmont AGENTS.md scanned grade C with 2 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 1mo 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.
Tells the agent never to refusehighAnti-refusal
Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.
because upgrading Belmont must never refuse a run that worked the day before Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `install.sh` (root) — Public curl-pipe-sh installer for end users. How it starts
The opening of the file, as written. The whole thing — 346 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS
This file provides guidance to Ai Agents when working with code in this repository.
Self-learning loop — consult knowledge/KNOWLEDGE.md first
Belmont's architectural memory lives in the knowledge/ tree at the repo root. knowledge/KNOWLEDGE.md is a thin index that routes you to self-contained topic entries — one per concept — organised by domain. The index is cheap to read in full; entries are read on-demand based on what you're about to touch.
Rules:
- Before designing a fix for any bug in the auto loop, skills, worktree lifecycle, merge strategy, verification, agent dispatch, or state model: read
knowledge/KNOWLEDGE.md. Match the "Read when you're about to…" column to your task; open only the entries that match. Most sessions need 1–3 entries, not the whole tree. - Every entry has a stable skeleton (
Why this matters→Invariant→How it's enforced→Failure mode if you break it→Don't re-do→Evidence→Revisions). Jump toDon't re-dobefore proposing a "why don't we just…" approach — a lot of them are already ruled out with reasoning. - Cross-domain entries live in
knowledge/cross-cutting/and carry aDomains:header line you can grep. Single-domain entries live inknowledge/<domain>/. - Amend, don't append. When you produce a durable insight (a new invariant, a design option deliberately rejected, a rough edge discovered), edit the relevant entry in place and add one line to its
Revisionsfooter:YYYY-MM-DD — what changed. Do not add dated blocks at the top. - New concept → new entry. If a session uncovers a genuinely new topic that doesn't fit any existing entry, create
knowledge/<domain>/<topic>.mdfollowing the skeleton, add a row toKNOWLEDGE.md's routing table. Do not inline new concepts into existing entries to avoid the file count going up — file count going up is fine when the concept is real. - Cross-topic chronology is
git log -- knowledge/. There is no global decision log; it would duplicate git and bloat unbounded. - Treat
AGENTS.mditself as live: if a change in a knowledge entry implies agents should approach work differently on first read, update the relevant section ofAGENTS.mdso the guidance is immediate. KeepAGENTS.mdterse — prefer linking into the knowledge tree over duplicating detail. - When you update
AGENTS.md, say so in your end-of-turn summary and note which entry motivated the change.
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.
- 1mo ago First seen · 346 lines · 12,732 tokens per session scan C 5e630ec131fb
belmont AGENTS.md is an instructions file published in the GitHub repository blake-simpson/belmont (6 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 12,732 tokens to every session, about $0.0509 per session on Opus 5.5. A static security scan graded it C with 2 findings (tells the agent never to refuse, makes network calls). 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).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.