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/nearform/lastlight/domaingit clone --depth 1 https://github.com/nearform/lastlightWhat 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.00428 |
| Opus 5 | $0.00000 | $0.00214 |
| Sonnet 5 | $0.00000 | $0.00086 |
| Haiku 4.5 | $0.00000 | $0.00043 |
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
83% 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 repo is single-context: one CONTEXT.md + docs/adr/ at the repo root.
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 /domain-modeling skill (reached via /grill-with-docs and /improve-codebase-architecture) creates them lazily when terms or decisions actually get resolved.
Note: the repo-root
CLAUDE.mdandspec/README.mdare the day-to-day orientation and rebuild-grade spec respectively.CONTEXT.mdis narrower — the project's domain glossary (ubiquitous language), seeded lazily as terms get pinned down. It does not yet exist.
File structure
/
├── CONTEXT.md ← domain glossary (created lazily)
├── docs/adr/ ← architectural decision records (created lazily)
│ ├── 0001-....md
│ └── 0002-....md
└── src/
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 /domain-modeling).
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 · 41 lines · 0 tokens per session scan A 396806d2b986
domain is an agent published in the GitHub repository nearform/lastlight (22 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 428 tokens. A static security scan graded it A with 0 findings. It is 83% identical to domain, differing in 33 lines, and is treated as a copy.
Other agents, from other repositories
Plan
Software architect agent for designing implementation plans. Use this when you need to plan the implementation strategy for a task. Returns step-by-step plans, identifies critical files, and considers architectural trade-offs.
vision
Analyze images with task-aware visual reasoning.
code-reviewer
Dedicated code reviewer. Reads diffs/commits, reviews changed files, and returns a terse report of problems found. Prompt MUST specify scope: unstaged changes, a commit range, or since-branch-point. Read-only — no file edits.
ux-reviewer
Holistic UX/UI reviewer. Opens the app and evaluates overall design quality against best practices. Use after milestones or design-heavy work for a design critique. MUST run in foreground — MCP tools do not work in background.
ss-reviewer
Independent code reviewer for the specship review stage — one member of the opt-in review panel. Use to get fresh, context-free eyes on a working diff, optionally through a named lens (correctness, security, performance, contract-consistency). Reports findings only; it does not fix code, decide the verdict, or touch…
ss-researcher
External-fact search worker for the specship research stage. Use to run one query angle of a larger question and return verified, cited conclusions. One invocation per angle — it gathers and checks its own sources, and it neither picks the angles nor writes the report.