What is Zoo-Code AGENTS.md?

Repository instructions for Zoo-Code, including rules for settings changes, lint suppressions, changesets, and changelog updates.

They are for changing the settings view, handling ESLint suppressions, and following the project’s release-file rules.

They prevent common maintenance mistakes, such as binding settings to live state or increasing file-specific lint exceptions.

How Zoo-Code-Org/Zoo-Code configures Codex and OpenCode

About the project

Zoo Code is a code-editor extension that provides a team of AI agents for software development. Developers use it for coding assistance, code search, task coordination, and autonomous work, while the catalogue entries extend its workflows.

Zoo-Code-Org/Zoo-Code · 2,093 stars · on GitHub · zoocode.dev

Reuse

Borrowing it

Nothing to install: this file belongs to Zoo-Code-Org/Zoo-Code. 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/Zoo-Code-Org/Zoo-Code/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/Zoo-Code-Org/Zoo-Code

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

README.md

[![agentmods](https://agentmods.dev/badge/instructions/zoo-code-org/zoo-code/agents-md/github.svg)](https://agentmods.dev/instructions/zoo-code-org/zoo-code/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/zoo-code-org/zoo-code/agents-md"><img src="https://agentmods.dev/badge/instructions/zoo-code-org/zoo-code/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/zoo-code-org/zoo-code/agents-md"><img src="https://agentmods.dev/badge/instructions/zoo-code-org/zoo-code/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,852 This file is loaded in full into every session.

When invoked 1,852 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.

Model	Per session	Once invoked
Fable 5.1	$0.01852	$0.01852
Opus 5.5	$0.00741	$0.00741
Sonnet 5.5	$0.00370	$0.00370
Haiku 4.5	$0.00185	$0.00185

Measured 19d ago against content hash 30a9bffa1e68, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

Zoo-Code 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 19d 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 · 76 lines

How it starts

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

AGENTS.md

This file provides guidance to agents when working with code in this repository.

Settings View Pattern: When working on SettingsView, inputs must bind to the local cachedState, NOT the live useExtensionState(). The cachedState acts as a buffer for user edits, isolating them from the ContextProxy source-of-truth until the user explicitly clicks "Save". Wiring inputs directly to the live state causes race conditions.
Changesets: Do NOT create .changeset files for each commit or code change. Changesets are managed separately by maintainers and should not be generated by agents during normal development.
CHANGELOG: Do NOT update CHANGELOG.md or src/CHANGELOG.md in individual PRs. CHANGELOG entries are added in bulk during release preparation PRs.

ESLint Suppressions

src/eslint-suppressions.json tracks per-file counts of suppressed lint rules. Suppression counts must never increase. When touching a file, prefer reducing its count when the fix is local and low-risk; avoid broad unrelated cleanup.

When writing new code:

Fix lint violations in the new code rather than suppressing them.
Avoid as any; use typed APIs directly (e.g. RooCodeEventName.X constants with typed on()/listenerCount()), or bracket notation (obj["privateField"]) to access private members. Prefer precise test doubles or unknown with a type guard over double assertions (as unknown as T); use double assertions only as a last resort, with a comment explaining why.
Avoid floating promises; add void, await, or .catch() as appropriate.
After editing a file, run pnpm --dir src exec eslint --prune-suppressions --max-warnings=0 <relative-file> and confirm the count for that file did not increase.
If a suppression is truly unavoidable (e.g. vi.spyOn(Cls.prototype as any, "privateMethod") where no typed alternative exists), document why in a comment next to the cast.

Typed test files

New or substantially changed test files must not add @typescript-eslint/no-explicit-any suppression entries to src/eslint-suppressions.json:

Read the full file on GitHub · 76 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.

19d ago Changed · +3 lines · +94 tokens per session 30a9bffa1e68
24d ago Changed · +10 lines · +245 tokens per session dfc3b28107c8
1mo ago Changed · +1 lines · +57 tokens per session 552d08d9f018
2mo ago Changed · +7 lines · +169 tokens per session 736056844882
2mo ago First seen · 55 lines · 1,287 tokens per session scan A b2f38d080885

Subscribe to this mod's changes

Zoo-Code AGENTS.md is an instructions file published in the GitHub repository Zoo-Code-Org/Zoo-Code (2,093 stars, last pushed today), licensed Apache-2.0. It adds 1,852 tokens to every session, about $0.0074 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.

Zoo-Code AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
Zoo-Code AGENTS.mdZoo-Code-Org/Zoo-Code	Instructions file	2.1k	today	Apache-2.0	A	1,852	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

Zoo-Code: Instructions file for Codex