Borrowing it
Nothing to install: this file belongs to brifl/coding-agent-orchestration. 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/brifl/coding-agent-orchestration/main/AGENTS.mdgit clone --depth 1 https://github.com/brifl/coding-agent-orchestrationWrote 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/brifl/coding-agent-orchestration/agents-md)<a href="https://agentmods.dev/instructions/brifl/coding-agent-orchestration/agents-md"><img src="https://agentmods.dev/badge/instructions/brifl/coding-agent-orchestration/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/brifl/coding-agent-orchestration/agents-md"><img src="https://agentmods.dev/badge/instructions/brifl/coding-agent-orchestration/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.02470 | $0.02470 |
| Opus 5.5 | $0.00988 | $0.00988 |
| Sonnet 5.5 | $0.00494 | $0.00494 |
| Haiku 4.5 | $0.00247 | $0.00247 |
Grade A, and why
coding-agent-orchestration 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Execution Contract (Repo Baseline)
Purpose
This file defines the working contract for coding agents and humans collaborating in this repository.
- This repo uses project-local workflow files stored under
.vibe/. - The agent must follow the precedence order and stop conditions below.
- This baseline is intended to be copied into target repos and may drift per project.
Authoritative files and precedence
When instructions conflict, follow this order:
- User instructions in the current chat
- This file:
AGENTS.md .vibe/STATE.md(current truth: what we are doing now).vibe/PLAN.md(checkpoint backlog and acceptance criteria).vibe/HISTORY.md(non-authoritative rollups, context only)- Repository source code and tests
- Anything else (including assumptions)
Required behavior
Read order at the start of a session
At the start of any new session (or when context is unclear), the agent must:
- Read
AGENTS.md(optional if already read this session) - Read
.vibe/STATE.md - Read
.vibe/PLAN.md - Optionally read
.vibe/HISTORY.mdif needed
Work granularity
- Do one coherent unit of work at a time (typically one checkpoint step).
- Prefer small, reviewable diffs.
- When ambiguity affects correctness, ask 1–2 clarifying questions max as issues in
.vibe/STATE.md, then stop.
Deferral for throughput
- If an issue, checkpoint, or stage is blocked but later independent work can safely proceed, mark it
[DEFERRED]and move on instead of stopping the project. - Add a short reason and unblock/revisit condition near the deferred item. Waiting on human feedback is a legitimate deferral reason.
- Do not defer work that a later item depends on unless that later item is also deferred or redesigned; deferral is for preserving momentum, not hiding shaky foundations.
- Revisit
[DEFERRED]items during stage design and consolidation. If the unblock condition is now true, reactivate the item or fold it into the next executable checkpoint.
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 · 190 lines · 2,470 tokens per session scan A 9fc0410cb27f
coding-agent-orchestration AGENTS.md is an instructions file published in the GitHub repository brifl/coding-agent-orchestration (22 stars, last pushed 15d ago), licensed MIT. It adds 2,470 tokens to every session, about $0.0099 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-30.
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.