domain

A guide for exploring a code repository's domain documentation: its glossary file and records explaining past architecture decisions. A repository's domain documentation describes the project's terminology and important design choices.

In plain words
What is it for?
Use it when exploring a repository, naming domain concepts in issues or tests, or working in an area covered by an architecture decision record.
Why use it?
It helps an agent understand the project's language and decisions before changing code. This reduces confusion caused by inventing different terms or overlooking earlier choices.

Agent

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/velkyvenik/missingmcp/domain
Clone the repo
git clone --depth 1 https://github.com/VelkyVenik/missingmcp
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 83% 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.

ModelPer sessionOnce 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 2d ago against content hash e847bc6e74e7, 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 2d 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.

Origin

This is a copy

83% identical to domain — 29 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 · 37 lines

What it actually says

Domain Docs

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

This repo is single-context: one CONTEXT.md + docs/adr/ at the repo root.

Before exploring, read these

  • CONTEXT.md at the repo root — the domain glossary.
  • 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 /domain-modeling skill (reached via /grill-with-docs and /improve-codebase-architecture) creates them lazily when terms or decisions actually get resolved.

File structure

Single-context repo (this repo):

/
├── CONTEXT.md
├── docs/adr/
│   └── 0001-retired-adapter-cleanup.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 CONTEXT.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 /domain-modeling).

Flag ADR conflicts

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

Contradicts ADR-0001 (retired-adapter cleanup) — 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.

  1. 2d ago First seen · 37 lines · 0 tokens per session scan A e847bc6e74e7

Subscribe to this mod's changes

domain is an agent published in the GitHub repository VelkyVenik/missingmcp (4 stars, last pushed 11d 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 83% identical to domain, differing in 29 lines, and is treated as a copy.