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/cliftonc/drizzle-cube/domaingit clone --depth 1 https://github.com/cliftonc/drizzle-cubeWrote this? Show the measurements
A badge for your README with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them.
[](https://agentmods.dev/agents/cliftonc/drizzle-cube/domain)What 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.00626 |
| Opus 5 | $0.00000 | $0.00313 |
| Sonnet 5 | $0.00000 | $0.00125 |
| Haiku 4.5 | $0.00000 | $0.00063 |
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.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domain Docs
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
This is a multi-context repo: a CONTEXT-MAP.md at the root points to one CONTEXT.md per area, mirroring the per-area CLAUDE.md files.
Before exploring, read these
CONTEXT-MAP.mdat the repo root — the index of per-area glossaries. Read theCONTEXT.mdfor the area(s) your task touches:src/server/CONTEXT.md— semantic layer / query pipeline (the foundational vocabulary)src/client/CONTEXT.md— dashboard / chart / analysis buildersrc/adapters/CONTEXT.md— HTTP + MCP transport (handler protocol, HttpPort, etc.)
docs/adr/— system-wide architecture decisions. Also checksrc/<area>/docs/adr/for area-specific decisions in the area you're working 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. The server and client glossaries are created lazily; the adapters glossary already exists.
File structure
/
├── CONTEXT-MAP.md ← index of per-area glossaries
├── docs/adr/ ← system-wide decisions (created lazily)
└── src/
├── server/
│ ├── CONTEXT.md ← (created lazily)
│ ├── CLAUDE.md
│ └── docs/adr/ ← area-specific decisions (created lazily)
├── client/
│ ├── CONTEXT.md ← (created lazily)
│ └── CLAUDE.md
└── adapters/
├── CONTEXT.md ← seeded
└── CLAUDE.md
Note: the per-area CLAUDE.md files are implementation/convention guides, not glossaries — the area's CONTEXT.md is the source of domain vocabulary.
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 the relevant area's CONTEXT.md. Don't drift to synonyms the glossary explicitly avoids.
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 · 49 lines · 0 tokens per session scan A 964b58a35cbb
domain is an agent published in the GitHub repository cliftonc/drizzle-cube (59 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 626 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
timing-analysis-agent
Analyzes real-time constraints, ISR latency, DMA transfer times, and LED protocol timing for embedded systems.
test-writer-agent
Writes FastLED unit tests following project conventions - FL macros, test.h patterns, file placement, and simplicity principles.
test-agent
Runs test suite and reports pass/fail status.
enterprise-backend-expert
Use this agent for Metabase Clojure backend work on enterprise platform features — serialization (export/import), audit logging, SCIM provisioning, multi-tenancy, database routing, dependency tracking, remote sync, premium features infrastructure, content translation, stale content detection, or support access grants.…
drivers-and-sync-backend-expert
Use this agent for Metabase Clojure backend work on database driver system, metadata sync, schema introspection, fingerprinting, field value caching, or driver-specific behavior. This includes adding or modifying database drivers, fixing JDBC metadata issues, debugging sync processes, working with the driver…
investigative-reporter-agent
Takes a story spark and produces a fully-scoped investigation package — editorial angle, source map, records requests, document analysis, verification checklist, libel-risk flags, and a draft lede — ready for an editor's desk.