write-adr

write-adr is a skill for Claude Code, Codex from soulcodex/agentic. It costs 55 tokens per session (435 once invoked), scanned A, original, MIT.

An Architecture Decision Record (ADR) is a short document that explains an important technical choice, why it was made, and its results. This skill creates one using a standard structure and numbered file.

In plain words
What is it for?
Use it to record a chosen approach, the alternatives considered, its trade-offs, and the consequences for the project.
Why use it?
It preserves the reasoning behind decisions so future developers can understand the context without repeating the same discussion.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Codex; mentions OpenCode.

Good fit Use it to record a chosen approach, the alternatives considered, its trade-offs, and the consequences for the project.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/soulcodex/agentic/write-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 soulcodex/agentic --skill write-adr
Clone the repo
git clone --depth 1 https://github.com/soulcodex/agentic

Made for: Claude Code, Codex.

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 write-adr

README.md
[![agentmods](https://agentmods.dev/badge/skills/soulcodex/agentic/write-adr/github.svg)](https://agentmods.dev/skills/soulcodex/agentic/write-adr)
Your own site
<a href="https://agentmods.dev/skills/soulcodex/agentic/write-adr"><img src="https://agentmods.dev/badge/skills/soulcodex/agentic/write-adr/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.

agentmods 80×15 button for write-adr

Your own site · 80×15
<a href="https://agentmods.dev/skills/soulcodex/agentic/write-adr"><img src="https://agentmods.dev/badge/skills/soulcodex/agentic/write-adr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 435 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.00055 $0.00435
Opus 5.5 $0.00022 $0.00174
Sonnet 5.5 $0.00011 $0.00087
Haiku 4.5 $0.00006 $0.00044

Measured 2mo ago against content hash fe5f5b350855, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

write-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 2mo 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.

skills/documentation/write-adr/SKILL.md · 57 lines

What it actually says

Write ADR Skill

Create a well-structured Architecture Decision Record.

Step 1 — Gather Information

Ask the user (if not already provided):

  1. What decision was made?
  2. What was the context or problem that prompted it?
  3. What alternatives were considered?
  4. What are the trade-offs or consequences of this decision?

Step 2 — Determine the ADR Number

List existing ADRs in docs/adr/ and increment the highest number. If the directory does not exist, create it and start at 0001.

Step 3 — Write the ADR

Use the template from adr-template.md. Fill every section:

  • Title: short, imperative phrase describing the decision
  • Status: Accepted for a new decision
  • Date: today's date in YYYY-MM-DD format
  • Context: the situation that made a decision necessary — be specific about constraints
  • Decision: what was decided — use active voice ("We will use X")
  • Consequences: both positive and negative outcomes; what becomes easier and harder

The ADR must stand alone — a reader unfamiliar with the decision must understand it fully from the ADR text without needing to ask follow-up questions.

Step 4 — Write the File

Save to docs/adr/NNNN-{kebab-case-title}.md.

Example: docs/adr/0003-use-postgresql-as-primary-store.md

Files

What ships with it

1 file 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. 2mo ago First seen · 57 lines · 55 tokens per session scan A fe5f5b350855

Subscribe to this mod's changes

write-adr is a skill published in the GitHub repository soulcodex/agentic (10 stars, last pushed 3d ago), licensed MIT. It adds 55 tokens to every session and 435 once invoked, about $0.0002 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-08-31.

Related

Other skills, from other repositories

help

Use when asked what the capstone plugin can do - prints the usage block.

GentBajko/capstone · 18 tokens

adr-documentation

Architecture Decision Records (ADR) documentation practice. Use when documenting architectural decisions, recording technical trade-offs, creating decision logs, or establishing architectural patterns. Trigger keywords - "ADR", "architecture decision", "decision record", "trade-offs", "architectural decision"…

MadAppGang/claude-code · 60 tokens

review

Use when asked for an opinionated review of the codebase - architecture/backend findings, UI findings against the project's own design docs, or both - severity-ranked with evidence, written to docs/capstone/review.md. Bare "review" does both sides; "review backend" or "review frontend" does one. "review retro…

GentBajko/capstone · 113 tokens

start

Use when the user says just "capstone" with nothing else, or asks to start or continue the capstone pipeline - runs the greenfield chain one stage at a time, detecting completed stages and resuming at the first incomplete one. A stage word as the argument (mockup, logic, uiux, architecture, standards, stack, build)…

GentBajko/capstone · 116 tokens

core

Internal to the capstone suite - carries the shared rules (references/) and scripts every capstone subcommand reads; it exists so npx-skills installs ship them alongside the command skills. Not meant to be invoked directly; when invoked anyway, run references/../scripts/help.sh and output its stdout verbatim.

GentBajko/capstone · 65 tokens

feature

Use when the user wants one feature taken from idea to working code - "add a feature", "build X end to end", "take X from idea to shipped" - runs the feature chain groom → plan → implement consecutively, detecting the feature's stage and resuming at the first incomplete one. For the whole-product greenfield pipeline…

GentBajko/capstone · 95 tokens