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/aklivity/zilla/agents-mdgit clone --depth 1 https://github.com/aklivity/zillaWhat 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.03538 | $0.03538 |
| Opus 5 | $0.01769 | $0.01769 |
| Sonnet 5 | $0.00708 | $0.00708 |
| Haiku 4.5 | $0.00354 | $0.00354 |
Grade A, and why
zilla 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.
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 · 316 lines · 3,538 tokens per session scan A bc4b53982914
zilla AGENTS.md is an instructions file published in the GitHub repository aklivity/zilla (1,721 stars, last pushed yesterday), with no licence file. It adds 3,538 tokens to every session, about $0.0177 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
conductor AGENTS.md
Instructions for conductor-oss/conductor, covering agents.md, project overview, setup commands, java version references and code style.
conductor CLAUDE.md
Instructions for conductor-oss/conductor, covering claude.md — conductor (server repo), writing documentation, for each content type, start here, when you can't verify and key source locations.
azure-sdk-for-go AGENTS.md
Instructions for Azure/azure-sdk-for-go, covering agents.md, repository overview, key documentation, go version support and agent capabilities and boundaries.
azure-sdk-for-go go-examples.instructions.md
Instructions for Azure/azure-sdk-for-go, a project described as: This repository is for active development of the Azure SDK for Go. For consumers of the SDK we recommend visiting our public developer docs at.
core copilot-instructions.md
Copilot instructions for home-assistant/core, covering copilot code review instructions, pull request template, breaking change, proposed change and type of change.
hoop CLAUDE.md
Instructions for hoophq/hoop, covering claude.md, project overview, toolchain & prerequisites, architecture and module breakdown.