What is lead-protocol AGENTS.md?

Repository instructions for a project that uses the Lead Protocol to coordinate work between agents. The protocol stores operational rules, project context, active scopes, session information, and handoff notes in the `.agents` directory.

Use them when working in the repository to load the required rules, identify active modules, check concurrent sessions, resolve the agent identity, and record or read the appropriate handoff state.

They tell an agent which project rules and current state to read before acting. This reduces the chance of bypassing required coordination steps or overwriting another agent’s work.

How mmilanez/lead-protocol configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to mmilanez/lead-protocol. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/mmilanez/lead-protocol/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/mmilanez/lead-protocol

Made for: Codex, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/mmilanez/lead-protocol/agents-md/github.svg)](https://agentmods.dev/instructions/mmilanez/lead-protocol/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/mmilanez/lead-protocol/agents-md"><img src="https://agentmods.dev/badge/instructions/mmilanez/lead-protocol/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/mmilanez/lead-protocol/agents-md"><img src="https://agentmods.dev/badge/instructions/mmilanez/lead-protocol/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 523 This file is loaded in full into every session.

When invoked 523 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00523	$0.00523
Opus 5.5	$0.00209	$0.00209
Sonnet 5.5	$0.00105	$0.00105
Haiku 4.5	$0.00052	$0.00052

Measured 1mo ago against content hash 5ca6237897cc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

lead-protocol 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 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.

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.

AGENTS.md · 22 lines

What it actually says

AGENTS.md — Pointer for AI Agents

This file acts as a universal pointer for agents like Cursor, Windsurf, Antigravity, and Codex.

This repository operates under the Lead Protocol. All operational instructions, project context, and state definitions are stored in the .agents/ directory.

Before taking any action, read the rules and the current state in this order:

.agents/CORE_RULES.md — index + essential contracts
.agents/PROJECT_RULES.md — identify the scopes listed in §J8 Active modules 2a. Setup gate: if .agents/PROJECT_RULES.md is missing or still pristine (§J1 Name or §J8 substrate/modules still contain [...] placeholders) and no repo-root .lead-protocol-source sentinel exists, run the first-run setup interview defined in .agents/PROTOCOL_RULES.md §P10 and write the answers before serving any request, even if the user asked for something else first. Reply later or skip defers for this session only; non-interactive environments warn without writing configuration. Preserve existing values and clarify required answers per §P10.
For each scope listed in §J8 Active modules (in declaration order): .agents/modules/<scope>.md
.agents/AGENTS_MAP.md — tool-signature → agent-slug map; resolve your own <agent> slug here (needed to form the per-pair handoff path)
.agents/sessions/active_sessions.md — concurrent-session awareness
.agents/local/<actor>/<agent>/handoff.md — state of THIS (actor, agent) pair

Before answering a project question, consult relevant INDEX.md entries on demand, then read canonical sources. If the map is absent, use PROJECT_RULES.md §J6 and the independent search recipes in PROTOCOL_RULES.md §P-Access; absence never blocks legacy boot. Do not load the full map or its targets at boot.

PROTOCOL_RULES.md is read on demand, not in the baseline — CORE_RULES.md points to it. See PROTOCOL_RULES.md §P-Access for the full load contract.

Do not bypass the protocol. Your work must be logged in your pair's handoff.md and, when applicable, in .agents/decisions.jsonl and .agents/JOURNAL.md at the end of your session.

Changes

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 Changed · +3 lines · +202 tokens per session 5ca6237897cc
2mo ago First seen · 19 lines · 321 tokens per session scan A 8983a36b50da

Subscribe to this mod's changes

lead-protocol AGENTS.md is an instructions file published in the GitHub repository mmilanez/lead-protocol (5 stars, last pushed 8d ago), licensed Apache-2.0. It adds 523 tokens to every session, about $0.0021 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.

Building agents Planning agentic-ai agents ai ai-agents audit-trail handoff

lead-protocol AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
lead-protocol AGENTS.mdmmilanez/lead-protocol	Instructions file	5	8d ago	Apache-2.0	A	523	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	275k	2d ago	MIT	A	4,313	Codex, OpenCode

lead-protocol: Instructions file for Codex