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/gitlawb/zero/agents-mdgit clone --depth 1 https://github.com/Gitlawb/zeroWhat 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.02164 | $0.02164 |
| Opus 5 | $0.01082 | $0.01082 |
| Sonnet 5 | $0.00433 | $0.00433 |
| Haiku 4.5 | $0.00216 | $0.00216 |
Grade A, and why
zero 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines for Zero
These instructions apply to all work in this repository. For the user-facing guide to extending Zero with specialists, hooks, plugins, MCP, and skills, see docs/EXTENDING.md.
1. Contribution and Pull Request Rules
- Before opening any pull request, all contributors—including maintainers, community contributors, and coding agents—must read and follow CONTRIBUTING.md.
- Community pull requests require an existing parent issue with the
issue-approvedlabel. Team members may open pull requests through the internal development process described inCONTRIBUTING.md. - Keep each change focused on the approved or assigned scope. Do not include unrelated fixes, refactors, formatting churn, generated output, or existing local changes in the same commit or pull request.
- Discuss new implementation languages, runtimes, major dependency changes, and broad architectural rewrites with maintainers before implementation.
- Pull request descriptions must explain what changed and why, link the parent issue when required, and list the tests or verification performed. Include screenshots or a short recording for user-visible UI changes when practical.
2. Repository and Implementation Conventions
- Use the Go version declared in
go.mod. Do not hardcode a different local toolchain version in scripts or documentation. - Use the repository build and release commands (
makeandgo run ./cmd/zero-release ...) instead of inventing parallel build flows. - Keep tests beside their source files (
foo_test.gonext tofoo.go). Add a regression test for behavior changes and run affected concurrent code under the race detector. - Never edit files under
third_party/; they are vendored. - Prefer one cross-platform function with small conditional checks over duplicated platform-specific helpers when the behavior can remain unified.
- Do not commit generated benchmark reports from
internal/perfbench/reports/*.json; reports are configuration-specific evidence, not repository state. - Preserve the user's working tree. Do not overwrite, delete, stage, or commit unrelated tracked or untracked files.
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 · 153 lines · 2,164 tokens per session scan A 18fe2e20a18d
zero AGENTS.md is an instructions file published in the GitHub repository Gitlawb/zero (1,641 stars, last pushed 2d ago), licensed MIT. It adds 2,164 tokens to every session, about $0.0108 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
CodeAuto AGENTS.md
Instructions for Yulin-Bi/CodeAuto, a project described as: CodeAuto is an intelligent programming assistant developed using Java, drawing inspiration from Claude Code and Minicode.
CluxMate AGENTS.md
Instructions for r1c7/CluxMate, covering project memory, what cluxmate is, architecture — core invariants, security: sandbox (read the docs before touching this code) and hooks.
CodeAuto CLAUDE.md
Instructions for Yulin-Bi/CodeAuto, a project described as: CodeAuto is an intelligent programming assistant developed using Java, drawing inspiration from Claude Code and Minicode.
seektty AGENTS.md
Instructions for Hilbert-beinghappy/seektty: This repository ships one out-of-tree DeepSeek Harness Bundle. Harness remains the only owner of Agent, Session, model, settings, permissions, Profile, plugin, and persistence state.
amp-acp AGENTS.md
Instructions for tao12345666333/amp-acp, covering agents.md, commands, architecture and code style.
roamcode AGENTS.md
Instructions for burakgon/roamcode, covering repository instructions for coding agents, public-repository safety, stable release and ota contract, releasing a stable version and ota changes.