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/dbrattli/adc/agents-mdgit clone --depth 1 https://github.com/dbrattli/adcWhat 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.00591 | $0.00591 |
| Opus 5 | $0.00296 | $0.00296 |
| Sonnet 5 | $0.00118 | $0.00118 |
| Haiku 4.5 | $0.00059 | $0.00059 |
Grade A, and why
adc 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
This is a documentation-first repository for the Agent Decision Comments
convention. README.md is the canonical specification: it defines the four
directives, their format, scope, examples, review workflow, and current version.
LICENSE contains the MIT license. There are currently no source, test,
generated, or asset directories. Keep new documentation at the repository root
unless a larger collection clearly warrants a focused directory such as
examples/.
Build, Test, and Development Commands
This repository produces no build artifact. Markdown linting is its primary CI check. Run these commands before submitting a change:
npx --yes [email protected] --config .markdownlint.jsonc "**/*.md"runs the same linter version as CI.git diff --checkdetects trailing whitespace and malformed patches.rg '^#{1,6} ' README.md AGENTS.mdreviews the Markdown heading hierarchy.git diff -- README.md AGENTS.mdgives a focused review of documentation changes.
Also render changed Markdown in a previewer and verify that fenced examples, lists, and headings display correctly.
Coding Style & Naming Conventions
Write concise Markdown with ATX headings (## Heading), fenced code blocks
with language tags, and hyphenated bullets. Follow the existing prose style:
short paragraphs, direct present-tense statements, and one sentence per line
when practical. Use the exact lowercase directive labels decision:,
invariant:, assumption:, and tradeoff:. Examples should demonstrate
non-obvious rationale rather than restate code behavior. The Markdownlint
configuration excludes code blocks from MD013; directives must remain on one
physical line. In docstrings and documentation comments, place normal prose
before the directives with a blank line between them. Use ordinary comments for
directive-only examples.
Testing Guidelines
The workflow in .github/workflows/markdownlint.yml lints every Markdown file
on pushes and pull requests. Confirm every new example matches the format and
scope rules in README.md, uses valid syntax for its declared language, and
does not contradict another section. Run the local lint command and
git diff --check, then inspect the rendered output.
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 · 59 lines · 591 tokens per session scan A b1467d787864
adc AGENTS.md is an instructions file published in the GitHub repository dbrattli/adc (5 stars, last pushed 16d ago), licensed MIT. It adds 591 tokens to every session, about $0.0030 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
redraft CLAUDE.md
Instructions for KaelinGraf/redraft, covering redraft (engine), running tests, rebuilding the ui and the organizing protocol.
ephemeral-sandbox CLAUDE.md
Instructions for Ephemeral-AI-Lab/ephemeral-sandbox, covering claude.md, project, engineering practice (required), build & test and sandbox tools.
matt-skills-with-to-goal CLAUDE.md
Instructions for tt-a1i/matt-skills-with-to-goal: Skills are organized into bucket folders under skills/.
coral CLAUDE.md
Instructions for cdknorow/coral, covering claude.md - coral go, mission, testing, go unit tests and legacy parity tools (historical reference).
pixir CLAUDE.md
Instructions for Ranvier-Technologies/pixir, covering pixir harness - legacy agent guide, current map and commands.
Agent-Memory-Bridge AGENTS.md
Instructions for zzhang82/Agent-Memory-Bridge, covering agent memory bridge contributor instructions, setup and checks, architecture boundaries, mutation and migration invariants and benchmark expectations.