agentmods.dev

timing-cli: Skill for Claude Code

.agents/skills/domain-modeling/SKILL.md

domain-modeling is a skill for Claude Code, Codex from sussdorff/timing-cli. It costs 83 tokens per session (936 once invoked), scanned A, original, MIT.

A codebase terminology and decision-documenting workflow. It clarifies the meanings of terms and can maintain a glossary plus ADRs or BDRs, which record technical or business decisions.

In plain words
What is it for?
Use it to define domain terms, test them against code and edge cases, update CONTEXT.md, and create decision records when the stated criteria are met.
Why use it?
It reduces confusion caused by overloaded or conflicting terms and keeps important decisions linked to the project's shared vocabulary.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions CLAUDE.md; installed under .agents/ (shared by several agents); mentions AGENTS.md.

This is sussdorff/timing-cli's own configuration. It tells Claude Code and Codex how to work on timing-cli itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything timing-cli configures →

not rated 1repo changed 24d ago A scan 83 tokens original MIT
View source ↗ sussdorff/timing-cli
Reuse

Borrowing it

Nothing to install: this file belongs to sussdorff/timing-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/sussdorff/timing-cli/main/.agents/skills/domain-modeling/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/sussdorff/timing-cli

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/sussdorff/timing-cli/domain-modeling/github.svg)](https://agentmods.dev/skills/sussdorff/timing-cli/domain-modeling)
Your own site
<a href="https://agentmods.dev/skills/sussdorff/timing-cli/domain-modeling"><img src="https://agentmods.dev/badge/skills/sussdorff/timing-cli/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/sussdorff/timing-cli/domain-modeling"><img src="https://agentmods.dev/badge/skills/sussdorff/timing-cli/domain-modeling.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 83 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 936 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.00083 $0.00936
Opus 5.5 $0.00033 $0.00374
Sonnet 5.5 $0.00017 $0.00187
Haiku 4.5 $0.00008 $0.00094

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

.agents/skills/domain-modeling/SKILL.md · 55 lines

How it starts

The opening of the file, as written. The whole thing — 55 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. Challenge terms, invent edge-case scenarios, and write the glossary and decision records the moment they crystallise. Merely reading GLOSSARY.md for vocabulary is not this skill; this skill changes the domain model.

Inputs

  • The current conversation, code, and any existing GLOSSARY.md / GLOSSARY-MAP.md.
  • Existing docs/adr/, docs/bdr/ and docs/decisions.md when they exist.

Outputs

  • An updated GLOSSARY.md, created lazily. It is a glossary and nothing else.
  • An ADR in docs/adr/ or a BDR in docs/bdr/ only when the offer tests pass.
  • One line per record in the docs/decisions.md decision index.

Workflow

  1. Before writing, migrate a legacy glossary on touch, all in one change. Paths are relative to the context root.
    • With CONTEXT.md and no GLOSSARY.md, run git mv CONTEXT.md GLOSSARY.md. With both, merge the CONTEXT.md terms into GLOSSARY.md, ask the user about conflicting definitions, then git rm CONTEXT.md.
    • Move the old ## Decisions lines into that context's docs/decisions.md and rewrite each link relative to docs/decisions.md: docs/adr/x.md becomes adr/x.md, docs/bdr/x.md becomes bdr/x.md. Merge into an existing docs/decisions.md; never overwrite it.
    • With CONTEXT-MAP.md, run git mv CONTEXT-MAP.md GLOSSARY-MAP.md and migrate every context it lists in the same change, so the map never mixes old and new names.
    • Update references to the renamed files in AGENTS.md, CLAUDE.md, docs/agents/domain.md and the per-context links of GLOSSARY-MAP.md.
  2. Challenge terms against GLOSSARY.md. Call out conflicts immediately.
  3. Sharpen fuzzy or overloaded language into a canonical term.
  4. Stress-test relationships with concrete scenarios, including edge cases.
  5. Check the code when the user states how something works. Surface contradictions.
  6. Update GLOSSARY.md inline when a term is resolved. Use GLOSSARY-FORMAT.md. Create the file lazily. It holds terms only: no decision index, no spec, no implementation detail.
  7. Offer a decision record only when the three tests in ADR-FORMAT.md or BDR-FORMAT.md all hold. Business and product commitments go to BDRs. Technical shape goes to ADRs. After writing either record, add one index line to docs/decisions.md. Whenever you touch decisions, also add index lines for records in docs/adr/ and docs/bdr/ that the index does not list yet; upstream domain-modeling writes ADRs without indexing them.

Read the full file on GitHub · 55 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. 24d ago Changed · +7 lines · +54 tokens per session caf9488cd421
  2. 1mo ago First seen · 48 lines · 29 tokens per session scan A b004dfda87ba

Subscribe to this mod's changes

domain-modeling is a skill published in the GitHub repository sussdorff/timing-cli (1 stars, last pushed 10d ago), licensed MIT. It adds 83 tokens to every session and 936 once invoked, about $0.0003 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-09-24.

PlanningWriting and docs
Related

Other skills, from other repositories

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

systematic-debugging

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

obra/superpowers · 21 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

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 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