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 JansenAnalytics/claudex --skill adr-managergit clone --depth 1 https://github.com/JansenAnalytics/claudexWrote 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/jansenanalytics/claudex/adr-manager)<a href="https://agentmods.dev/skills/jansenanalytics/claudex/adr-manager"><img src="https://agentmods.dev/badge/skills/jansenanalytics/claudex/adr-manager/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/jansenanalytics/claudex/adr-manager"><img src="https://agentmods.dev/badge/skills/jansenanalytics/claudex/adr-manager.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.00059 | $0.00504 |
| Opus 5.5 | $0.00024 | $0.00202 |
| Sonnet 5.5 | $0.00012 | $0.00101 |
| Haiku 4.5 | $0.00006 | $0.00050 |
Grade A, and why
adr-manager 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 1mo 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.
What it actually says
ADR Manager Skill
Use when: making a non-trivial technical decision — choosing between options, committing to an architecture, or accepting a tradeoff. Record it so future sessions don't have to guess.
Trigger: any time you make a design decision, choose between tools/approaches, or the user asks "why did we do it this way?"
Create an ADR
node ${ADR_MANAGER_HOME:-$HOME/projects/adr-manager}/adr.cjs new \
--project <project-name> \
--title "Decision title" \
--context "Why this decision was needed" \
--options "option1,option2,option3" \
--decision "chosen-option" \
--rationale "Why this option was chosen" \
--tradeoffs "What we gave up and why it's acceptable"
List ADRs for a project
node ${ADR_MANAGER_HOME:-$HOME/projects/adr-manager}/adr.cjs list --project <name>
List all ADRs across all projects
node ${ADR_MANAGER_HOME:-$HOME/projects/adr-manager}/adr.cjs list
View an ADR
node ${ADR_MANAGER_HOME:-$HOME/projects/adr-manager}/adr.cjs view ADR-001 --project <name>
Search
node ${ADR_MANAGER_HOME:-$HOME/projects/adr-manager}/adr.cjs search "query"
Update status
node ${ADR_MANAGER_HOME:-$HOME/projects/adr-manager}/adr.cjs status ADR-001 Superseded --project <name>
ADR files location
~/projects/<project>/.adr/ADR-NNN-<slug>.md
When to create an ADR
- Choosing a database, language, or framework
- Deciding between build vs. buy
- Accepting a known tradeoff (e.g. no concurrency for simplicity)
- Any decision the user or future-Kite might question later
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.
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.
- 1mo ago First seen · 68 lines · 59 tokens per session scan A e81e35314ce5
adr-manager is a skill published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 4mo ago), licensed MIT. It adds 59 tokens to every session and 504 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.
Other skills, from other repositories
decision-records
Use when a hard-to-reverse choice (database, framework, vendor, auth model) must be frozen as an immutable numbered ADR — the context that forced it, the options weighed, the decision, consequences both ways — or superseded without erasing history. NOT a meeting recap (that is meeting-notes), NOT standing project…
adr-skill
Create and maintain Architecture Decision Records (ADRs) optimized for agentic coding workflows. Use when you need to propose, write, update, accept/reject, deprecate, or supersede an ADR; bootstrap an adr folder and index; consult existing ADRs before implementing changes; or enforce ADR conventions. This skill uses…
architecture-decision-record-maintainer-skill
Use when working ON the joelparkerhenderson/architecture-decision-record repository itself (this repo) — adding or editing a decision-record template, example, tool/guardrail link, or translation; reviewing a contributor's PR against it; or keeping README.md and locales/en-001/ in sync. Not for writing an ADR for some…
architecture-decision-record-skill
Use when a user wants to create, write, name, place, or organize an Architecture Decision Record (ADR) in a software project — e.g. "write an ADR for choosing a database", "document this architecture decision", "set up an adr/ or decisions/ directory", "which ADR template should I use", "supersede an old ADR". Covers…
atlas-adr
Write an Architecture Decision Record — document what was decided, why, what alternatives were considered, and what trade-offs were accepted. Use when asked to "write an ADR", "document this decision", or "why did we choose X".
bootstrap
Scaffold or retrofit documentation-led conventions (AGENTS.md, CLAUDE.md, CONVENTIONS.md, ADR catalogue, plan/ queue, agent/ coordination) into a repo. Use when the user asks to "set up conventions", "bootstrap ADRs", "scaffold the documentation-led layout", or "add AGENTS.md and a plan queue". Works on fresh repos…