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/govza/mlo-mcp/domaingit clone --depth 1 https://github.com/govza/mlo-mcpWrote 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/agents/govza/mlo-mcp/domain)<a href="https://agentmods.dev/agents/govza/mlo-mcp/domain"><img src="https://agentmods.dev/badge/agents/govza/mlo-mcp/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.00000 | $0.00610 |
| Opus 5 | $0.00000 | $0.00305 |
| Sonnet 5 | $0.00000 | $0.00122 |
| Haiku 4.5 | $0.00000 | $0.00061 |
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 — 44 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 single-context repo: one CONTEXT.md at the repo root, backed by an existing body of reference docs under docs/.
Before exploring, read these
CONTEXT.mdat the repo root — the glossary and entry point. It defines the ubiquitous language and points into the deep reference docs.- The reference docs it links —
docs/README.mdindexes them:docs/tools.md(tool semantics),docs/server-architecture.md(server internals),docs/mcp-cloud.md(the sync endpoint), anddocs/mlo/(reverse-engineered MLO formats and protocol). Read the ones relevant to the area you're working in; they are the authoritative domain documentation, not just background. docs/adr/— read ADRs that touch the area you're about to work in.
If docs/adr/ (or a linked doc) doesn't exist, proceed silently. Don't flag the absence; don't suggest creating it upfront. The /domain-modeling skill (reached via /grill-with-docs and /improve-codebase-architecture) creates ADRs lazily when decisions actually get resolved.
Decisions
Established decisions predating this setup are recorded in prose inside the reference docs (e.g. "writes never touch the data file" in docs/tools.md; "switching sync endpoints is not a reconnect" in docs/mlo/cloud-sync.md). Leave them there — don't retro-extract ADRs. New decisions go to docs/adr/ as numbered records.
File structure
/
├── CONTEXT.md ← glossary / entry point
├── docs/
│ ├── README.md ← index of the reference docs
│ ├── adr/ ← new decisions (created lazily)
│ ├── agents/ ← these convention files
│ ├── tools.md, server-architecture.md, mcp-cloud.md
│ └── mlo/ ← reverse-engineered MLO formats & protocol
└── mcp-server/
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.
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 · 44 lines · 0 tokens per session scan A 433a5e15f770
domain is an agent published in the GitHub repository govza/mlo-mcp (1 stars, last pushed 14d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 610 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.