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/sethdeckard/atria/agents-mdgit clone --depth 1 https://github.com/sethdeckard/atriaWhat 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.04703 | $0.04703 |
| Opus 5 | $0.02351 | $0.02351 |
| Sonnet 5 | $0.00941 | $0.00941 |
| Haiku 4.5 | $0.00470 | $0.00470 |
Grade A, and why
atria 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 2d 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 — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atria - Agent Conventions
Internal development conventions. See README.md for user documentation.
Project Overview
Atria is a Go TUI tool for managing multiple AI coding agents (Claude Code, Codex, OpenCode) running in terminal tabs/panes. Built with Bubble Tea (bubbletea, lipgloss, bubbles).
Code Style
- Idiomatic Go: follow Effective Go patterns, standard naming conventions
- Format all code with
gofmt/goimports - Error handling: return errors, don't panic. Wrap errors with context using
fmt.Errorf("context: %w", err) - No
log.Fatalin library code (internal packages). Onlymain.gomay exit the process
Commit Messages
- Subject: max 50 chars, capitalized, imperative mood (e.g. "Add feature" not "Added feature")
- Blank line between subject and body
- Body: wrapped at 72 chars, describe what and why, not how
Project Structure
main.go # Entry point
internal/
config/config.go # TOML config parsing
model/types.go # Domain types (Project, AgentSession, etc.)
model/store.go # In-memory store + JSON persistence
terminal/backend.go # Backend interface
terminal/detect.go # Agent detection from session name
terminal/monitor.go # Log reading + status classification
terminal/composite.go # Composite backend (PTY + integrations)
terminal/cache.go # Cached session list with TTL
terminal/cwd.go # CWD discovery strategies (shared)
terminal/kitty/client.go # Kitty backend (kitten @ CLI via socket)
terminal/wezterm/client.go # WezTerm backend (wezterm cli)
terminal/iterm/proto/api.proto # iTerm2 protobuf spec (trimmed)
terminal/iterm/proto/api.pb.go # Generated protobuf Go code
terminal/iterm/conn.go # iTerm2 WebSocket connection manager
terminal/iterm/client.go # iTerm2 backend (native protobuf API)
terminal/tmux/client.go # tmux backend
terminal/pty/client.go # PTY backend (built-in multiplexer)
terminal/pty/session.go # PTY session (process + vt10x emulator)
tui/app.go # Root Bubble Tea model
tui/messages.go # tea.Msg types
tui/commands.go # tea.Cmd factories
tui/keys.go # Key bindings
tui/styles.go # Lip Gloss styles
tui/settings.go # Settings screen (config editor)
tui/projectlist.go # Agent list view (agents dashboard)
tui/chatview.go # Chat/send view
tui/termview.go # Embedded terminal view (PTY backend)
tui/paths.go # Path display utilities (contractHome)
tui/gitinfo.go # Git worktree detection
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.
- 2d ago First seen · 326 lines · 4,703 tokens per session scan A 3397bd249963
atria AGENTS.md is an instructions file published in the GitHub repository sethdeckard/atria (20 stars, last pushed 1mo ago), licensed MIT. It adds 4,703 tokens to every session, about $0.0235 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
langgraph AGENTS.md
AGENTS.md instructions for langchain-ai/langgraph, covering agents instructions, corridor security analysis, libraries and dependency map.
agentgateway copilot-instructions.md
Copilot instructions for agentgateway/agentgateway: Do not check for, speculate about, or report compilation errors during code review. Compilation diagnostics from review are frequently incorrect; rely on CI to detect and report compilation failures.
hatch3r CLAUDE.md
Instructions for hatch3r/hatch3r, covering hatch3r — development instructions, architecture, development commands, two-axis pillar framework (2.0.0) and orchestrator self-discipline (bypass protection).
aeon CLAUDE.md
Instructions for aeonfun/aeon, covering aeon, how aeon works, strategy, voice and soul file hierarchy (read in this order).
ken CLAUDE.md
Instructions for townsendmerino/ken, covering claude.md, what this is, repository ownership (read this first), commands and embedding parity & golden fixtures (now in aikit).
gangsta GEMINI.md
Instructions for kucherenko/gangsta, a project described as: AI agentic skills framework for spec-driven development, built on the organizational model of mafia.