Borrowing it
Nothing to install: this file belongs to nerds-odd-e/doughnut. 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/nerds-odd-e/doughnut/main/.agents/skills/dough-adr-awareness/SKILL.mdgit clone --depth 1 https://github.com/nerds-odd-e/doughnutWrote 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/skills/nerds-odd-e/doughnut/dough-adr-awareness)<a href="https://agentmods.dev/skills/nerds-odd-e/doughnut/dough-adr-awareness"><img src="https://agentmods.dev/badge/skills/nerds-odd-e/doughnut/dough-adr-awareness/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/skills/nerds-odd-e/doughnut/dough-adr-awareness"><img src="https://agentmods.dev/badge/skills/nerds-odd-e/doughnut/dough-adr-awareness.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.00067 | $0.01449 |
| Opus 5.5 | $0.00027 | $0.00580 |
| Sonnet 5.5 | $0.00013 | $0.00290 |
| Haiku 4.5 | $0.00007 | $0.00145 |
Grade A, and why
dough-adr-awareness 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 1mo 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ADR awareness
Keep architecture-shaped work consistent with this project's current Accepted ADRs without taking decision authority from humans.
Required project context
Resolve the following context from the repository's own guidance as needed for the current request; ask the human only for a missing value that affects it:
- the repository-relative ADR store and index or catalog path;
- the fields that authoritatively classify an ADR as Proposed, Accepted, Rejected, or Superseded, and the human-owned rule for resolving disagreement between those fields;
- the filename conventions and supersession-link convention;
- the project's definition of architecture-shaped work and the areas governed by each ADR;
- the durable place to record an explicitly approved exception;
- the human advice, announcement, approval, rejection, and supersession process; and
- the precedence between ADR guidance and any planning or delivery workflow.
The proposal template is required only when the human asks for proposal-drafting help. Do not assume a template, ADR path, status syntax, or exception trail from another project.
If context needed for the current request cannot be resolved, name the missing context and stop the affected work. Do not claim that an ADR check completed.
Do not require policies for situations absent from the current request. When the index and record statuses agree, no disagreement-resolution rule is needed. When no relevant record indicates supersession and no lifecycle change is requested, a supersession-maintenance convention is not needed. Do not invent either policy. An actual status disagreement or unclear successor still blocks dependent work as described below.
When to apply
Apply this skill when the human explicitly asks to check, cite, contradict, supersede, or otherwise work with ADRs. Also apply it to architecture-shaped work according to this project's definition, typically cross-cutting choices about technology stacks, persistence, API contracts, authentication, packaging, repository layout, or shared conventions.
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.
- 1mo ago Changed · +1 tokens per session 169a108c845c
- 1mo ago First seen · 157 lines · 66 tokens per session scan A 6c0f29ceec25
dough-adr-awareness is a skill published in the GitHub repository nerds-odd-e/doughnut (50 stars, last pushed today), licensed MIT. It adds 67 tokens to every session and 1,449 once invoked, about $0.0003 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-08.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.