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 skills add uniqbit-ag/mate-cli --skill mate-domain-modelinggit clone --depth 1 https://github.com/uniqbit-ag/mate-cliWrote 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/uniqbit-ag/mate-cli/mate-domain-modeling)<a href="https://agentmods.dev/skills/uniqbit-ag/mate-cli/mate-domain-modeling"><img src="https://agentmods.dev/badge/skills/uniqbit-ag/mate-cli/mate-domain-modeling/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/uniqbit-ag/mate-cli/mate-domain-modeling"><img src="https://agentmods.dev/badge/skills/uniqbit-ag/mate-cli/mate-domain-modeling.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00037 | $0.00754 |
| Opus 5.5 | $0.00015 | $0.00302 |
| Sonnet 5.5 | $0.00007 | $0.00151 |
| Haiku 4.5 | $0.00004 | $0.00075 |
Grade A, and why
mate-domain-modeling 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 22d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mate Domain Modeling
Actively sharpen project terminology and durable domain decisions. Reading a context for vocabulary is not enough: challenge fuzzy terms, test boundaries with concrete scenarios, and ask the user to confirm each proposed definition or decision.
Resolve scope first
- Identify the Companion Repository that owns the session and read its root
CONTEXT-MAP.mdbefore any domain analysis. This is the companion-wide index for shared contexts and repository-scoped context maps. - Resolve the primary Working Repository from its canonical Git remote or the explicit Mate repository attachment. Do not use a checkout basename as its identity.
- Convert the canonical external repository ID to its filesystem key only for
path lookup. For example,
acme/repomaps toacme_repo. Keep the canonical ID authoritative, and use the same normalized key everywhere; do not guess from a checkout name or silently accept a colliding key. - Read the repository-scoped map at
repos/<normalized-repository-id>/CONTEXT-MAP.md, when present. Resolve the repository-relative Area from that map. In a monorepo, the Area is the owning package root such aspackages/acme; in a non-monorepo it is the exact repository-relative path, such asdocsor.. - Select exactly one context-map entry matching the canonical repository ID and Area, then load only its mapped context file. Never apply another repository's context. Shared context is applicable only when the root map explicitly maps it to the current scope.
If the topic cannot be mapped to exactly one repository and Area, ask the user
to identify the scope. Do not guess, synthesize an Area, use N/A, or fall back
to a checkout name.
Model the domain
- Call out terms that conflict with the mapped glossary.
- Propose one canonical term when language is vague or overloaded, listing meaningful alternatives as avoided terms.
- Use concrete and edge-case scenarios to test relationships and boundaries.
- Compare claims about behavior with the relevant Working Repository code.
- Keep context entries to project-specific definitions, not implementation details.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 22d ago Changed · +17 tokens per session 722d0e5a972d
- 23d ago Changed · +3 lines e9b812c5b70f
- 1mo ago First seen · 69 lines · 20 tokens per session scan A 22f1d92b65ce
mate-domain-modeling is a skill published in the GitHub repository uniqbit-ag/mate-cli (12 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 754 once invoked, about $0.0001 per session on Opus 5.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-09-09.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…