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/eryouhao/zano/agents-mdgit clone --depth 1 https://github.com/EryouHao/zanoWrote 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.
[](https://agentmods.dev/instructions/eryouhao/zano/agents-md)<a href="https://agentmods.dev/instructions/eryouhao/zano/agents-md"><img src="https://agentmods.dev/badge/instructions/eryouhao/zano/agents-md.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00797 | $0.00797 |
| Opus 5 | $0.00398 | $0.00398 |
| Sonnet 5 | $0.00159 | $0.00159 |
| Haiku 4.5 | $0.00080 | $0.00080 |
Grade A, and why
zano 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Context for AI coding assistants (Claude Code, Cursor, etc.) working in this repo. For human contributors, start with the README and CONTRIBUTING.md.
What this project is
Zano is a chat platform where humans and AI agents share channels. Agents are long-running Claude Code processes spawned by a local "bridge" daemon; they communicate exclusively through a zano CLI that talks to Supabase. The web UI is Next.js + Supabase Realtime.
Repo shape
apps/web/ Next.js 16 web UI + auth + bridge bootstrap API
apps/bridge/ Local Node daemon (@fehey/zano-bridge on npm)
packages/cli/ The `zano` CLI agents use to chat (@fehey/zano-cli on npm)
packages/db/ SQL schema, RLS, triggers, generated TS types
packages/shared/ Types shared between web/bridge/cli
supabase/ Supabase project config (config.toml only — no migrations)
Tooling: pnpm 10 workspaces + Turborepo. Node ≥ 20.
Where things live
- Database schema:
packages/db/src/schema.sqlis the source of truth. Apply via Supabase SQL editor. RLS lives in the same file plusfix-rls.sql. - Auto-onboarding trigger:
packages/db/src/onboarding-trigger.sql— runs on every new profile to create a default agent + channel. - Bridge entry point:
apps/bridge/src/index.ts→bridge.ts. Subscribes to channels via Supabase Realtime, spawns Claude Code subprocesses throughagent-manager.ts. - Agent system prompt:
apps/bridge/src/system-prompt.ts— read this to understand how agents are expected to behave inside Zano. - CLI commands:
packages/cli/src/index.ts— single file, allzano message …andzano task …subcommands. - Web routes:
apps/web/src/app/(chat)is the chat UI.apps/web/src/app/api/bridge/connect/route.tsis the bootstrap endpoint local bridges hit on startup. - UI primitives:
apps/web/src/components/ui(shadcn-derived) and@base-ui/reactfor accessible behavior. Tailwind v4 + Radix UI Colors (sand scale).
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.
- 4d ago First seen · 57 lines · 797 tokens per session scan A eb3703bfef9d
zano AGENTS.md is an instructions file published in the GitHub repository EryouHao/zano (217 stars, last pushed 3mo ago), licensed MIT. It adds 797 tokens to every session, about $0.0040 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
AionUi AGENTS.md
AGENTS.md instructions for iOfficeAI/AionUi, covering aionui - project guide, code conventions, file & directory structure, naming and ui library & icons.
core CLAUDE.md
Claude Code instructions for module-federation/core, covering claude task parallelization & development guidelines, core principles, maximum parallelization strategy, universal parallel task patterns and for any codebase task.
mastra AGENTS.md
AGENTS.md instructions for mastra-ai/mastra: Unless asked, don't inspect reference or modify examples. Use the most-specific AGENTS.md; for package work, read packages/ /AGENTS.md first.
technocore-chat AGENTS.md
AGENTS.md instructions for flop-labs/technocore-chat: CI runs exactly these — run them before pushing.
souls-directory CLAUDE.md
Instructions for thedaviddias/souls-directory, covering claude.md — project context for ai assistants, project overview, tech stack, critical rules and database is convex.
nextarter-tailwind AGENTS.md
AGENTS.md instructions for agustinusnathaniel/nextarter-tailwind, covering next.js: always read docs before coding, ai agent guidance: nextarter-tailwind, 1. mental model for agents, implementation delegation and tooling strategy.