documentation-precedence

A project rule that explains how architecture decision records, or ADRs, take priority over a default rule of not adding documentation.

In plain words
What is it for?
Use it when deciding whether an architectural decision requires documentation despite the project’s normal no-documentation default.
Why use it?
It resolves conflicts about whether documentation should be created when an ADR requires it.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/open-locker/open-locker/documentation-precedence
Clone the repo
git clone --depth 1 https://github.com/Open-Locker/Open-Locker

Made for: Cursor.

Per session 98 This file is loaded in full into every session.
When invoked 98 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00098 $0.00098
Opus 5 $0.00049 $0.00049
Sonnet 5 $0.00020 $0.00020
Haiku 4.5 $0.00010 $0.00010

Measured 2d ago against content hash dcefa68c17be, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

documentation-precedence 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.

.cursor/rules/general/documentation-precedence.mdc · 16 lines

The source is not reproduced here

Licensed GPL-3.0

The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

Changes

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.

  1. 2d ago First seen · 16 lines · 98 tokens per session scan A dcefa68c17be

Subscribe to this mod's changes

documentation-precedence is a cursor rule published in the GitHub repository Open-Locker/Open-Locker (24 stars, last pushed 6d ago), licensed GPL-3.0. It adds 98 tokens to every session, about $0.0005 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.