ubiquitous-language

ubiquitous-language is a skill for Claude Code from Future-CX/AI-Architecture-Toolkit. It costs 67 tokens per session (1,773 once invoked), scanned A, original, MIT.

A way to create a shared glossary of domain terms from a conversation. Domain-driven design, or DDD, is a software design approach that uses the language of the business or subject area in the code and documentation.

In plain words
What is it for?
Extracting concepts and relationships, proposing standard names, recording definitions in GLOSSARY.md, and flagging terms that need clarification.
Why use it?
It exposes ambiguous words, synonyms, vague terms, and jargon before they cause misunderstandings. The agreed terms give a team a consistent vocabulary for discussing the system.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

Good fit Extracting concepts and relationships, proposing standard names, recording definitions in GLOSSARY.md, and flagging terms that need clarification.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/future-cx/ai-architecture-toolkit/ubiquitous-language
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 Future-CX/AI-Architecture-Toolkit --skill ubiquitous-language
Clone the repo
git clone --depth 1 https://github.com/Future-CX/AI-Architecture-Toolkit

Made for: Claude Code.

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 ubiquitous-language

README.md
[![agentmods](https://agentmods.dev/badge/skills/future-cx/ai-architecture-toolkit/ubiquitous-language/github.svg)](https://agentmods.dev/skills/future-cx/ai-architecture-toolkit/ubiquitous-language)
Your own site
<a href="https://agentmods.dev/skills/future-cx/ai-architecture-toolkit/ubiquitous-language"><img src="https://agentmods.dev/badge/skills/future-cx/ai-architecture-toolkit/ubiquitous-language/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 ubiquitous-language

Your own site · 80×15
<a href="https://agentmods.dev/skills/future-cx/ai-architecture-toolkit/ubiquitous-language"><img src="https://agentmods.dev/badge/skills/future-cx/ai-architecture-toolkit/ubiquitous-language.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,773 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.00067 $0.01773
Opus 5 $0.00034 $0.00886
Sonnet 5 $0.00013 $0.00355
Haiku 4.5 $0.00007 $0.00177

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

Security

Grade A, and why

ubiquitous-language 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 9d 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/ubiquitous-language/SKILL.md · 116 lines

How it starts

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

Ubiquitous Language

Extract and formalize domain terminology from the current conversation into a consistent glossary, saved to a local file.

Process

  1. Scan the conversation for domain-relevant nouns, verbs, concepts, and known applications
  2. Identify problems:
    • Same word used for different concepts (ambiguity)
    • Different words used for the same concept (synonyms)
    • Vague or overloaded terms
    • Jargon, deprecated terms, vendor-specific labels, or words the team wants to avoid
  3. Propose a canonical glossary with opinionated term choices
  4. Write to GLOSSARY.md in the working directory using the format below
  5. Maintain the table of contents immediately below # Glossary
  6. Output a summary inline in the conversation

Output Format

Write a GLOSSARY.md file with this structure:

# Glossary

## Table of Contents

- [Order lifecycle](#order-lifecycle)
- [People](#people)
- [Applications](#applications)
- [Data objects](#data-objects)
- [Relationships](#relationships)
- [Jargon](#jargon)
- [Flagged ambiguities](#flagged-ambiguities)

## Order lifecycle

| Term        | Definition                                                                             | Aliases to avoid      |
| ----------- | -------------------------------------------------------------------------------------- | --------------------- |
| **Invoice** | A request for payment sent to a customer after delivery<br>- Billing: Billing Document | Bill, payment request |
| **Order**   | A customer's request to purchase one or more items<br>- ERP: Sales Order               | Purchase, transaction |

## People

| Term         | Definition                                                                   | Aliases to avoid       |
| ------------ | ---------------------------------------------------------------------------- | ---------------------- |
| **Customer** | A person or organization that places orders<br>- Commerce Platform: B2B Unit | Client, buyer, account |
| **User**     | An authentication identity in the system<br>- Commerce Platform: Customer    | Login, account         |

## Applications

| Application           | Definition                                                        | Capabilities and functions delivered                                                                                                                |
| --------------------- | ----------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Commerce Platform** | Application used to manage digital commerce interactions.         | Customer Management, Product Catalog, Order Capture<br>- Manage B2B units<br>- Maintain customer accounts<br>- Publish articles<br>- Capture orders |
| **ERP**               | System of record for core operational and financial transactions. | Order Management, Inventory Management, Financial Accounting<br>- Maintain sales orders<br>- Manage stock positions<br>- Post invoices              |

## Data objects

| Data object      | Definition                                                      | Owner or source of truth |
| ---------------- | --------------------------------------------------------------- | ------------------------ |
| **Availability** | Structured information representing whether something can sell. | Inventory Management     |
| **Customer**     | Structured information representing a person or organization.   | CRM                      |
| **Order**        | Structured information representing a customer's purchase.      | ERP                      |
| **Price**        | Structured information representing the amount charged.         | Pricing                  |
| **Product**      | Structured information representing an item offered for sale.   | Product Management       |

## Relationships

- An **Invoice** belongs to exactly one **Customer**
- An **Order** produces one or more **Invoices**

## Jargon

| Avoid this term | Preferred term | Reason |
| --------------- | -------------- | ------ |
| client          | **Customer**   | "Client" is used inconsistently for both customer organizations and API consumers. |
| user account    | **User**       | "User account" mixes authentication identity with customer or account ownership. |

## Flagged ambiguities

- "account" was used to mean both **Customer** and **User** — these are distinct concepts: a **Customer** places orders, while a **User** is an authentication identity that may or may not represent a **Customer**.

Read the full file on GitHub · 116 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. 9d ago First seen · 116 lines · 67 tokens per session scan A a645a1d3c31b

Subscribe to this mod's changes

ubiquitous-language is a skill published in the GitHub repository Future-CX/AI-Architecture-Toolkit (5 stars, last pushed 6d ago), licensed MIT. It adds 67 tokens to every session and 1,773 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-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens