issues: Agent for Claude Code

.claude/agents/domain-model.md

domain-model is an agent for Claude Code from vepo/issues. It costs 30 tokens per session (249 once invoked), scanned A, original, Apache-2.0.

A planning agent for defining the concepts and vocabulary of an issue-tracking feature before coding. It describes entities, state changes, rules, labels, and where they belong in the code.

In plain words
What is it for?
Use it before adding ticket, workflow, project, or notification features. It helps prepare domain definitions, implementation boundaries, rules, and test scenarios.
Why use it?
It prevents developers from building features around unclear or conflicting terms. It also exposes required documentation, API, and test changes early.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

This is vepo/issues's own configuration. It tells Claude Code how to work on issues 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 issues configures →

View source ↗ vepo/issues
Reuse

Borrowing it

Nothing to install: this file belongs to vepo/issues. 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/vepo/issues/main/.claude/agents/domain-model.md
Clone the repo
git clone --depth 1 https://github.com/vepo/issues

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 domain-model

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

Your own site · 80×15
<a href="https://agentmods.dev/agents/vepo/issues/domain-model"><img src="https://agentmods.dev/badge/agents/vepo/issues/domain-model.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 249 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.00030 $0.00249
Opus 5.5 $0.00012 $0.00100
Sonnet 5.5 $0.00006 $0.00050
Haiku 4.5 $0.00003 $0.00025

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

Security

Grade A, and why

domain-model 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 1mo 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.

.claude/agents/domain-model.md · 29 lines

What it actually says

You are the Domain Model agent for Issues.

Read docs/domain-specification.md and .cursor/rules/issues-model.mdc.

Your job

  1. Restate the requested change in ubiquitous language (ticket, workflow, project terms).
  2. List new or changed concepts: entities, transitions, invariants, UI labels.
  3. Propose domain-spec edits (sections and terms) before any src/main code.
  4. Map concepts to packages (ticket, workflow, project, …).
  5. Flag doc updates: feature-catalog.md, ARCHITECTURE.md §13.

Output

  • Glossary additions/changes (term → meaning)
  • Invariants the implementation must preserve
  • Suggested test scenarios in domain language (hand off to tdd-red)
  • Whether ARCHITECTURE.md or API surface changes are needed

Forbidden

  • Writing production code in this phase
  • Inventing domain terms not aligned with existing workflow/ticket vocabulary
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. 1mo ago First seen · 29 lines · 30 tokens per session scan A af48cfd71dd9

Subscribe to this mod's changes

domain-model is an agent published in the GitHub repository vepo/issues (8 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 249 once invoked, about $0.0001 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.

Related

Other agents, from other repositories