agent-chorus: Instructions file for Claude Code

AGENTS.md

agent-chorus AGENTS.md is an instructions file for Claude Code, Codex, OpenCode from cote-star/agent-chorus. It costs 1,511 tokens per session, scanned A, original, MIT.

Repository instructions for Agent Chorus that route each task through structured context files, completeness rules, reporting rules, and an allowed search area. A monorepo is a repository containing multiple related parts or projects.

In plain words
What is it for?
Use them when investigating the codebase, selecting the right task procedure, checking required files, or handling a missing or outdated context pack.
Why use it?
They limit an agent's search to the files relevant to the task, which makes work more focused and helps prevent missed project rules.

Instructions file for Claude CodeCodexOpenCode

Written for Claude Code and Codex and OpenCode: SessionEnd hook event, but also the file is AGENTS.md. Also seen: mentions Claude Code; mentions Codex.

This is cote-star/agent-chorus's own configuration. It tells Claude Code, Codex and OpenCode how to work on agent-chorus itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agent-chorus configures →

Reuse

Borrowing it

Nothing to install: this file belongs to cote-star/agent-chorus. 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/cote-star/agent-chorus/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/cote-star/agent-chorus

Made for: Claude Code, 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.

agentmods badge for agent-chorus AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/cote-star/agent-chorus/agents-md/github.svg)](https://agentmods.dev/instructions/cote-star/agent-chorus/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/cote-star/agent-chorus/agents-md"><img src="https://agentmods.dev/badge/instructions/cote-star/agent-chorus/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.

agentmods 80×15 button for agent-chorus AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/cote-star/agent-chorus/agents-md"><img src="https://agentmods.dev/badge/instructions/cote-star/agent-chorus/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,511 This file is loaded in full into every session.
When invoked 1,511 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01511 $0.01511
Opus 5.5 $0.00604 $0.00604
Sonnet 5.5 $0.00302 $0.00302
Haiku 4.5 $0.00151 $0.00151

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

Security

Grade A, and why

agent-chorus 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 · 153 lines

How it starts

The opening of the file, as written. The whole thing — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.

  1. Read .agent-context/current/routes.json to identify task type
  2. Load contracts from .agent-context/current/completeness_contract.json + .agent-context/current/search_scope.json
  3. Search ONLY within scoped directories defined in search_scope.json
  4. Do not open repo source files before step 3

Context Pack

When asked to understand this repository:

  1. Read .agent-context/current/00_START_HERE.md.
  2. Read .agent-context/current/routes.json.
  3. Identify the active task type in routes.json.
  4. Read the matching entries in completeness_contract.json, reporting_rules.json, and search_scope.json.
  5. Search ONLY within the directories listed in search_scope.json for your task type.
  6. Use verification_shortcuts to check specific line ranges instead of reading full files.
  7. Do not enumerate files in directories marked exclude_from_search.
  8. Do not open repo files before those steps unless a referenced structured file is missing.

If .agent-context/current/routes.json is missing, fall back to the markdown pack only.

Agent Instructions For This Repo

Naming convention: Use chorus agent-context ... commands. Legacy npm wrappers (npm run agent-context:*) are still available in this repo.

End-to-End Understanding Shortcut

When asked to understand this repository end-to-end:

  1. Read .agent-context/current/00_START_HERE.md first.
  2. Use .agent-context/current/manifest.json + 20_CODE_MAP.md to target only relevant source files.
  3. Open additional files only when the current task requires deeper proof.

If Context Pack Is Missing or Stale

Run:

chorus agent-context init
# ...fill details...
chorus agent-context seal

Main Push Context Sync

Install hook once:

chorus agent-context install-hooks

The pre-push hook prints an advisory warning when a push targets main and changes context-relevant files. It never auto-builds or blocks the push.

Read the full file on GitHub · 153 lines

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.

  1. 1mo ago First seen · 153 lines · 1,511 tokens per session scan A 638e7609f954

Subscribe to this mod's changes

agent-chorus AGENTS.md is an instructions file published in the GitHub repository cote-star/agent-chorus (15 stars, last pushed 22d ago), licensed MIT. It adds 1,511 tokens to every session, about $0.0060 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.

Related

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

microsoft/vscode · 9,649 tokens

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.

vercel/next.js · 7,384 tokens

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

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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

microsoft/vscode · 2,731 tokens

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.

deepseek-ai/deepseek-harness · 4,159 tokens