A set of instructions for finding the engineering terms and design decisions documented in a code repository. It points developers to context documents and architecture decision records, which explain parts of the system and why they were built that way.

Use it before exploring or changing code to locate the right domain documents, system decisions, and context-specific guidance.

Developers can misunderstand a codebase when its domain knowledge is scattered across folders. This gives engineering skills a consistent starting point for learning the relevant context.

domain — Agent by LeXwDeX

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/lexwdex/opencode-graphagent/domain

Clone the repo

git clone --depth 1 https://github.com/LeXwDeX/OpenCode-GraphAgent

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 371 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found 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.00371
Opus 5	$0.00000	$0.00186
Sonnet 5	$0.00000	$0.00074
Haiku 4.5	$0.00000	$0.00037

Measured yesterday against content hash f824ef2629df, 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.

docs/agents/domain.md · 38 lines

What it actually says

Domain Docs

How engineering skills consume this repository's domain documentation while exploring the codebase.

Selected layout

This repository uses a multi-context layout. CONTEXT-MAP.md is the entry point and points to the domain documents relevant to each bounded context.

Before exploring

Read CONTEXT-MAP.md at the repository root.
Read each linked CONTEXT.md relevant to the work.
Read system-wide ADRs under docs/adr/ and context-scoped ADRs linked by the map.

If a referenced directory or document does not exist, proceed silently. Do not create speculative terminology or ADRs merely to fill the layout. /domain-modeling, reached through /grill-with-docs or /improve-codebase-architecture, creates them when terms or decisions are actually resolved.

File structure

/
├── CONTEXT-MAP.md                    # context index
├── CONTEXT.md                        # existing Session Runtime context
├── docs/adr/                         # system-wide decisions, created lazily
└── packages/<context>/
    ├── CONTEXT.md                    # context vocabulary, created lazily
    └── docs/adr/                     # context decisions, created lazily

Use the glossary vocabulary

When an issue title, refactor proposal, hypothesis, or test names a domain concept, use the term defined in the relevant CONTEXT.md. Do not replace a defined term with a synonym that the glossary explicitly avoids.

If the required concept is absent, reconsider whether the project already uses another term. If the gap is real, record it for /domain-modeling.

Flag ADR conflicts

If proposed work contradicts an existing ADR, state the conflict explicitly rather than silently overriding it.

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 f824ef2629df

Subscribe to this mod's changes

domain is an agent published in the GitHub repository LeXwDeX/OpenCode-GraphAgent (111 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 371 tokens. 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.

Planning Writing and docs dag graph-agent opencode

model-compatibility

Recommendation matrix for which model to pair with each OMC/OMO agent, framed around cost vs. quality. This page exists so the recurring "어떤 모델을 어느 agent에 박아야 함?" question stops being tribal Discord knowledge.

Yeachan-Heo/oh-my-claudecode · 0 tokens

codemap

Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…

alvinunreal/oh-my-opencode-slim · 0 tokens

domain