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/genai-io/san/agents-mdgit clone --depth 1 https://github.com/genai-io/sanWrote 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/genai-io/san/agents-md)<a href="https://agentmods.dev/instructions/genai-io/san/agents-md"><img src="https://agentmods.dev/badge/instructions/genai-io/san/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.00676 | $0.00676 |
| Opus 5 | $0.00338 | $0.00338 |
| Sonnet 5 | $0.00135 | $0.00135 |
| Haiku 4.5 | $0.00068 | $0.00068 |
Grade A, and why
san 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
San Agent Guide
This file is the short navigation map for agents and contributors. Keep durable
knowledge in docs/; keep this file focused on where to look and what rules to
follow before changing code.
San follows the AGENTS.md standard, so this file is both
the navigation aid for whoever opens the repository and the project
instructions loaded into the running agent's context at session start. Keep it
short: pointers and rules only. Uncommitted personal notes belong in
AGENTS.local.md (git-ignored); a subdirectory with its own conventions can
carry its own AGENTS.md, and the file nearest the working directory wins.
Start Here
- Product overview:
README.md - Documentation index:
docs/index.md - Detailed architecture:
docs/concepts/architecture.md - Package map and ownership:
docs/reference/package-map.md - Dependency rules:
docs/reference/dependency-rules.md - Feature notes:
docs/packages/index.md - Development workflow:
docs/operations/development.md
Repository Shape
cmd/san: CLI entrypoint and command wiring.internal/app: Bubble Tea TUI shell, model composition, event routing.internal/core: stable agent, message, tool, and system-prompt contracts.internal/agent: agent construction and session-facing runtime setup.internal/llm: model provider registry, clients, cost and logging helpers.internal/tool: built-in tool registry, schemas, adapters, and executors.internal/session: transcript persistence, projection, metadata, resume.internal/task,internal/subagent,internal/cron: background work and orchestration.internal/command,internal/skill,internal/plugin,internal/mcp,internal/hook: extension surfaces.internal/setting,internal/persona: configuration and persona overlays.internal/log,internal/secret,internal/filecache,internal/markdown,internal/confdir: infrastructure helpers.internal/selflearn: background memory and skill review loop.docs: durable explanations, design decisions, operations, and references.
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 · 66 lines · 676 tokens per session scan A 49bfa96d556b
san AGENTS.md is an instructions file published in the GitHub repository genai-io/san (76 stars, last pushed yesterday), licensed Apache-2.0. It adds 676 tokens to every session, about $0.0034 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
autolith AGENTS.md
AGENTS.md instructions for lambda-symbolics/autolith, covering repository guidelines, purpose and sources of truth, upstream references, architectural guardrails and package policy.
senpi AGENTS.md
AGENTS.md instructions for code-yeongyu/senpi, covering senpi repository guide, mandatory execution protocols — non-negotiable, protocol 1 — explicitly requested modifications, protocol 2 — user-requested pr reviews and structure.
x-code-cli AGENTS.md
AGENTS.md instructions for woai3c/x-code-cli, covering agents.md, rules, commands, delivery workflow and architecture.
my-pi AGENTS.md
Instructions for spences10/my-pi, covering agents.md, orientation, repository-specific skills, source of truth order and commit and changeset ownership.
neo AGENTS.md
Instructions for owainlewis/neo: You are Neo. You have access to your own documentation here.
pi-ask AGENTS.md
Instructions for eko24ive/pi-ask, covering agents.md, project scope, project goals, tech stack and commands.