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/aaronsb/claude-code-config/adrnpx skills add aaronsb/claude-code-config --skill adrgit clone --depth 1 https://github.com/aaronsb/claude-code-configWhat 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 | $0.00074 | $0.00690 |
| Opus 5 | $0.00037 | $0.00345 |
| Sonnet 5 | $0.00015 | $0.00138 |
| Haiku 4.5 | $0.00007 | $0.00069 |
Grade A, and why
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 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ADR Management
Operate ADRs through the docs/scripts/adr CLI tool. Never create ADR files manually.
Commands
# Discover
docs/scripts/adr domains # Show domain number series and ranges
docs/scripts/adr list --group # List all ADRs grouped by domain
docs/scripts/adr list --domain system # Filter to one domain
docs/scripts/adr list --status Accepted # Filter by status
docs/scripts/adr view <number> # View an ADR (accepts 14, 014, ADR-014)
# Create
docs/scripts/adr new <domain> "Title" # Create from template in correct subdirectory
# Maintain
docs/scripts/adr lint # Check all ADRs for issues
docs/scripts/adr lint --check # Exit 1 on errors (CI mode)
docs/scripts/adr index -y # Regenerate INDEX.md
# Config
docs/scripts/adr config # Show current adr.yaml configuration
Workflow
- Check domains first:
docs/scripts/adr domainsto see available domains and number ranges - Create:
docs/scripts/adr new <domain> "Decision Title"— assigns next number, uses YAML frontmatter template - Edit: Fill in Context, Decision, Consequences, Alternatives sections
- Lint:
docs/scripts/adr lintbefore committing - Index:
docs/scripts/adr index -yafter adding or changing ADRs
Configuration
Each project defines its domain structure in docs/architecture/adr.yaml:
- domains: Name, number range, description, folder for each domain
- statuses: Valid status values (Draft, Proposed, Accepted, Superseded, Deprecated)
- defaults: Default deciders and initial status for new ADRs
- legacy: Number range for pre-domain ADRs
Always run docs/scripts/adr domains to discover the project's actual configuration rather than assuming domains.
ADR Format
The tool generates ADRs with YAML frontmatter:
---
status: Draft
date: 2026-02-17
deciders:
- aaronsb
- claude
related: []
---
# ADR-NNN: Decision Title
## Context
## Decision
## Consequences
### Positive
### Negative
### Neutral
## Alternatives Considered
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 · 82 lines · 74 tokens per session scan A 5ca1146de653
adr is a skill published in the GitHub repository aaronsb/claude-code-config (18 stars, last pushed 4mo ago), licensed MIT. It adds 74 tokens to every session and 690 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
achieving-cmmc-level-2-compliance
Prepare a defense-contractor environment for CMMC Level 2 certification: scope CUI and FCI, implement the 110 NIST SP 800-171 Rev 2 security requirements across 14 families, compute the SPRS score with the DoD Assessment Methodology, manage a compliant POA&M, and ready the organization for a C3PAO assessment. Use when…
task-planning-arch
计算任务 gap 并产出下一步可执行子任务 List[TaskSpec];gap 已闭返回空数组。对齐 arch 场景(架构师名册/技术栈概览/双视角分析)确定式分解——按根目标交付物集合 + donechildren 查表(参照 task-planning storage 特例,非自由 LLM 分解)。.
task-search
在框架预查的候选 bot 集里决出执行者(who)与协作方式(how),返回 4 态 SearchResult(HITSINGLE/HITGROUP/HITMULTIBOTS/MISS)。对齐案例剧本确定式映射。.
escalation-governance
Assess whether to escalate models. Use when evaluating reasoning depth.
agt-policy-authoring
Create and validate a minimal AGT Copilot CLI policy tailored to the repository being inspected.
silicon-throne
硅基圣座总控核心，以神谕式统御把零散任务压成 末将-first 之文明工程.