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/brettkinny/dotty-stackchan/domaingit clone --depth 1 https://github.com/BrettKinny/dotty-stackchanWhat 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.00000 | $0.00417 |
| Opus 5 | $0.00000 | $0.00209 |
| Sonnet 5 | $0.00000 | $0.00083 |
| Haiku 4.5 | $0.00000 | $0.00042 |
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 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.
This is a copy
84% identical to domain — 33 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.
What it actually says
Domain Docs
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
This is a single-context repo: one CONTEXT.md + docs/adr/ at the repo root cover the whole Dotty stack. (Note: CLAUDE.md at the root is the always-on architecture reference and the authoritative starting point regardless — CONTEXT.md is the lazily-grown domain glossary the producer skills maintain.)
Before exploring, read these
CONTEXT.mdat the repo root.docs/adr/— read ADRs that touch the area you're about to work in.
If any of these files don't exist, proceed silently. Don't flag their absence; don't suggest creating them upfront. The producer skill (/grill-with-docs) creates them lazily when terms or decisions actually get resolved.
File structure
Single-context repo:
/
├── CLAUDE.md ← always-on architecture reference (already exists)
├── CONTEXT.md ← domain glossary (created lazily by /grill-with-docs)
├── docs/adr/ ← architectural decision records (created lazily)
│ ├── 0001-....md
│ └── 0002-....md
└── ...
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.
If the concept you need isn't in the glossary yet, that's a signal — either you're inventing language the project doesn't use (reconsider) or there's a real gap (note it for /grill-with-docs).
Flag ADR conflicts
If your output contradicts an existing ADR, surface it explicitly rather than silently overriding:
Contradicts ADR-0007 (...) — but worth reopening because…
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 · 39 lines · 0 tokens per session scan A d4b2ac27e868
domain is an agent published in the GitHub repository BrettKinny/dotty-stackchan (105 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 417 tokens. A static security scan graded it A with 0 findings. It is 84% identical to domain, differing in 33 lines, and is treated as a copy.
Other agents, from other repositories
debugger
Use when something is broken and the cause isn't obvious — bugs, error stack traces, "works in dev not prod", performance regressions, weird behavior after a change.
reviewer
Use to review code changes (diffs, PRs, single files) for bugs, security issues, performance problems, style violations, and missing edge cases. Read-only — produces a review, doesn't fix code.
researcher
Use for any task requiring external research — finding documentation, comparing libraries, looking up release notes, market research, fact-checking. Read-only by design — won't modify files. Auto-delegate when query starts with "find", "research", "look up", "compare", "what is the latest".
tester
Use to write, run, or debug tests. Auto-discovers test framework (pytest, jest, vitest, go test, cargo test). Invoke after implementing a feature that needs coverage, or when tests are failing.
WEBHOOK_SDK
Write a custom Commonly agent in 30 lines of Python. The SDK is a single stdlib-only file that implements the four CAP verbs; the scaffolder wires publish + install + token-issuance in one command.
Reviewer
Use when: reviewing C++ code for quality, checking memory safety and RAII compliance, verifying cross-platform portability, enforcing API consistency, reviewing for thread safety, checking const-correctness, auditing error handling patterns.