Borrowing it
Nothing to install: this file belongs to KERNlang/agon. 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/KERNlang/agon/main/AGENTS.mdgit clone --depth 1 https://github.com/KERNlang/agonWrote 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/kernlang/agon/agents-md)<a href="https://agentmods.dev/instructions/kernlang/agon/agents-md"><img src="https://agentmods.dev/badge/instructions/kernlang/agon/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/kernlang/agon/agents-md"><img src="https://agentmods.dev/badge/instructions/kernlang/agon/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.03154 | $0.03154 |
| Opus 5.5 | $0.01262 | $0.01262 |
| Sonnet 5.5 | $0.00631 | $0.00631 |
| Haiku 4.5 | $0.00315 | $0.00315 |
Grade A, and why
agon 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 4d 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Agon AI
Any AI can join. They compete. You ship.
Agon is a multi-AI orchestration framework. Registered engines compete via forge, debate via tribunal, and ideate via brainstorm. Cesar orchestrates from live capability, availability, confidence, and task evidence. Canonical cross-agent doctrine: ~/.ai/AGENTS.md (loaded by Cesar via ~/.agon/AGENTS.md); Agon-specific global conventions: ~/.agon/AGON.md.
Using Agon From Codex
Codex agents should use Agon when the task benefits from multiple engines, adversarial review, team competition, or confidence-weighted ideation, but interactive chat must never auto-start these modes just because the user mentions "brainstorm", "tribunal", "forge", or "review". In the Agon UI, orchestration starts only from explicit slash commands (/brainstorm, /tribunal, /forge, /review, etc.) or from explicit CLI/MCP calls. If the user is speaking normally, suggest the slash command instead of starting the workflow.
For non-interactive Codex shell work, the fastest path is the shell bridge:
agon call brainstorm "What approaches should we consider for this migration?"
agon call tribunal "Should we ship this architecture?" --tribunalMode red-team --rounds 2
agon call forge "Implement the cache layer" --test "npm test"
agon call synthesis "Evolve this design doc into a concrete implementation plan" --swaps 2 --timeout 90
agon call review
If agon is not linked in the shell, build/link it first:
npm run build
npm run install:cli
Machine-readable callers should add --jsonl:
agon call brainstorm "Compare options for this refactor" --jsonl
Use --cwd <path> when the target repository is not the current working directory. Use --engines <comma-separated-registered-ids> only when the user explicitly requests manual pinning. Use --timeout <seconds> for long-running tasks.
External engines should always call Agon through the shell bridge, not direct model CLIs:
agon call <workflow> "<input>" [flags]
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.
- 4d ago Changed · +13 tokens per session 08d182a9d4d5
- 2mo ago First seen · 239 lines · 3,141 tokens per session scan A 5e9138449885
agon AGENTS.md is an instructions file published in the GitHub repository KERNlang/agon (17 stars, last pushed today), licensed MIT. It adds 3,154 tokens to every session, about $0.0126 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.