Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/cote-star/agent-chorus/agents-mdgit clone --depth 1 https://github.com/cote-star/agent-chorusWrote 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/cote-star/agent-chorus/agents-md)<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="Measured on agentmods" 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 | $0.01511 | $0.01511 |
| Opus 5 | $0.00756 | $0.00756 |
| Sonnet 5 | $0.00302 | $0.00302 |
| Haiku 4.5 | $0.00151 | $0.00151 |
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 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
- Read .agent-context/current/routes.json to identify task type
- Load contracts from .agent-context/current/completeness_contract.json + .agent-context/current/search_scope.json
- Search ONLY within scoped directories defined in search_scope.json
- Do not open repo source files before step 3
Context Pack
When asked to understand this repository:
- Read
.agent-context/current/00_START_HERE.md. - Read
.agent-context/current/routes.json. - Identify the active task type in
routes.json. - Read the matching entries in
completeness_contract.json,reporting_rules.json, andsearch_scope.json. - Search ONLY within the directories listed in
search_scope.jsonfor your task type. - Use
verification_shortcutsto check specific line ranges instead of reading full files. - Do not enumerate files in directories marked
exclude_from_search. - 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:
- Read
.agent-context/current/00_START_HERE.mdfirst. - Use
.agent-context/current/manifest.json+20_CODE_MAP.mdto target only relevant source files. - 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.
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 First seen · 153 lines · 1,511 tokens per session scan A 638e7609f954
agent-chorus AGENTS.md is an instructions file published in the GitHub repository cote-star/agent-chorus (13 stars, last pushed 2mo ago), licensed MIT. It adds 1,511 tokens to every session, about $0.0076 per session on Opus 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
cocoindex AGENTS.md
AGENTS.md instructions for cocoindex-io/cocoindex, covering agents.md, build and test commands, building, testing and code formatting and linting.
apm python.instructions.md
Python development guidelines.
framework AGENTS.md
AGENTS.md instructions for ai-driven-dev/framework, covering agents.md, behavior, communication, action and memory management.
Commit Message
Comprehensive Conventional Commits guidelines for openwebui-extensions.
Meterless AGENTS.md
Instructions for Meterless/Meterless, covering agent instructions for meterless, routing table, isolation rule, repo-wide rules and non-coding agents.
apm linting.instructions.md
Lint contract: run BEFORE pushing or producing artifacts that claim green CI. Mirrors the CI Lint job.