Borrowing it
Nothing to install: this file belongs to rjmurillo/ai-agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rjmurillo/ai-agents/main/.github/instructions/adr-records.instructions.mdgit clone --depth 1 https://github.com/rjmurillo/ai-agentsWrote 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/rjmurillo/ai-agents/adr-records)<a href="https://agentmods.dev/instructions/rjmurillo/ai-agents/adr-records"><img src="https://agentmods.dev/badge/instructions/rjmurillo/ai-agents/adr-records/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/rjmurillo/ai-agents/adr-records"><img src="https://agentmods.dev/badge/instructions/rjmurillo/ai-agents/adr-records.svg" alt="Reviewed on agentmods" width="80" 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.00505 | $0.00505 |
| Opus 5.5 | $0.00202 | $0.00202 |
| Sonnet 5.5 | $0.00101 | $0.00101 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
ai-agents adr-records.instructions.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 28d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ADR Record Rules
Conventions for authoring a record under .project-toolkit/architecture/. The generated
index reads these files mechanically, so a record can be correct prose and still
render wrong in the index.
MUST
-
The first sentence of
## StatusMUST stand alone. The generated ADR index strips a leading bare status token from that paragraph before rendering it as the Proposed table's blocker cell. The stripper isbuild/scripts/generate_adr_index.py:161:_LEADING_PROPOSED_RE = re.compile(r"^Proposed\b[ \t]*[.:-]?[ \t]*", re.IGNORECASE)applied by
_blocking_conditionatbuild/scripts/generate_adr_index.py:503-514to the first paragraph of the## Statussection. It consumes the word plus at most one trailing.,:or-. It does not consume a comma, so a record openingProposed, and concluded without consensus.renders in the index as, and concluded without consensus.Write a status paragraph whose first sentence carries its own subject:
Proposed. The panel concluded without consensus.renders asThe panel concluded without consensus.The strip is deliberate and tested, not a defect to fix in the generator:
tests/build_scripts/test_generate_adr_index.py:195istest_proposed_blocker_drops_the_redundant_status_token, which asserts"Proposed." not in proposed_row. The section heading already carries the status, so repeating it in the cell is noise. The obligation is on the author.Evidence: this fired twice in one session while settling ADR-101 (PR #5677). ADR-072's debate log had already recorded the same trap, which is why the convention belongs in a rule the loader reads by
paths:rather than in a critique artifact nobody opens while drafting.
References
build/scripts/generate_adr_index.py. Renders the index; owns the strip.tests/build_scripts/test_generate_adr_index.py. Pins the strip's behavior..project-toolkit/architecture/README.md. The generated index itself.
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.
- 28d ago Changed · +6 tokens per session fabf5d3df099
- 1mo ago First seen · 49 lines · 499 tokens per session scan A f9ccebe8c5e3
ai-agents adr-records.instructions.md is an instructions file published in the GitHub repository rjmurillo/ai-agents (48 stars, last pushed today), licensed MIT. It adds 505 tokens to every session, about $0.0020 per session on Opus 5.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-09-12.
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.