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/zoo-code-org/zoo-code/agents-mdgit clone --depth 1 https://github.com/Zoo-Code-Org/Zoo-CodeWhat 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.01287 | $0.01287 |
| Opus 5 | $0.00643 | $0.00643 |
| Sonnet 5 | $0.00257 | $0.00257 |
| Haiku 4.5 | $0.00129 | $0.00129 |
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 yesterday.
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 — 55 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 localcachedState, NOT the liveuseExtensionState(). ThecachedStateacts as a buffer for user edits, isolating them from theContextProxysource-of-truth until the user explicitly clicks "Save". Wiring inputs directly to the live state causes race conditions. - Changesets: Do NOT create
.changesetfiles 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.mdorsrc/CHANGELOG.mdin 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.Xconstants with typedon()/listenerCount()), or bracket notation (obj["privateField"]) to access private members. Prefer precise test doubles orunknownwith 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.
Persisted Setting Checklist
When adding or changing a user setting, trace the complete round trip. A setting is not complete merely because its control renders or its value reaches storage.
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.
- yesterday First seen · 55 lines · 1,287 tokens per session scan A b2f38d080885
Zoo-Code AGENTS.md is an instructions file published in the GitHub repository Zoo-Code-Org/Zoo-Code (1,752 stars, last pushed yesterday), licensed Apache-2.0. It adds 1,287 tokens to every session, about $0.0064 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
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
buildNext
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
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, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain 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.