Repository guidance that tells contributors which architecture and research documents to read before exploring or changing parts of the codebase. It also maps the main Rust crates and documentation areas.

For orienting developers and agents before work on the general architecture, semantic layer, calibration, or Rust port.

It reduces the chance of making changes that conflict with the project's architecture, research decisions, or porting requirements.

domain — Agent by get-tmonier

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/get-tmonier/argot/domain

Clone the repo

git clone --depth 1 https://github.com/get-tmonier/argot

Or install argot, the plugin that ships this one along with the rest of its 7 skills, 5 agents, 1 hook, 1 MCP server.

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 401 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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00401
Opus 5	$0.00000	$0.00200
Sonnet 5	$0.00000	$0.00080
Haiku 4.5	$0.00000	$0.00040

Measured 3d ago against content hash 3a25cd04eb8b, 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 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.

docs/agents/domain.md · 38 lines

What it actually says

Domain Docs

Before exploring, read these

CLAUDE.md — the current single-binary architecture map and crate layout.
CLAUDE.md — Architecture section: the crate/module layout.
docs/research/ — serves as ADR for this repo. Read entries that touch the area you're about to work in.
docs/rust-port/ — the Rust port's parity record + cutover plan.
Touching the semantic layer (crates/argot-rules-semantic/) — read docs/agents/semantic-contract.md (self-calibration invariants) and the "Semantic layer" section of CLAUDE.md first.
Touching calibration — docs/agents/calibration-contract.md is binding.

If any of these files don't exist, proceed silently. Don't flag their absence upfront.

Layout

/
├── CLAUDE.md               ← architecture + conventions
├── docs/research/          ← system-wide decisions (ADR)
├── docs/rust-port/         ← port parity record
└── crates/
    ├── argot-lang/         ← language substrate and adapters
    ├── argot-engine/       ← rule-blind engine
    ├── argot-rules-*/      ← independent detector slices
    ├── argot-core/         ← facade + composition root
    └── argot-cli/          ← clap CLI → `argot` binary

Use consistent vocabulary

When your output names a domain concept, use the term defined in CLAUDE.md. Don't drift to synonyms.

Flag research conflicts

If your output contradicts a finding in docs/research/, surface it explicitly rather than silently overriding:

Contradicts research/04-import-graph-breakthrough.md — but worth revisiting because…

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.

3d ago First seen · 38 lines · 0 tokens per session scan A 3a25cd04eb8b

Subscribe to this mod's changes

domain is an agent published in the GitHub repository get-tmonier/argot (48 stars, last pushed 20d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 401 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.

ci cli code-quality coding-style developer-tools

harness-doctor

Check a claudeconf-generated harness against its RECORDED constitution profile — advisory, evidence-driven, read-only. Use when the user asks to check, diagnose, or "doctor" their harness, verify pins/wiring/drift, see whether branch protection matches the enforcement checklist, or whether a profile upgrade is…

nikolaypaskov/claudeconf-plugin · 98 tokens

eval-curator

Authors and maintains the brooks-lint eval suite in evals/evals.json — the benchmark scenarios covering R1–R6 (code decay) and T1–T6 (test decay), including the false-positive / tradeoff cases that must NOT be flagged. Ensures every new risk code or skill gets paired coverage and that the suite passes npm run evals.…

hyhmrright/brooks-lint · 97 tokens

domain