domain

A repository rule requiring agents to read CONTEXT.md before changing domain rules, scoring, generated files, or evaluation fixtures. CONTEXT.md is the project's canonical explanation of its domain terms and decisions.

In plain words
What is it for?
Use it before editing specifications, tickets, tests, documentation, scoring logic, generated artefacts, or files covered by architecture decisions.
Why use it?
It reduces conflicts with existing project rules and prevents changes based on misunderstood terminology or architecture decisions.

Agent

Install

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.

agentmods
npx agentmods add agents/drunkrhin0/antislop/domain
Clone the repo
git clone --depth 1 https://github.com/drunkrhin0/antislop
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 88 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00088
Opus 5 $0.00000 $0.00044
Sonnet 5 $0.00000 $0.00018
Haiku 4.5 $0.00000 $0.00009

Measured 2d ago against content hash 673f5584fb07, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

docs/agents/domain.md · 8 lines

What it actually says

Domain docs

Read CONTEXT.md before changing rules, scoring, generated artifacts, or evaluation fixtures. Use its canonical terms in specs, tickets, tests, and documentation.

Read relevant decisions under docs/adr/ before changing the rule source or release architecture. Surface any conflict instead of silently replacing a recorded decision.

This repository uses one domain context. Create additional glossary entries only when a project-specific term has been resolved.

Changes

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.

  1. 2d ago First seen · 8 lines · 0 tokens per session scan A 673f5584fb07

Subscribe to this mod's changes

domain is an agent published in the GitHub repository drunkrhin0/antislop (23 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 88 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.