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/open-gsd/gsd-core/domaingit clone --depth 1 https://github.com/open-gsd/gsd-coreWhat 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.00346 |
| Opus 5 | $0.00000 | $0.00173 |
| Sonnet 5 | $0.00000 | $0.00069 |
| Haiku 4.5 | $0.00000 | $0.00035 |
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 3d 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
100% identical to domain — 0 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 engineering skills consume this repo's domain documentation.
Layout: single-context
/
├── CONTEXT.md ← domain glossary + recurring PR rules + workflow learnings
├── docs/adr/ ← architectural decisions
│ ├── 0001-dispatch-policy-module.md
│ └── 0002-command-contract-validation-module.md
└── ...
Before exploring, read these
CONTEXT.mdat the repo root — domain terms, module names, recurring PR mistakes, workflow learnings. Read in full before naming anything or proposing architecture changes.docs/adr/— read ADRs relevant to the area you're working in before proposing structural changes. If your output contradicts an ADR, surface it explicitly:Contradicts ADR-0002 — but worth reopening because…
If either file doesn't exist yet, proceed silently.
Use the glossary's vocabulary
When naming modules, writing issue titles, test descriptions, or commit messages — use terms as defined in CONTEXT.md. Don't drift to synonyms. If you need a concept that isn't in the glossary, note it for /grill-with-docs rather than inventing language.
CONTEXT.md sections
- Domain terms — canonical module names and seam vocabulary (Dispatch Policy Module, Command Contract Validation Module, etc.)
- Recurring PR mistakes — CodeRabbit findings that recur; check before writing tests, shell scripts, changesets, or docs
- Workflow learnings — patterns learned from triage + PR cycles; check before writing new command/workflow files or test paths
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.
- 3d ago First seen · 33 lines · 0 tokens per session scan A c1982e4b432c
domain is an agent published in the GitHub repository open-gsd/gsd-core (8,999 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 346 tokens. A static security scan graded it A with 0 findings. It is 100% identical to domain, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
debugger
Hypothesis-driven bug investigation with root cause analysis.
security
OWASP security audit, dependency risks, and secrets detection.
javascript-pro
Modern JavaScript specialist for browser, Node.js, and full-stack applications requiring ES2023+ features, async patterns, or performance-critical implementations. Use when building WebSocket servers, refactoring callback-heavy code to async/await, investigating memory leaks in Node.js, scaffolding ES module libraries…
typescript-pro
TypeScript specialist for advanced type system patterns, complex generics, type-level programming, and end-to-end type safety across full-stack applications. Use when designing type-first APIs, creating branded types for domain modeling, building generic utilities, implementing discriminated unions for state machines…
doc-writer
Documentation generation from code — API docs, inline comments, READMEs.
git-ops
Conflict resolution, rebase strategy, PR preparation, and changelog generation.