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/zed-industries/zed/gemini-mdgit clone --depth 1 https://github.com/zed-industries/zedWhat 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.00001 | $0.00001 |
| Opus 5 | $0.00000 | $0.00000 |
| Sonnet 5 | $0.00000 | $0.00000 |
| Haiku 4.5 | $0.00000 | $0.00000 |
Grade A, and why
zed 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 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 1 lines · 1 tokens per session scan A 4321ba53b426
zed GEMINI.md is an instructions file published in the GitHub repository zed-industries/zed (89,467 stars, last pushed yesterday), with no licence file. It adds 1 tokens to every session, about $0.0000 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
gpuix AGENTS.md
Instructions for remorses/gpuix, covering agents.md - gpuix codebase guide, gpuix is a thin layer on gpui, project goal, mouse capture is armed by the press and architecture overview.
gpuix CLAUDE.md
Instructions for remorses/gpuix, a project described as: Node.js & React bindings for Zed’s GPUI. Build memory efficient native apps with React and no Electron.
chroma CLAUDE.md
Instructions for chroma-core/chroma, covering chroma codebase guidelines, commit message style, 50/72 rule and tilt-backed tests.
chroma AGENTS.md
Instructions for chroma-core/chroma: See CLAUDE.md for codebase conventions (commit message format, etc.).
lmnr CLAUDE.md
Instructions for lmnr-ai/lmnr, covering claude.md, project overview, repository structure, development commands and frontend (next.js).
azure-sdk-for-rust pwsh.instructions.md
Instructions for Azure/azure-sdk-for-rust, covering powershell script instructions, path handling, command invocation, output grouping and console output.