A repository glossary that records the business terms and concepts used in a project. It follows Domain-Driven Design, an approach that keeps software language aligned with the real-world problem it serves.

Use it to identify domain vocabulary, clarify business rules and states, document actors and processes, and create or refresh docs/GLOSSARY.md.

It reduces confusion when the same business idea has different names, or when one term means different things in different parts of a system.

glossary — Skill for Claude Code and Codex by stefanrossmeier

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 stefanrossmeier/ai-craftkit --skill glossary

Clone the repo

git clone --depth 1 https://github.com/stefanrossmeier/ai-craftkit

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/stefanrossmeier/ai-craftkit/glossary/github.svg)](https://agentmods.dev/skills/stefanrossmeier/ai-craftkit/glossary)

Your own site

<a href="https://agentmods.dev/skills/stefanrossmeier/ai-craftkit/glossary"><img src="https://agentmods.dev/badge/skills/stefanrossmeier/ai-craftkit/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/stefanrossmeier/ai-craftkit/glossary"><img src="https://agentmods.dev/badge/skills/stefanrossmeier/ai-craftkit/glossary.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 5,646 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.

Model	Per session	Once invoked
Fable 5.1	$0.00051	$0.05646
Opus 5.5	$0.00020	$0.02258
Sonnet 5.5	$0.00010	$0.01129
Haiku 4.5	$0.00005	$0.00565

Measured 2mo ago against content hash cf7ab70e4238, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 2mo 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/glossary/SKILL.md · 1,067 lines

How it starts

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

Glossary Skill

Command: /glossary

Identify the repository's domain-specific language and create an evidence-based glossary from a Domain-Driven Design perspective.

The skill focuses on the language of the problem domain: business concepts, actors, rules, events, states, processes, classifications, measures, and artifacts. It deliberately excludes ordinary software-engineering vocabulary unless a technical-looking term has a specific meaning in the domain.

Invocation Model

Use this skill when the user calls:

/glossary

This is a skill invocation, not a shell command.

It has no command-line flags, parameters, modes, or options. If the user adds text after the invocation, treat it as plain-language scoping guidance.

Examples:

/glossary

/glossary focus on the claims workflow

/glossary inspect only the reserving and settlement areas

/glossary refresh the existing glossary and highlight terminology drift

Do not document or advertise flag-based usage.

Purpose

Generate or update:

docs/GLOSSARY.md

The document should help developers, architects, analysts, testers, product experts, and future agents use the repository's domain language consistently.

The skill should:

identify terms that carry domain meaning
explain those terms in plain business language
connect definitions to repository evidence
group terms by candidate bounded context when useful
expose inconsistent, ambiguous, overloaded, or competing terminology
distinguish observed language from domain-expert-approved language
identify important domain concepts whose meaning cannot be recovered from the repository
avoid filling the glossary with frameworks, infrastructure, and implementation jargon

A repository can reveal language that is encoded in software. It cannot, by itself, prove that this language is accepted by domain experts or used consistently in real conversations.

Therefore, treat the result as an observed or candidate ubiquitous language until a knowledgeable human reviews it.

Read the full file on GitHub · 1,067 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

2mo ago First seen · 1,067 lines · 51 tokens per session scan A cf7ab70e4238

Subscribe to this mod's changes

glossary is a skill published in the GitHub repository stefanrossmeier/ai-craftkit (5 stars, last pushed 4d ago), licensed Apache-2.0. It adds 51 tokens to every session and 5,646 once invoked, about $0.0002 per session on Opus 5.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.

Writing and docs adr ai-agents ai-assisted-development developer-tools documentation mermaid

glossary next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
glossarystefanrossmeier/ai-craftkit	Skill	5	4d ago	Apache-2.0	A	51	Claude Code, Codex
architecture-decision-record-maintainer-skillarchitecture-decision-record/architecture-decision-record	Skill	17k	8d ago	none	A	92	Claude Code, Codex
architecture-decision-record-skillarchitecture-decision-record/architecture-decision-record	Skill	17k	8d ago	none	A	108	Claude Code, Codex
atlas-adrtonone-ai/tonone	Skill	77	23d ago	MIT	A	51	Claude Code
bootstrapEvolveHQ/docflow	Skill	16	15d ago	MIT	A	114	Claude Code, Codex
agent-waveEvolveHQ/docflow	Skill	16	15d ago	MIT	A	82	Claude Code, Codex
new-planEvolveHQ/docflow	Skill	16	15d ago	MIT	A	118	Claude Code, Codex