domain-modeling

domain-modeling is a skill for Claude Code, Codex from znlgis/my-opencode-deepseek-config. It costs 70 tokens per session (581 once invoked), scanned A, original, MIT.

A project glossary and decision-recording practice that keeps important terms consistent with the code. It stores shared definitions in CONTEXT.md and records significant architecture choices as ADRs.

In plain words
What is it for?
Use it while clarifying domain terms, checking whether a glossary matches the implementation, and deciding when an architectural decision needs to be recorded.
Why use it?
It prevents teammates from using the same word for different concepts or documenting relationships that the code does not actually implement. It also avoids creating unnecessary decision records.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it while clarifying domain terms, checking whether a glossary matches the implementation, and deciding when an architectural decision needs to be recorded.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/znlgis/my-opencode-deepseek-config/domain-modeling
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.

Any agent
npx skills add znlgis/my-opencode-deepseek-config --skill domain-modeling
Clone the repo
git clone --depth 1 https://github.com/znlgis/my-opencode-deepseek-config

Made for: Claude Code, Codex.

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

agentmods badge for domain-modeling

README.md
[![agentmods](https://agentmods.dev/badge/skills/znlgis/my-opencode-deepseek-config/domain-modeling/github.svg)](https://agentmods.dev/skills/znlgis/my-opencode-deepseek-config/domain-modeling)
Your own site
<a href="https://agentmods.dev/skills/znlgis/my-opencode-deepseek-config/domain-modeling"><img src="https://agentmods.dev/badge/skills/znlgis/my-opencode-deepseek-config/domain-modeling/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.

agentmods 80×15 button for domain-modeling

Your own site · 80×15
<a href="https://agentmods.dev/skills/znlgis/my-opencode-deepseek-config/domain-modeling"><img src="https://agentmods.dev/badge/skills/znlgis/my-opencode-deepseek-config/domain-modeling.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 581 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00070 $0.00581
Opus 5 $0.00035 $0.00291
Sonnet 5 $0.00014 $0.00116
Haiku 4.5 $0.00007 $0.00058

Measured today against content hash 5e6ca370fabe, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

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

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.

opencode/skills/domain-modeling/SKILL.md · 56 lines

How it starts

The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Domain Modeling

An active discipline for keeping a project's domain language precise. It owns the CONTEXT.md glossary — a shared vocabulary of domain terms — and decides when a decision warrants an ADR. Trigger it when terms are used inconsistently, terminology drifts, or the same concept keeps being re-explained across sessions (each re-explanation wastes tokens that a one-sentence entry replaces).

Layout

  • A single CONTEXT.md at the project root holding the glossary, plus docs/adr/NNNN-*.md for architectural decisions.
  • For a codebase with several distinct contexts, use CONTEXT-MAP.md instead.
  • Create the file lazily — only when a term actually needs pinning down. Do not scaffold an empty glossary up front.

During a session

  • Challenge terms. When a word is used two ways, name the ambiguity and propose the sharper meaning.
  • Sharpen fuzzy language. Replace vague phrasing with the concrete term the code actually implements.
  • Stress-test relationships. Ask whether the way two concepts relate in conversation matches how they relate in code.
  • Cross-reference claims against code. A glossary entry that contradicts the implementation is wrong — fix the entry or the code.
  • Update CONTEXT.md inline, as you discover the sharper meaning. Never batch glossary edits at the end of a session.
  • Pin repeated explanations. When the same concept needs more than two sentences across messages or sessions, add a one-sentence CONTEXT.md entry so it never needs re-explaining.

CONTEXT.md rules

  • It is a glossary only — terms and their precise meanings. No implementation details, no how-to, no prose essays.
  • One entry per term, one sentence per meaning where possible.
  • If a term is genuinely contested, mark it Flagged: and note the competing meanings rather than silently picking one.

When to offer an ADR

Offer an architectural decision record only when all three hold:

  1. The decision is hard to reverse.
  2. It would be surprising without context.
  3. There was a real trade-off between viable options.

Read the full file on GitHub · 56 lines

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. today Changed · +5 lines · +24 tokens per session 5e6ca370fabe
  2. 5d ago First seen · 51 lines · 46 tokens per session scan A 1d32773ba698

Subscribe to this mod's changes

domain-modeling is a skill published in the GitHub repository znlgis/my-opencode-deepseek-config (57 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 581 once invoked, about $0.0003 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-09-03.

Related

Other skills, from other repositories