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/larens94/codedna/agents-mdgit clone --depth 1 https://github.com/Larens94/codednaWhat 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.03041 | $0.03041 |
| Opus 5 | $0.01520 | $0.01520 |
| Sonnet 5 | $0.00608 | $0.00608 |
| Haiku 4.5 | $0.00304 | $0.00304 |
Grade A, and why
codedna 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- codedna CLAUDE.md — 88% identical, 40 lines differ
How it starts
The opening of the file, as written. The whole thing — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CodeDNA v0.9 — Protocol for AI Coding Agents (Codex, OpenCode, Aider, GitHub Copilot CLI, etc.)
This project uses the CodeDNA in-source communication protocol. Follow these rules on every file operation.
Reading files
- Read the CodeDNA module header at the top of every supported source file before reading any code. Python uses a module docstring; other languages use their native comment syntax.
- Parse
exports:— these are symbols you must never rename or remove without explicit instruction. - Parse
used_by:— callers that depend on this file. Do not follow all of them blindly. Ask: "does this caller's domain intersect with my current task?" Only explore callers relevant to the specific change you're making. - Parse
related:— files sharing the same logic without importing each other. Same filter: is it relevant to this task? - Parse
rules:— hard constraints for every edit in this file; read before writing any logic. - Parse
agent:— session history written by previous agents; read to understand why the current state exists. - For any function with a
Rules:docstring, read and respect those before writing logic.
Required command workflow
Use the audit commands as evidence gates:
| When | Command | Agent action |
|---|---|---|
| First session/onboarding | codedna doctor --path . |
Fix ERROR items before editing. Report WARNING items as optional integrations. |
| Before changing a public file or symbol | codedna impact <file-or-symbol> --path . |
Read every MATCH rule and inspect domain-relevant AFFECTS files. Exit 1 means resolve the correct query before editing. |
| After structural edits | codedna verify . |
Exit 1 means review evidence, run codedna refresh ., then verify again. Never overwrite semantic rules:. |
| Automation/CI | add --json |
Parse stable structured fields. Exit 0 passes; exit 1 reports actionable findings. |
verify proves structural consistency only (exports: and used_by:); it does not certify that natural-language rules: are semantically true.
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 · 274 lines · 3,041 tokens per session scan A 4009c72dfd7b
codedna AGENTS.md is an instructions file published in the GitHub repository Larens94/codedna (145 stars, last pushed 6d ago), licensed MIT. It adds 3,041 tokens to every session, about $0.0152 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
deepagents AGENTS.md
Instructions for langchain-ai/deepagents, covering global development guidelines for the deep agents monorepo, corridor security analysis, development workflow, suppressing ruff rules and pr conventions.
autoharness AGENTS.md
Instructions for tigerless-labs/autoharness: This repo uses Open Knowledge — collaborative markdown via MCP. .open-knowledge/config.yml (with optional /.open-knowledge/config.yml; CLI/env may override) is the path contract: content.dir is the root for relative paths; content.include lists globs that add markdown…
cookiecutter-mlops-package AGENTS.md
Instructions for fmind/cookiecutter-mlops-package, covering agents.md, project overview, setup & core commands, definition of done and conventions & idioms.
python-cheatsheet copilot-instructions.md
Copilot instructions for labex-labs/python-cheatsheet, covering python cheatsheet - ai coding assistant instructions, project overview, architecture & key patterns, content structure and routing & layout system.
martex-quant CLAUDE.md
Instructions for martex-dev/martex-quant, covering session start — read these first, project instructions, ai trading bot project - master instructions, role and project objective.
ZipAgent AGENTS.md
Instructions for JiayuXu0/ZipAgent, covering repository guidelines, project structure & module organization, build, test & development commands, coding style & naming conventions and testing guidelines.