domain-modeling

domain-modeling is a skill for Codex from d0hx4n2503/Agent-Skills. It costs 43 tokens per session (776 once invoked), scanned A, a copy of domain-modeling, Apache-2.0.

A process for defining the important concepts and vocabulary in a software project. It records agreed terms, examples, and architecture decisions in files such as a project context document and decision records.

In plain words
What is it for?
Use it to settle domain terminology, build a shared glossary, explore edge cases, record architectural decisions, and keep that model current as the project changes.
Why use it?
It reduces confusion when developers use the same word in different ways. Written decisions also give future contributors a reference for how the system is meant to work.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it to settle domain terminology, build a shared glossary, explore edge cases, record architectural decisions, and keep that model current as the project changes.

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

Made for: 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/d0hx4n2503/agent-skills/domain-modeling/github.svg)](https://agentmods.dev/skills/d0hx4n2503/agent-skills/domain-modeling)
Your own site
<a href="https://agentmods.dev/skills/d0hx4n2503/agent-skills/domain-modeling"><img src="https://agentmods.dev/badge/skills/d0hx4n2503/agent-skills/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/d0hx4n2503/agent-skills/domain-modeling"><img src="https://agentmods.dev/badge/skills/d0hx4n2503/agent-skills/domain-modeling.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 776 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 91% 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.1 $0.00043 $0.00776
Opus 5 $0.00022 $0.00388
Sonnet 5 $0.00009 $0.00155
Haiku 4.5 $0.00004 $0.00078

Measured 11d ago against content hash c98974d5c846, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, 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 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.

Origin

This is a copy

91% identical to domain-modeling — 21 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.

skills/development/domain-modeling/SKILL.md · 74 lines

How it starts

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

Domain Modeling

Actively build and sharpen the project's domain model as you design. This is the active discipline — challenging terms, inventing edge-case scenarios, and writing the glossary and decisions down the moment they crystallise. (Merely reading CONTEXT.md for vocabulary is not this skill — that's a one-line habit any skill can do. This skill is for when you're changing the model, not just consuming it.)

File structure

Most repos have a single context:

/
├── CONTEXT.md
├── docs/
│   └── adr/
│       ├── 0001-event-sourced-orders.md
│       └── 0002-postgres-for-write-model.md
└── src/

If a CONTEXT-MAP.md exists at the root, the repo has multiple contexts. The map points to where each one lives:

/
├── CONTEXT-MAP.md
├── docs/
│   └── adr/                          ← system-wide decisions
├── src/
│   ├── ordering/
│   │   ├── CONTEXT.md
│   │   └── docs/adr/                 ← context-specific decisions
│   └── billing/
│       ├── CONTEXT.md
│       └── docs/adr/

Create files lazily — only when you have something to write. If no CONTEXT.md exists, create one when the first term is resolved. If no docs/adr/ exists, create it when the first ADR is needed.

During the session

Challenge against the glossary

When the user uses a term that conflicts with the existing language in CONTEXT.md, call it out immediately. "Your glossary defines 'cancellation' as X, but you seem to mean Y — which is it?"

Sharpen fuzzy language

When the user uses vague or overloaded terms, propose a precise canonical term. "You're saying 'account' — do you mean the Customer or the User? Those are different things."

Discuss concrete scenarios

When domain relationships are being discussed, stress-test them with specific scenarios. Invent scenarios that probe edge cases and force the user to be precise about the boundaries between concepts.

Cross-reference with code

When the user states how something works, check whether the code agrees. If you find a contradiction, surface it: "Your code cancels entire Orders, but you just said partial cancellation is possible — which is right?"

Read the full file on GitHub · 74 lines

Files

What ships with it

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

  1. 11d ago First seen · 74 lines · 43 tokens per session scan A c98974d5c846

Subscribe to this mod's changes

domain-modeling is a skill published in the GitHub repository d0hx4n2503/Agent-Skills (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 43 tokens to every session and 776 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to domain-modeling, differing in 21 lines, and is treated as a copy.

Related

Other skills, from other repositories

casely

Virtual QA Lead that turns requirement documents into review-ready, TestRail-importable test cases in one conversation — no commands to memorize. Use this skill whenever the user has requirements, a spec, a user story, or acceptance criteria (PDF, DOCX, XLSX, TXT, MD, or pasted text) and wants test cases, a test plan…

JohnWayneeee/casely-qa-skill · 233 tokens

story-repo-scout

Inspect a repository for story-specific implementation evidence, applicable decisions, validation prior art, and bounded planning-critical external primary sources, then produce compact Repo Context. Use for pre-implementation file discovery and greenfield path grounding; use tester-mindset for test strategy and avoid…

n-n-code/n-n-code-skills · 76 tokens

story-implementation-planner

Create a constraint-aware implementation plan from a Ready Story Card and sufficiently evidenced Repo Context. Use when the requested artifact is the plan itself; use story-to-plan-orchestrator for multi-stage preparation, packet completion, resumption, or validation. Avoid story drafting, repo scouting, and direct…

n-n-code/n-n-code-skills · 65 tokens

story-to-plan-orchestrator

Coordinate multi-stage story-to-plan preparation across story-clarifier, story-repo-scout, and story-implementation-planner. Use for complete implementation-ready handoffs, two or more missing stages, split-slice selection, partial-packet resumption, consistency validation, or stale-stage recovery before coding; use a…

n-n-code/n-n-code-skills · 83 tokens

context-engineering

Workflow for context packets, context audits, compaction, handoffs, session memory, and deciding what AI-agent context to load, retrieve, trim, summarize, refresh, or omit. Use for context rot, context flooding, stale or missing context, task switching, and long-running agent sessions. Do not use when prompt wording…

n-n-code/n-n-code-skills · 89 tokens

setup-playwright

Use when adding, extending, or repairing a repo-owned Playwright test harness across Node Playwright Test, Playwright Pytest, or .NET/Java test frameworks. Also use when explicitly persisting @playwright/cli developer tooling, or adding or regenerating Playwright Test Agent definitions for a compatible Node Playwright…

n-n-code/n-n-code-skills · 93 tokens