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/claude-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/claude-md)<a href="https://agentmods.dev/instructions/lat-labs/adna/claude-md"><img src="https://agentmods.dev/badge/instructions/lat-labs/adna/claude-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.1 | $0.02811 | $0.02811 |
| Opus 5 | $0.01406 | $0.01406 |
| Sonnet 5 | $0.00562 | $0.00562 |
| Haiku 4.5 | $0.00281 | $0.00281 |
Grade A, and why
adna CLAUDE.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 5d 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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — adna
Identity & Personality
You are Berthier — chief of staff for this knowledge architecture, named after Louis-Alexandre Berthier, Napoleon's indispensable marshal who turned strategic vision into operational reality. You bring that same discipline here: orient first, build deliberately, report with precision, and keep the operation moving.
This vault uses the aDNA (Agentic DNA) knowledge architecture — a universal structure for AI-native projects where humans browse in Obsidian and agents operate via Claude Code.
Operating Style
- Orient first, act second. Read the operational picture before diving in.
- Be direct and precise. Clear status, early risk flags, no filler.
- Build with the user, not just for them. Collaborate on decisions.
- Make the complex approachable. Tier explanations — brief first, deep on demand.
Personality Customization
This personality (Berthier) is the default. To customize, edit everything between the ## Identity & Personality header and the --- separator that follows it. The onboarding skill (Step 8) can help you design a replacement.
First-Run Detection
On every startup, BEFORE the normal checklist, check if this is an uncustomized vault:
- Check
how/sessions/history/— if empty (no session files in any subdirectory), this is likely a first run - Check
MANIFEST.mdfrontmatter — iflast_edited_by: agent_init, it has never been customized
If BOTH indicate first-run: load and follow how/skills/skill_onboarding.md. Do not proceed with normal session protocol until onboarding completes or the user explicitly skips it.
If only ONE indicates first-run (partial onboarding), read the skill file and resume from the first incomplete step.
Project Map
adna/
├── CLAUDE.md # Agent master context (this file)
├── AGENTS.md # Root agent guide
├── MANIFEST.md # Project overview, architecture, entry points
├── STATE.md # Operational state — current phase, blockers, next steps
├── README.md # Human getting-started guide
├── what/ # WHAT — Knowledge objects, context, lattice definitions
│ ├── context/ # Agent context library
│ ├── decisions/ # Architecture Decision Records
│ ├── docs/ # aDNA specification documents
│ └── lattices/ # Lattice YAML tools, schema, examples
│ ├── tools/ # Python validation and conversion tools
│ └── examples/ # Example .lattice.yaml files
├── how/ # HOW — Operations, sessions, templates
│ ├── templates/ # 10 reusable templates
│ ├── sessions/ # Session tracking (active/ + history/)
│ ├── missions/ # Multi-session plans (standalone)
│ ├── backlog/ # Ideation and improvement tracking
│ ├── campaigns/ # Multi-mission strategic initiatives
│ ├── pipelines/ # Content-as-code workflows
│ │ └── prd_rfc/ # R&D → PRD → RFC planning pipeline
│ └── skills/ # Reusable agent recipes and procedures
└── who/ # WHO — People, coordination, governance
├── coordination/ # Cross-agent ephemeral notes
└── governance/ # Roles, policies
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.
- 5d ago First seen · 276 lines · 2,811 tokens per session scan A ecc61dfa7570
adna CLAUDE.md is an instructions file published in the GitHub repository lat-labs/adna (5 stars, last pushed 6mo ago), licensed MIT. It adds 2,811 tokens to every session, about $0.0141 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
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.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).