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/lat-labs/adna/agents-mdgit clone --depth 1 https://github.com/lat-labs/adnaWrote 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/lat-labs/adna/agents-md)<a href="https://agentmods.dev/instructions/lat-labs/adna/agents-md"><img src="https://agentmods.dev/badge/instructions/lat-labs/adna/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.00683 | $0.00683 |
| Opus 5 | $0.00342 | $0.00342 |
| Sonnet 5 | $0.00137 | $0.00137 |
| Haiku 4.5 | $0.00068 | $0.00068 |
Grade A, and why
adna 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.
adna — Agent Guide
Purpose
This is the root agent reference for the adna project. It routes agents to the appropriate triad leg (what/how/who) based on their current task. This file is always loaded — it does not have a Load/Skip section because agents need it for orientation on every session.
Quick Orientation
| Document | What You'll Find |
|---|---|
| CLAUDE.md | Agent operating context — safety rules, startup checklist, protocols |
| MANIFEST.md | Project overview — architecture, entry points, active builds |
| STATE.md | Current operational state — phase, blockers, next steps |
| README.md | Human-readable getting-started guide |
Project Structure
adna/
├── what/ # WHAT — Knowledge objects, context library, decisions, docs, lattices
├── how/ # HOW — Campaigns, missions, sessions, templates, pipelines, skills, backlog
└── who/ # WHO — Coordination, governance (extend with team/, customers/, etc.)
Navigation: Read this file → follow the Layer References below into the triad leg matching your task → drill into specific subdirectories as needed. Each AGENTS.md narrows context progressively.
Agent Startup
- CLAUDE.md — auto-loaded; confirms project structure and rules
- First-run check — if uncustomized vault, invoke onboarding skill (
how/skills/skill_onboarding.md) - STATE.md — operational snapshot: current phase, blockers, next steps
how/sessions/active/— check for conflicting sessionswho/coordination/— read any urgent cross-agent noteshow/backlog/— quick scan for ideas relevant to current sessionhow/campaigns/— check for active campaignshow/missions/— check for active missions- Create session file in
how/sessions/active/and begin work
Layer References
- what/AGENTS — Knowledge objects (WHAT)
- how/AGENTS — Operations (HOW)
- who/AGENTS — Organization (WHO)
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 · 683 tokens per session scan A 7fcab52d2b17
adna AGENTS.md is an instructions file published in the GitHub repository lat-labs/adna (5 stars, last pushed 6mo ago), licensed MIT. It adds 683 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-31.
Other instructions, from other repositories
AndroidAutoX AGENTS.md
AGENTS.md instructions for Xiddoc/AndroidAutoX, covering agents.md, project overview, tech stack, repository layout and autox virtual-display subsystem.
AndroidAutoX CLAUDE.md
Claude Code instructions for Xiddoc/AndroidAutoX, covering claude.md and claude code quick tips.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.