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 skills/gideondk/strata/domainnpx skills add gideondk/strata --skill domaingit clone --depth 1 https://github.com/gideondk/strataWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/gideondk/strata/domain)<a href="https://agentmods.dev/skills/gideondk/strata/domain"><img src="https://agentmods.dev/badge/skills/gideondk/strata/domain.svg" alt="Measured on agentmods" height="20"></a>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.00076 | $0.00462 |
| Opus 5 | $0.00038 | $0.00231 |
| Sonnet 5 | $0.00015 | $0.00092 |
| Haiku 4.5 | $0.00008 | $0.00046 |
Grade A, and why
strata: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 4d 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.
What it actually says
strata:domain
Domain notes are the long-lived part of team memory. They define vocabulary (what does "Tenant" mean here?), encode invariants (an Order always belongs to exactly one Customer), and pin conventions (event names use past tense).
Rules
- One concept per file. Split rather than expand.
- Filename in kebab-case:
medication-administration-windows.md. - Frontmatter required (see
templates/domain.md). - Use Obsidian-style
[[wikilinks]]to cross-reference other domain notes and ADRs by filename without extension.
How
User runs /strata:domain <concept-name>. You:
- Recall first. Call
recall(query="<concept>", scope="domain", layer=1)to find an existing note for this concept, possibly under a different slug. If one exists, UPDATE it instead of forking a second definition; if two notes would conflict, reconcile through/strata:correct. Only create a new note when recall shows nothing close. - If new, write the body using
templates/domain.mdas the shape. - Save it directly to
<vault>/<repo>/domain/<slug>.mdvia the standard Write tool. Use the absolute path printed by/strata:initor read it fromstrata.memory_statusvia MCP.
After saving, regenerate the index so the MCP search picks it up:
"${CLAUDE_PLUGIN_ROOT}/bin/strata" reindex
Cross-repo (shared) domain notes
For vocabulary that applies across multiple repos (e.g. a company-wide
Convention), put the note at <vault>/_shared/domain/<slug>.md. The MCP
Search includes shared notes by default.
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.
- 4d ago First seen · 45 lines · 76 tokens per session scan A e8417f259500
strata:domain is a skill published in the GitHub repository gideondk/strata (5 stars, last pushed 1mo ago), licensed MPL-2.0. It adds 76 tokens to every session and 462 once invoked, about $0.0004 per session on Opus 5. 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-31.
Other skills, from other repositories
my-wiki
Manage local OKF-compatible Markdown My Wiki vaults with an AI agent. Use for capturing webpages, PDFs, Office documents, notes, images, folders, and ZIP bundles as References; maintaining Reference-to-Concept evidence links; searching or answering from a vault; checking or repairing vault health; switching among…
kb
Set up, evolve, or operate a hraness/kb local-first Markdown knowledge base for coding-agent memory. Use when a user asks to design KB conventions or a recurring KB ritual; search or query a KB or Obsidian vault; load or recover repository context, plans, decisions, concepts, backlinks, semantic search, or Git…
memory-forest
Build, validate, index, and query a private local Memory Forest with provenance-aware layers, pointer-first search, and validated root-first retrieval. Use when creating a new forest, checking an existing forest's structure, building its local SQLite index, or retrieving bounded memory trails without exposing full…
memory-forest-retrieve
Integrate a mandatory, metadata-only Memory Forest consultation gate before an agent responds to each non-empty user-authored text turn.
beads
Use when working in a repository that uses bd or Beads for durable project task tracking, issue dependencies, blocker management, multi-session handoff, or shared work memory. Trigger when the user asks to find ready work, claim or close tasks, create follow-up work, inspect blockers, recover project context, or…
wiki-sync
Synthesize a single source note into the vault's wiki/ folder — read the source, find or create the right wiki entry, write it back with proper frontmatter and source links. Used by Lumina's background wiki manager when a note changes.