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.
npx skills add Kaddo-kdd/kaddo --skill adr-writinggit clone --depth 1 https://github.com/Kaddo-kdd/kaddoWrote 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/kaddo-kdd/kaddo/adr-writing)<a href="https://agentmods.dev/skills/kaddo-kdd/kaddo/adr-writing"><img src="https://agentmods.dev/badge/skills/kaddo-kdd/kaddo/adr-writing/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/kaddo-kdd/kaddo/adr-writing"><img src="https://agentmods.dev/badge/skills/kaddo-kdd/kaddo/adr-writing.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.00044 | $0.00533 |
| Opus 5.5 | $0.00018 | $0.00213 |
| Sonnet 5 | $0.00009 | $0.00107 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
adr-writing 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 yesterday.
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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ADR Writing Skill
Purpose
Standardize how Architecture Decision Records are written so every decision is captured the same way and stays auditable.
When to use
When a real, consequential technical decision is being made or recognized — and only then.
Inputs
The context pack, the relevant Work Item or architecture note, and the decision being made.
Output
A single ADR (saved under knowledge/tech/decisions/) with front matter and the standard sections:
context, options considered, the decision, consequences, related capabilities and related Work Items.
Status is one of draft, accepted, superseded, deprecated.
Materializing from decision candidates (VS-075)
When knowledge/tech/decisions/ is empty but knowledge/tech/decision-candidates.md holds
candidates, materialize each candidate as an ADR draft — copy its context and options, leave the
decision and consequences as [open] for human confirmation, and record its origin with
created_from: knowledge/tech/decision-candidates.md. Never mark a materialized draft accepted;
acceptance is a human decision.
Rules
- One ADR = one decision. Never mix unrelated decisions.
- Never invent decisions; never write an ADR without a clear reason.
- Record alternatives honestly, including the one chosen and why (or
[open]when undecided). - Prefer narrow governed
code:globs over broad ones.
Quality checklist
- Context explains why the decision was needed.
- The decision and its alternatives are explicit (or explicitly
[open]). - Consequences (positive and negative) are stated.
- Status and governed paths are present.
Example output
---
type: adr
status: draft | accepted | superseded | deprecated
date: YYYY-MM-DD
created_from: knowledge/tech/decision-candidates.md
---
# ADR-001 — Use INTERNAL_CRON_SECRET for internal endpoint protection
## Context
...
## Options Considered
...
## Decision
[open]
## Consequences
[open]
## Related Capabilities
- <domain / capability>
## Related Work Items
- <WI id>
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.
- yesterday First seen · 76 lines · 44 tokens per session scan A 4230ea7115e6
adr-writing is a skill published in the GitHub repository Kaddo-kdd/kaddo (54 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 533 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-09-25.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…