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 agentmods add skills/joelhooks/joelclaw/adr-skillnpx skills add joelhooks/joelclaw --skill adr-skillgit clone --depth 1 https://github.com/joelhooks/joelclawWrote 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/joelhooks/joelclaw/adr-skill)<a href="https://agentmods.dev/skills/joelhooks/joelclaw/adr-skill"><img src="https://agentmods.dev/badge/skills/joelhooks/joelclaw/adr-skill.svg" alt="Measured on agentmods" 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.00089 | $0.05221 |
| Opus 5 | $0.00044 | $0.02610 |
| Sonnet 5 | $0.00018 | $0.01044 |
| Haiku 4.5 | $0.00009 | $0.00522 |
Grade A, and why
adr-skill 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 6d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
13 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.
- agents/openai.yaml 91 B
- assets/large-logo.png 5.1 KB
- assets/small-logo.svg 375 B
- assets/templates/adr-madr.md 3.6 KB
- assets/templates/adr-readme.md 672 B
- assets/templates/adr-simple.md 1.7 KB
- references/adr-conventions.md 3.4 KB
- references/examples.md 9.9 KB
- references/review-checklist.md 4.6 KB
- references/template-variants.md 2.5 KB
- scripts/bootstrap_adr.js 9.7 KB runs code
- scripts/new_adr.js 13 KB runs code
- scripts/set_adr_status.js 4.2 KB runs code
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.
- 6d ago First seen · 438 lines · 89 tokens per session scan A 26151fb54c69
adr-skill is a skill published in the GitHub repository joelhooks/joelclaw (63 stars, last pushed yesterday), with no licence file. It adds 89 tokens to every session and 5,221 once invoked, about $0.0004 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.
Other skills, from other repositories
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"…
mpm-adr
Architecture Decision Records (ADRs) — opt-in convention for documenting significant, hard-to-reverse architectural decisions using the Nygard template.
adr-manager
Record and retrieve Architecture Decision Records — log a decision's context, options, rationale, and tradeoffs, then list/search them. Use when making a non-trivial design or architecture decision, choosing between tools/approaches, or asked 'why did we do it this way?'.
adr-writing
Write Architecture Decision Records future engineers will actually read. Invoke when making a non-trivial architectural choice that you want to defend later.
architecture-decision-record-creator
Create structured Architecture Decision Records (ADRs) with 7 sections to document architecture decisions with full justification. Use this skill whenever the user has made or needs to make an architecture decision, wants to document why a technical choice was made, is choosing between technologies or patterns, needs…
architecture-decision-records
Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.