architecture-decisions

A set of records that explain important architecture choices in a software project. The agent must read accepted decisions, refer to them, and flag conflicts; people approve or replace them.

In plain words
What is it for?
Use it when changing system structure, choosing technical approaches, or maintaining Architecture Decision Records (ADRs), which are short documents recording why a design choice was made.
Why use it?
It prevents the agent from quietly making changes that contradict decisions the team has already accepted. It also keeps exceptions visible for human review.

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/nerds-odd-e/doughnut/architecture-decisions
Clone the repo
git clone --depth 1 https://github.com/nerds-odd-e/doughnut

Made for: Cursor.

Per session 164 This file is loaded in full into every session.
When invoked 164 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original 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.00164 $0.00164
Opus 5 $0.00082 $0.00082
Sonnet 5 $0.00033 $0.00033
Haiku 4.5 $0.00016 $0.00016

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

Security

Grade A, and why

architecture-decisions 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/architecture-decisions.mdc · 13 lines

What it actually says

Architecture Decisions (ADRs)

  • Human playbook (propose / discuss / approve): docs/adrs/README.md
  • Accepted ADRs (current recommendations): docs/adrs/*-accepted.md — read explicitly; docs/ is outside default indexing
  • Agent skill (use / cite / conflict / maintain): adr-awareness in .agents/skills/adr-awareness/
  • On architecture-shaped work, load relevant Accepted ADRs and follow them. Do not silently conflict. Do not approve ADRs; humans own the advice process.
  • Deviations require an explicit human-owned exception (trail it) or a human superseding ADR.
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 · 13 lines · 164 tokens per session scan A 997fdc333b03

Subscribe to this mod's changes

architecture-decisions is a cursor rule published in the GitHub repository nerds-odd-e/doughnut (49 stars, last pushed 2d ago), licensed MIT. It adds 164 tokens to every session, about $0.0008 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.