An engineering guide for using a repository’s domain documentation, which explains the project’s concepts and design decisions, during code exploration.

It helps engineers read relevant context and architecture records before exploring code and use the project’s defined terminology.

It reduces confusion caused by overlooking project context or using different names for the same concept.

domain — Agent by agentrhq

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 agents/agentrhq/authsome/domain

Clone the repo

git clone --depth 1 https://github.com/agentrhq/authsome

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 347 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin 75% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00347
Opus 5	$0.00000	$0.00173
Sonnet 5	$0.00000	$0.00069
Haiku 4.5	$0.00000	$0.00035

Measured yesterday against content hash a678572800f4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

domain 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.

Origin

This is a copy

75% identical to domain — 34 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

docs/agents/domain.md · 38 lines

What it actually says

Domain Docs

How engineering skills should consume this repo's domain documentation when exploring the codebase.

Before exploring, read these

CONTEXT.md at the repo root
docs/adr/ — read ADRs that touch the area you're about to work in

If any of these files don't exist, proceed silently. Don't flag their absence; don't suggest creating them upfront. The producer skill (/grill-with-docs) creates them lazily when terms or decisions actually get resolved.

File structure

Single-context repo:

/
├── CONTEXT.md
├── docs/adr/
│   ├── 0001-provider-client-record-server-scope.md
│   ├── 0002-server-registered-identities.md
│   ├── 0003-proxy-unmatched-pass-through.md
│   └── 0004-principal-owned-vault.md
└── src/

Use the glossary's vocabulary

When your output names a domain concept (in an issue title, a refactor proposal, a hypothesis, a test name), use the term as defined in docs/UBIQUITOUS_LANGUAGE.md. Don't drift to synonyms the glossary explicitly avoids.

If the concept you need isn't in the glossary yet, that's a signal — either you're inventing language the project doesn't use (reconsider) or there's a real gap (note it for /grill-with-docs).

Flag ADR conflicts

If your output contradicts an existing ADR, surface it explicitly rather than silently overriding:

Contradicts ADR-0003 (example) — but worth reopening because…

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.

yesterday First seen · 38 lines · 0 tokens per session scan A a678572800f4

Subscribe to this mod's changes

domain is an agent published in the GitHub repository agentrhq/authsome (84 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 347 tokens. A static security scan graded it A with 0 findings. It is 75% identical to domain, differing in 34 lines, and is treated as a copy.

Planning Writing and docs ai-agents authentication cli headless local-first mcp

sverklo-explore

Drop-in replacement for Claude Code's built-in Explore subagent. Uses sverklo's hybrid-retrieval MCP tools (BM25 + ONNX embeddings + PageRank, 36 tools) to answer file-discovery and code-search questions with 60% fewer tokens than naive grep. Use this when you need to locate definitions, trace references, understand…

sverklo/sverklo · 96 tokens

orbit-code-editor

Scoped read-write helper for an Orbit orchestrator. Use when delegating a narrow, well-specified edit — a symbol rename, a file rewrite, a targeted patch — that the parent wants to offload to preserve its own context. Returns a diff summary; the parent decides whether to commit.

danieljhkim/orbit · 63 tokens

ipc-contract-auditor

Use when IPC or command-surface drift is possible — after adding, renaming, or removing a Tauri command, a SidecarCommand/SidecarEvent variant, or a tauri-api.ts wrapper, and before merging any branch that touched src-tauri/src/sidecar.rs, src-tauri/sidecar-opencode/src/types.ts, src-tauri/src/lib.rs, or…

kevinlin/cowork-z · 105 tokens

domain