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/sswconsulting/ssw.verticalslicearchitecture/domaingit clone --depth 1 https://github.com/SSWConsulting/SSW.VerticalSliceArchitectureWrote 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.
[](https://agentmods.dev/agents/sswconsulting/ssw.verticalslicearchitecture/domain)<a href="https://agentmods.dev/agents/sswconsulting/ssw.verticalslicearchitecture/domain"><img src="https://agentmods.dev/badge/agents/sswconsulting/ssw.verticalslicearchitecture/domain.svg" alt="Measured on agentmods" height="20"></a>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.00000 | $0.00644 |
| Opus 5 | $0.00000 | $0.00322 |
| Sonnet 5 | $0.00000 | $0.00129 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
domain 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 6d 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.
This is a copy
75% identical to domain — 37 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.
How it starts
The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domain Docs
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
Before exploring, read these
CONTEXT.mdat the repo root — the glossary / ubiquitous language.docs/adr/— read ADRs that touch the area you're about to work in. ADRs are managed by Log4brains and namedYYYYMMDD-<slug>.md;docs/adr/index.mdlists them anddocs/adr/template.mdis the starting point for a new one.
If any of these files don't exist, proceed silently. Don't flag their absence; don't suggest creating them upfront. The /domain-modeling skill (reached via /grill-with-docs and /improve-codebase-architecture) creates them lazily when terms or decisions actually get resolved.
Those skills ship outside this repo. .claude/skills/ here holds add-entity, add-slice, add-adr, aspire, and bump-version — /add-adr is the in-repo way to record a decision once one is settled. If a referenced skill isn't installed, do the reading described above by hand and move on rather than trying to invoke it.
File structure
This is a single-context repo — one glossary, one ADR directory, both at the root:
/
├── CONTEXT.md ← created lazily by /domain-modeling
├── docs/adr/
│ ├── index.md
│ ├── template.md
│ ├── 20251018-api-use-fastendpoints-instead-of-minimal-apis.md
│ ├── 20260612-use-aggregate-specification-classes-with-factory-methods.md
│ └── ... ← run `ls docs/adr/` for the full set
└── src/
├── WebApi/
└── ServiceDefaults/
Vertical slices under src/WebApi/Features/ are feature folders, not bounded contexts — they don't get their own CONTEXT.md or docs/adr/. If this repo ever splits into genuinely separate contexts, switch to a root CONTEXT-MAP.md pointing at per-context CONTEXT.md files.
Use the glossary's vocabulary
When your output names a domain concept (in an issue title, a refactor proposal, a hypothesis, a test name), use the term as defined in CONTEXT.md. Don't drift to synonyms the glossary explicitly avoids.
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.
- 6d ago First seen · 45 lines · 0 tokens per session scan A c5e6488b11e5
domain is an agent published in the GitHub repository SSWConsulting/SSW.VerticalSliceArchitecture (397 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 644 tokens. A static security scan graded it A with 0 findings. It is 75% identical to domain, differing in 37 lines, and is treated as a copy.
Other agents, from other repositories
cli
Use as the primary implementation agent for this .NET repository. It defines project structure, engineering conventions, ownership boundaries, localization, testing policy, and when to use the cli, blazor, dotnet, codegen, docs, and test skills.
Reviewer
Use when reviewing Perigon.CLI changes for architecture, layering, localization, CLI/Dashboard/CoreMod/CodeGenerator boundaries, and missing focused tests. Read-only reviewer for implementation plans or diffs.
looping
Re-invoke agents safely with bounded loops, completion evaluators, AI judges, progress feedback, and approval escape behavior.
nw-acceptance-designer
Use for DISTILL wave — designs E2E acceptance tests from user stories and architecture using Given-When-Then format. EXPANDED scope (plan v3 §3.A, 2026-05-19) — exclusive test-expertise owner; authors ATs with maximum PBT + parametrize density, runs self-completeness audit (7-category taxonomy + 15-item checklist)…
frontend-engineer
Implements frontend features - pages, components, API integration, i18n, styling. Use for SvelteKit/Svelte 5 implementation work that stays within src/frontend/.
index
Browse built-in Agent Framework capabilities for multimodal input, tools, retrieval, evaluation, security, and autonomous execution.