domain-glossary

domain-glossary is a skill for Claude Code, Codex from kambleakash0/agent-skills. It costs 18 tokens per session (1,167 once invoked), scanned A, original, MIT.

A tool for extracting a shared glossary of domain terms from a conversation. In domain-driven design, this glossary records the words a team agrees to use for important business concepts.

In plain words
What is it for?
Use it to identify important domain terms, resolve naming conflicts, suggest standard names, and maintain a DOMAIN_GLOSSARY.md file.
Why use it?
It helps prevent confusion when the same word has several meanings or different words refer to the same thing.

Skill for Claude CodeCodex

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

Good fit Use it to identify important domain terms, resolve naming conflicts, suggest standard names, and maintain a DOMAIN_GLOSSARY.md file.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kambleakash0/agent-skills/domain-glossary
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 kambleakash0/agent-skills --skill domain-glossary
Clone the repo
git clone --depth 1 https://github.com/kambleakash0/agent-skills

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-glossary

README.md
[![agentmods](https://agentmods.dev/badge/skills/kambleakash0/agent-skills/domain-glossary/github.svg)](https://agentmods.dev/skills/kambleakash0/agent-skills/domain-glossary)
Your own site
<a href="https://agentmods.dev/skills/kambleakash0/agent-skills/domain-glossary"><img src="https://agentmods.dev/badge/skills/kambleakash0/agent-skills/domain-glossary/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-glossary

Your own site · 80×15
<a href="https://agentmods.dev/skills/kambleakash0/agent-skills/domain-glossary"><img src="https://agentmods.dev/badge/skills/kambleakash0/agent-skills/domain-glossary.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,167 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.
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.00018 $0.01167
Opus 5 $0.00009 $0.00583
Sonnet 5 $0.00004 $0.00233
Haiku 4.5 $0.00002 $0.00117

Measured 11d ago against content hash 1a688fe8298e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

domain-glossary 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 11d 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.

skills/domain-glossary/SKILL.md · 126 lines

How it starts

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

Ubiquitous Language Glossary

This skill turns an ongoing conversation into a DDD-style ubiquitous language document. It scans for domain terms, resolves ambiguities, proposes canonical names, and writes a living glossary to DOMAIN_GLOSSARY.md in the working directory.

When to Use

Use this skill when:

  • You’re discussing a domain, feature, product, or system and want shared language.
  • You mention “ubiquitous language”, “domain model”, or “DDD”.
  • You keep tripping over overloaded terms (“account”, “user”, “customer”) and want them nailed down.

You can re-run this skill as the conversation evolves to keep the glossary up to date.

Process

  1. Scan the conversation and context

    • Read the current conversation, plus any attached docs or PRDs, for domain-relevant nouns, verbs, and concepts.
    • Ignore generic technical terms (array, function, endpoint) unless they carry domain meaning here.
  2. Detect language problems

    Identify and note where:

    • The same word is used for different concepts (ambiguity).
    • Different words are used for the same concept (synonyms).
    • Terms are vague, overloaded, or inconsistently applied.
  3. Propose a canonical glossary

    • Choose one canonical term per concept and be opinionated about names.
    • For each term, write a tight, one‑sentence definition that says what it is, not how it’s implemented.
    • List “aliases to avoid” so everyone sees which terms should be retired in this context.
  4. Group terms into sections

    • Group related terms under headings (e.g. “Order lifecycle”, “People”, “Billing”, “Content model”).
    • Each group gets its own Markdown table with columns: Term, Definition, Aliases to avoid.
    • If everything belongs to a single cohesive cluster, one table is fine—don’t force fake groupings.
  5. Describe relationships

    • Add a “Relationships” section that describes how the key terms relate to each other in plain language.
    • Use bold term names and, where obvious, simple cardinalities (e.g. “An Order has many Line items”).

Read the full file on GitHub · 126 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. 11d ago First seen · 126 lines · 18 tokens per session scan A 1a688fe8298e

Subscribe to this mod's changes

domain-glossary is a skill published in the GitHub repository kambleakash0/agent-skills (9 stars, last pushed 2d ago), licensed MIT. It adds 18 tokens to every session and 1,167 once invoked, about $0.0001 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-31.