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/amruthpillai/reactive-resume/domaingit clone --depth 1 https://github.com/amruthpillai/reactive-resumeWhat 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.00366 |
| Opus 5 | $0.00000 | $0.00183 |
| Sonnet 5 | $0.00000 | $0.00073 |
| Haiku 4.5 | $0.00000 | $0.00037 |
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 yesterday.
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
Domain Docs
How engineering skills consume this repository’s domain documentation.
Before exploring, read these
CONTEXT-MAP.mdat repository root. It points to context-specificCONTEXT.mdfiles. Read each context relevant to current work.docs/adr/for system-wide decisions touching current area.- Context-scoped ADR directories referenced by
CONTEXT-MAP.md.
If any file does not exist, proceed silently. Do not flag absence or suggest creating it upfront. /domain-modeling creates domain documents lazily when terminology or decisions become settled.
File structure
This repository uses a multi-context layout:
/
├── CONTEXT-MAP.md
├── docs/adr/ ← system-wide decisions
├── apps/
│ └── <context>/
│ └── CONTEXT.md
└── packages/
└── <context>/
├── CONTEXT.md
└── docs/adr/ ← context-specific decisions
CONTEXT-MAP.md is authoritative for context boundaries. Not every app or package needs a CONTEXT.md; create one only when it represents a meaningful domain context.
Use glossary vocabulary
When output names a domain concept—in issue titles, refactor proposals, hypotheses, or test names—use terms defined in relevant CONTEXT.md. Do not drift to explicitly avoided synonyms.
Missing terminology signals either language foreign to project or genuine domain-model gap. Reconsider first; otherwise note gap for /domain-modeling.
Flag ADR conflicts
If output contradicts existing ADR, surface conflict explicitly instead of silently overriding:
Contradicts ADR-0007 (event-sourced orders), 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.
- yesterday First seen · 43 lines · 0 tokens per session scan A 49b13f118a05
domain is an agent published in the GitHub repository amruthpillai/reactive-resume (41,957 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 366 tokens. 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-30.
Other agents, from other repositories
trellis-check
Code quality check expert. Reviews code changes against specs and self-fixes issues.
trellis-research
Code and tech search expert. Finds files, patterns, and tech solutions, and PERSISTS every finding to the current task's research/ directory. No code modifications outside that directory.
trellis-implement
Code implementation expert. Understands specs and requirements, then implements features. No git commit allowed.
check
Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.
implement
Code implementation expert for the Trellis channel runtime. Understands specs and task artifacts, then implements features. No git commit allowed.
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.