Borrowing it
Nothing to install: this file belongs to Avyayalaya/agent-council. 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/Avyayalaya/agent-council/main/AGENTS.mdgit clone --depth 1 https://github.com/Avyayalaya/agent-councilWrote 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/avyayalaya/agent-council/agents-md)<a href="https://agentmods.dev/instructions/avyayalaya/agent-council/agents-md"><img src="https://agentmods.dev/badge/instructions/avyayalaya/agent-council/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/avyayalaya/agent-council/agents-md"><img src="https://agentmods.dev/badge/instructions/avyayalaya/agent-council/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.02230 | $0.02230 |
| Opus 5.5 | $0.00892 | $0.00892 |
| Sonnet 5.5 | $0.00446 | $0.00446 |
| Haiku 4.5 | $0.00223 | $0.00223 |
Grade A, and why
agent-council 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.
How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Agent Council capability manifest
This file declares the Council to other AI systems and orchestrators. Three layers: identity, evaluability, composability. They are all in this file.
Identity
Name: agent_council (Python package); agent-council (CLI binary).
Version: 0.1.0 (P0 — Week 1 scaffold).
One-paragraph capability:
The Agent Council is a runtime-portable quality gate. Given any text artifact and a config, it runs five role-conditioned LLM deliberators in a 2-round async protocol with cross-read rebuttal, then synthesizes a single verdict — SHIP, REVISE, or HOLD — plus a revision brief and a full audit transcript. It depends on no SDK and no API keys: a runtime adapter shells out to whatever CLI is configured (
claude,gh copilot,ollama, etc.). It is designed to gate tier-1 artifacts — external-facing, irreversible, identity-shaping, or memory writes — before they persist or publish.
What it does well:
- Catches voice violations, evidence gaps, and strategic mis-alignment that the artifact's producing agent missed.
- Surfaces dissent transparently — every deliberator's score, blocking flag, and irreducible flag is logged.
- Compounds across runs — prior verdicts on the same
artifact_typeare loaded into the Adjudicator's context. - Stays portable — adding a new LLM CLI is one new file in
runtimes/.
What it is not:
- It is not a writing tool. It does not produce artifacts; it gates them.
- It is not a generic LLM-as-judge. It is structured around five named roles, each with a Context Verification Gate and a typed output schema.
- It is not a fact-checker for the open web. Source verification stays inside the Evidence deliberator's tiered framework — accuracy is the operator's responsibility.
- It is not a replacement for the operator's own review. It is the gate before the operator's review, not after.
When to invoke:
- An artifact is tier-1 (external, irreversible, identity-shaping, or a memory write).
- The artifact has cleared its producing agent's quality gate but has not yet been published / committed / persisted.
- The operator wants structured dissent before shipping — not just "looks good."
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 · 181 lines · 2,230 tokens per session scan A 764f73c86ad4
agent-council AGENTS.md is an instructions file published in the GitHub repository Avyayalaya/agent-council (11 stars, last pushed 3mo ago), licensed MIT. It adds 2,230 tokens to every session, about $0.0089 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.
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.