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/claude-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/claude-md)<a href="https://agentmods.dev/instructions/cote-star/agent-chorus/claude-md"><img src="https://agentmods.dev/badge/instructions/cote-star/agent-chorus/claude-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.1 | $0.01924 | $0.01924 |
| Opus 5 | $0.00962 | $0.00962 |
| Sonnet 5 | $0.00385 | $0.00385 |
| Haiku 4.5 | $0.00192 | $0.00192 |
Grade B, and why
agent-chorus CLAUDE.md scanned grade B with 1 finding 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 5d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Install by adding to `~/.claude/settings.json`: How it starts
The opening of the file, as written. The whole thing — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BEFORE starting any task, read these 3 files in order:
- .agent-context/current/00_START_HERE.md
- .agent-context/current/30_BEHAVIORAL_INVARIANTS.md
- .agent-context/current/20_CODE_MAP.md Do NOT open repo source files until steps 1-3 are complete. Then open only files .agent-context identifies as relevant to your task.
Context Pack
BEFORE starting any task, read the context pack in this order:
.agent-context/current/00_START_HERE.md— entrypoint, routing, stop rules.agent-context/current/30_BEHAVIORAL_INVARIANTS.md— change checklists, file families, what NOT to do.agent-context/current/20_CODE_MAP.md— navigation index, tracing flows
Read these three files BEFORE opening any repo source files. Then open only the files the pack identifies as relevant.
For architecture questions, also read 10_SYSTEM_OVERVIEW.md. For test/deploy questions, also read 40_OPERATIONS_AND_RELEASE.md.
Claude Code Instructions
Naming convention: Use
chorus agent-context ...commands. Legacy npm wrappers (npm run agent-context:*) are still available in this repo.
Context Pack
When asked to understand this repository (or any "what does this repo do?" intent):
- Read
.agent-context/current/00_START_HERE.mdfirst. - Follow the read order defined in that file (
10_SYSTEM_OVERVIEW.md, then30_BEHAVIORAL_INVARIANTS.md, then20_CODE_MAP.md, then40_OPERATIONS_AND_RELEASE.md). - Only open project files when the context pack identifies a specific target.
If the context pack is missing, run:
chorus agent-context init
# ...fill in template sections...
chorus agent-context seal
If the context pack is stale (already initialized), run:
chorus agent-context seal
Context Pack Maintenance
After making changes to source files, check whether .agent-context/current/
needs updating. If the changes affect architecture, commands, behavioral
invariants, or the code map, run:
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.
- 5d ago First seen · 201 lines · 1,924 tokens per session scan B 18c9ed67a32a
agent-chorus CLAUDE.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,924 tokens to every session, about $0.0096 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
apm python.instructions.md
Python development guidelines.
Commit Message
Comprehensive Conventional Commits guidelines for openwebui-extensions.
framework AGENTS.md
AGENTS.md instructions for ai-driven-dev/framework, covering agents.md, behavior, communication, action and memory management.
packmind packmind-rest-api-endpoint-design.instructions.md
Instructions for PackmindHub/packmind: Conventions for designing REST API endpoints that are predictable, self-documenting, and aligned with distinct business actions. Favors dedicated action endpoints over generic status updates, and rout... .
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.