agentmods.dev

write-adr

write-adr is a skill for Claude Code, Codex from 686f6c61/alfred-dev. It costs 37 tokens per session (447 once invoked), scanned A, original, MIT.

A helper for writing Architecture Decision Records, or ADRs. An ADR is a short document that records an important technical choice, the options considered, and its consequences.

In plain words
What is it for?
Use it to document choices about technology stacks, data storage, authentication, system boundaries, or integrations in a repository's `docs/adr/` folder.
Why use it?
It makes significant architecture choices traceable instead of leaving the reasoning scattered across conversations or code. It also distinguishes proposed decisions from accepted ones.

Skill for Claude CodeCodex

Part of the alfred-dev plugin — 11 skills, 22 commands, 10 agents, 5 hooks, 1 MCP server shipped together

not rated 119 19d ago A scan 37 tokens original MIT
View the source file 686f6c61/alfred-dev
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 skills/686f6c61/alfred-dev/write-adr
Any agent
npx skills add 686f6c61/alfred-dev --skill write-adr
Clone the repo
git clone --depth 1 https://github.com/686f6c61/alfred-dev

Made for: Claude Code, Codex.

Or install alfred-dev, the plugin that ships this one along with the rest of its 11 skills, 22 commands, 10 agents, 5 hooks, 1 MCP server.

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/686f6c61/alfred-dev/write-adr.svg)](https://agentmods.dev/skills/686f6c61/alfred-dev/write-adr)
Your own site
<a href="https://agentmods.dev/skills/686f6c61/alfred-dev/write-adr"><img src="https://agentmods.dev/badge/skills/686f6c61/alfred-dev/write-adr.svg" alt="Measured on agentmods" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 447 The whole file, excluding the scripts and references it only reads on demand.
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.00037 $0.00447
Opus 5 $0.00018 $0.00224
Sonnet 5 $0.00007 $0.00089
Haiku 4.5 $0.00004 $0.00045

Measured 3d ago against content hash 602f37af9365, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

skills/write-adr/SKILL.md · 54 lines

What it actually says

Escribir un ADR

Resumen

Documenta una decisión arquitectónica significativa en docs/adr/. Un ADR no es un diario: solo se escribe si hay una elección real (stack, persistencia, auth, límites, integración).

Proceso

  1. Crea el esqueleto con el helper. No inventes el número a mano:

    python3 .claude/alfred-continuity.py next-adr "$PWD" --title "Título corto"

  2. Lee templates/adr.md si existe y el fichero recién creado.

  3. Rellena, con hechos del repo:

    • contexto y restricciones
    • al menos dos opciones reales, con pros y contras
    • decisión y por qué
    • consecuencias y deuda asumida

  4. Estado inicial: propuesto hasta que el usuario o la gate de arquitectura lo acepten. Entonces aceptado. Si más tarde cambia, crea un ADR nuevo que apunte al anterior; no reescribas el viejo.

  5. Sustituye <!-- alfred-doc:scaffold --> por <!-- alfred-doc:filled -->.

  6. Ejecuta sync-project-docs para refrescar el índice.

  7. Si la decisión es de diseño, regístrala también con memory_log_decision. La memoria no sustituye al ADR.

Criterios de éxito

  • El fichero está en docs/adr/ADR-NNN-....md.
  • Hay al menos dos opciones evaluadas.
  • La decisión y sus consecuencias se pueden leer sin el chat.
  • El marcador es filled.

Qué NO hacer

  • No abras un ADR por un rename o un ajuste local de quick.
  • No dejes _(pendiente)_ en un ADR que declaras cerrado.
  • No copies un ADR genérico que no menciona el repo.
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 First seen · 54 lines · 37 tokens per session scan A 602f37af9365

Subscribe to this mod's changes

write-adr is a skill published in the GitHub repository 686f6c61/alfred-dev (119 stars, last pushed 19d ago), licensed MIT. It adds 37 tokens to every session and 447 once invoked, about $0.0002 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.

PlanningWriting and docsai-agentsautomationclaude-codeclaude-code-pluginsdlc
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

writing-skills

Use when creating new skills, editing existing skills, or verifying skills work before deployment.

obra/superpowers · 20 tokens

finishing-a-development-branch

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.

obra/superpowers · 27 tokens

test-driven-development

Use when implementing any feature or bugfix, before writing implementation code.

obra/superpowers · 17 tokens

receiving-code-review

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.

obra/superpowers · 38 tokens

writing-plans

Use when you have a spec or requirements for a multi-step task, before touching code.

obra/superpowers · 21 tokens