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/spiritledsoftware/caplets/domaingit clone --depth 1 https://github.com/spiritledsoftware/capletsWhat 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.00382 |
| Opus 5 | $0.00000 | $0.00191 |
| Sonnet 5 | $0.00000 | $0.00076 |
| Haiku 4.5 | $0.00000 | $0.00038 |
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 the engineering skills should consume this repo's domain documentation when exploring the codebase.
Layout
This is a single-context repo.
- Read root
CONTEXT.mdfor Caplets product vocabulary and domain language. - Read relevant ADRs in
docs/adr/before changing areas covered by an architectural decision. - If a future
CONTEXT-MAP.mdappears, treat that as a signal that the repo has moved to a multi-context layout and update this file.
Before exploring, read these
CONTEXT.mdat the repo root.docs/adr/entries that touch the area you're about to work in.STRATEGY.mdwhen deciding whether proposed work fits the current product direction.CONCEPTS.mdwhen orienting to shared project vocabulary.docs/solutions/when implementing, debugging, or making decisions in an area with documented prior solutions.
If any optional file does not exist in a checkout, proceed silently. Do not suggest creating it upfront; producer workflows create or update these docs when terms, strategy, or decisions are actually resolved.
Use the glossary's vocabulary
When your output names a domain concept in an issue title, refactor proposal, hypothesis, test name, or implementation plan, use the terms defined in CONTEXT.md and CONCEPTS.md. Do not drift to synonyms those docs explicitly avoid.
If the concept you need is not in the glossary yet, either reconsider whether you are inventing language the project does not use, or note the gap for a vocabulary/documentation pass.
Flag ADR conflicts
If your output contradicts an existing ADR, surface it explicitly rather than silently overriding:
Contradicts ADR-0001 (Code Mode default exposure), 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 · 34 lines · 0 tokens per session scan A d6df4d055ee3
domain is an agent published in the GitHub repository spiritledsoftware/caplets (14 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 382 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
test-runner
Runs tests in the api-gateway Maven reactor — full/module unit runs, isolating a single core test class, or a single distribution/tutorial example test. Use this whenever tests need to be run, checked, or verified after a change, since naive -Dtest/-Dit.test invocations silently run (or skip) the wrong thing in this…
backend-system-architect
Backend architect: REST/GraphQL APIs, database schemas, microservice boundaries, distributed systems, clean architecture.
inbox-searcher
Email inbox search specialist, takes in appropriate context for the email and a goal of what to search for. Return the answer to the question.
api-designer
API design, documentation, and contract specialist.
researcher
Reads files and grep'd content, no writes.
det
Deterministic-fixture subagent.