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.
curl -O https://raw.githubusercontent.com/cote-star/agent-chorus/main/GEMINI.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/gemini-md)<a href="https://agentmods.dev/instructions/cote-star/agent-chorus/gemini-md"><img src="https://agentmods.dev/badge/instructions/cote-star/agent-chorus/gemini-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/cote-star/agent-chorus/gemini-md"><img src="https://agentmods.dev/badge/instructions/cote-star/agent-chorus/gemini-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.01429 | $0.01429 |
| Opus 5.5 | $0.00572 | $0.00572 |
| Sonnet 5.5 | $0.00286 | $0.00286 |
| Haiku 4.5 | $0.00143 | $0.00143 |
Grade A, and why
agent-chorus GEMINI.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 — 147 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
When asked to understand this repository:
- Read
.agent-context/current/00_START_HERE.mdfirst. - Follow the read order defined in that file.
- Use the structured files if present for task routing, grouped reporting, and stop conditions.
- Only open project files when the context pack identifies a specific target.
Gemini Instructions For This Repo
Naming convention: Use
chorus agent-context ...commands. Legacy npm wrappers (npm run agent-context:*) are still available in this repo.
If Context Pack Is Missing or Stale
chorus agent-context init
# ...fill template sections...
chorus agent-context seal
Agent Chorus Integration
This project is wired for cross-agent coordination via chorus.
Provider snippet: .agent-chorus/providers/gemini.md.
When a user asks about another agent's activity ("What is Claude doing?", "Compare Codex and Gemini outputs"), run Chorus commands first and answer with evidence from session output rather than reasoning.
Available Commands
chorus read --agent <agent> [--id=<id>] [--cwd=<path>] [--chats-dir=<path>] [--last=<N>] [--json] [--include-user] [--tool-calls] [--format=<json|markdown>] [--metadata-only] [--audit-redactions]
chorus summary --agent <agent> [--cwd=<path>] [--format=<json|markdown>] [--json]
chorus timeline [--agent <agent>]... [--cwd=<path>] [--limit=<N>] [--format=<json|markdown>] [--json]
chorus list --agent <agent> [--cwd=<path>] [--limit=<N>] [--json]
chorus search <query> --agent <agent> [--cwd=<path>] [--json]
chorus compare --source <agent[:id]>... [--cwd=<path>] [--json]
chorus diff --agent <agent> --from <id1> --to <id2> [--cwd=<path>] [--json]
chorus send --from <agent> --to <agent> --message <text> [--cwd=<path>]
chorus messages --agent <agent> [--cwd=<path>] [--clear] [--json]
chorus checkpoint --from <agent> [--cwd=<path>] [--message=<text>] [--json]
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 · 147 lines · 1,429 tokens per session scan A 0890f78a4c43
agent-chorus GEMINI.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,429 tokens to every session, about $0.0057 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).
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.