adr

adr is a skill for Claude Code from ulises-jeremias/agent-toolkit. It costs 50 tokens per session (957 once invoked), scanned A, original, MIT.

A process for recording lasting technical architecture decisions in Architecture Decision Records, or ADRs. An ADR explains the decision, alternatives, trade-offs, and links to related project work.

In plain words
What is it for?
Use it for decisions with long-term effects on architecture, security, data models, costs, or links between technical plans and pull requests.
Why use it?
It preserves the reasoning behind important design choices so future contributors can understand or replace them.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions CLAUDE.md; mentions AGENTS.md.

Part of the agent-toolkit-complete plugin — 116 skills shipped together

Good fit Use it for decisions with long-term effects on architecture, security, data models, costs, or links between technical plans and pull requests.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ulises-jeremias/agent-toolkit/adr
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.

Any agent
npx skills add ulises-jeremias/agent-toolkit --skill adr
Clone the repo
git clone --depth 1 https://github.com/ulises-jeremias/agent-toolkit

Made for: Claude Code.

Or install agent-toolkit-complete, the plugin that ships this one along with the rest of its 116 skills.

Wrote 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.

agentmods badge for adr

README.md
[![agentmods](https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/adr.svg)](https://agentmods.dev/skills/ulises-jeremias/agent-toolkit/adr)
Your own site
<a href="https://agentmods.dev/skills/ulises-jeremias/agent-toolkit/adr"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/adr.svg" alt="Measured on agentmods" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 957 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00050 $0.00957
Opus 5 $0.00025 $0.00478
Sonnet 5 $0.00010 $0.00191
Haiku 4.5 $0.00005 $0.00096

Measured 3d ago against content hash d2f18d4e5850, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

adr 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 3d 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.

plugins/agent-toolkit-complete/.github/skills/adr/SKILL.md · 57 lines

How it starts

The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.

ADR — Architecture Decisions (WHAT)

Template: references/default-template.md — local reference for ADR structure and workflow.

Default guardrails (before any final content)

  1. Apply output-handshake: confirm where the final ADR will be recorded and that a human will review.
  2. Then follow the steps below.

When to use

Use decision-log for lightweight product/project/operational decisions and agreement for explicit commitments or terms among parties. Use this ADR skill only for durable architecture or technical decisions.

  • A change has long-term architectural, security, data-model, or cost impact.
  • You need options with pros/cons and a record for future readers (and for supersession later).
  • The project needs decisions linked to PRDs, TRDs, tasks, PRs, diagrams, or other supporting artifacts.

Instructions

  1. Match existing convention first (per addyosmani/agent-skills documentation-and-adrs 2026-08-12, diff docs/research/diff-394-documentation-and-adrs.md): inspect docs/adrs/ (or Documentation/Decisions/, MADR, adr-tools .adr-dir) — location/format (Markdown vs reStructuredText), numbering/naming (ADR-004-*.md vs 0004-*.md), section headings. Surface conflict rather than silently introducing another scheme. Only when no convention can be established, default to docs/adrs/000N-*.md or docs/adrs/ADR-0xx-*.md six-part structure.

  2. Confirm the decision qualifies (new service, tech selection, schema change, deployment change, etc.) per the "When to Create an ADR" criteria.

  3. Draft using the six-part structure: Title & status, Context, Options, Decision, Consequences, References (link PRD/TRD, tasks, PRs, diagrams as applicable). Use lifecycle PROPOSED → ACCEPTED → (SUPERSEDED | DEPRECATED) and don't delete old ADRs — when decision changes, write new ADR that references and supersedes old (per upstream 2026-08-12).

  4. Review with the tech lead / peers as in the workflow; keep ADRs short and actionable (clarity over completeness).

  5. Link the ADR to the relevant epic or story and to PRs in the forge (use github-cli-workflow / gitlab-cli-workflow for PR text when applicable).

  6. If an ADR is superseded, preserve history: update status and point to the replacement document.

Read the full file on GitHub · 57 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 3d ago Changed d2f18d4e5850
  2. 7d ago First seen · 57 lines · 50 tokens per session scan A 84613c43c11f

Subscribe to this mod's changes

adr is a skill published in the GitHub repository ulises-jeremias/agent-toolkit (16 stars, last pushed yesterday), licensed MIT. It adds 50 tokens to every session and 957 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

verify

Fact-check claims encountered during reading — dates, names, events, citations. Use when encountering historical facts or disputed claims.

yha9806/academic-writing-toolkit · 26 tokens

iblai-api-catalog-media

Manage an ibl.ai organization's catalog media resources via the Data Manager API — videos, images, documents, audio, and external links attached to a course, unit, or resource (item). Per-org, per-user CRUD plus search and by-item lookup, with multipart file upload. Use when attaching media to course/unit/resource…

iblai/api · 88 tokens

iblai-api-agent-skill

Manage an ibl.ai agent's skills via the platform API — browse the org skill catalog, assign/unassign skills to an agent, and create/edit/delete catalog skills. Requires a connected sandbox. Use when giving an agent reusable skill instructions.

iblai/api · 55 tokens

iblai-api-agent-disclaimer

Manage an ibl.ai agent's disclaimers via the platform API — the Advisory text (saved through the agent settings endpoint) and the User Agreement (create/update/activate). Use when adding legal or advisory notices users must see or accept.

iblai/api · 55 tokens

iblai-api-agent-safety

Configure an ibl.ai agent's moderation and safety systems via the platform API — enable flags, system prompts and responses (saved through the agent settings endpoint) — and review or delete flagged-prompt moderation logs. Use when setting guardrails or auditing flagged content.

iblai/api · 59 tokens

pr-alignment-loop

Iterate a PR to its final form by running two opposing reviewer droids (reviewer-robustness and reviewer-minimalist) in a bounded back-and-forth loop. The main orchestrator synthesizes their feedback, makes edits, runs tests, and stops when both approve, on stagnation, or after 3 rounds. Use when the user asks to…

nikships/skills-registry · 122 tokens