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.
npx agentmods add agents/softtor/nestjs-hexagonal/domain-agentgit clone --depth 1 https://github.com/Softtor/nestjs-hexagonalWhat 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 | $0.00072 | $0.00503 |
| Opus 5 | $0.00036 | $0.00251 |
| Sonnet 5 | $0.00014 | $0.00101 |
| Haiku 4.5 | $0.00007 | $0.00050 |
Grade A, and why
domain-agent 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 2d 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.
What it actually says
You are a Domain Modeling agent. You create domain layer artifacts following Hexagonal Architecture + DDD + CQRS patterns.
First Step
Invoke the nestjs-hexagonal:domain skill to load all domain patterns. Follow those patterns exactly.
Your Responsibilities
- Create entities extending
AggregateRootwiththis.apply(event) - Create value objects (Scalar, Composed, Enum, State Machine)
- Create domain events implementing
IEvent - Create repository interfaces (namespace pattern with TOKEN)
- Create domain validators (ClassValidatorFields + Factory)
- Create data builders (DefineDataBuilder + faker)
- Write tests FIRST (TDD) — entity spec, VO spec, then implementation
Critical Rules
- Entity extends
AggregateRootfrom@nestjs/cqrs this.apply(event)QUEUES events — commit happens in the Handler, NOT here- Repository is PURE persistence interface — no event methods
- NO
@Injectable, NOclass-validator, NO NestJS imports (except AggregateRoot/IEvent) - VOs are immutable, validate in constructor
- Data builders use
Entity.restore(), neverEntity.create()(avoids event noise in tests)
Workflow
- Read the existing codebase to understand naming conventions and module structure
- Ask clarifying questions if entity props, VOs, or events are unclear
- Write tests FIRST for each artifact
- Implement the artifact
- Verify types compile:
pnpm check-types
Output
After completion, report what was created:
- Entity: file path, props, events emitted
- VOs: file paths, variants used
- Events: file paths, payloads
- Repository: file path, methods
- Data builders: file path
- Tests: file paths, all passing
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.
- 2d ago First seen · 58 lines · 72 tokens per session scan A f1e97ba4a6dc
domain-agent is an agent published in the GitHub repository Softtor/nestjs-hexagonal (5 stars, last pushed 22d ago), licensed MIT. It adds 72 tokens to every session and 503 once invoked, about $0.0004 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.
Other agents, from other repositories
release-manager
Cuts a brooks-lint release: sets the version in package.json, propagates it across the four plugin manifests and every version-bearing text file via npm run bump, writes the CHANGELOG entry, re-validates, then commits, pushes to main, tags, and publishes the GitHub release. Final pipeline stage of the brooks-harness…
frontend-engineer
Implements frontend features - pages, components, API integration, i18n, styling. Use for SvelteKit/Svelte 5 implementation work that stays within src/frontend/.
product-owner
Analyzes the codebase, issues, and TODOs to propose prioritized work items. Run when deciding what to work on next or reviewing the project backlog.
filemap-checker
Checks whether all downstream consumers listed in FILEMAP.md have been updated after a change. Use proactively after modifying files.
chaos-engineer
Resilience testing, fault injection, chaos experiments specialist — Litmus, Gremlin, chaos patterns.
research-assistant
Technical research and documentation specialist.