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/darecstowell/scratchboard/domaingit clone --depth 1 https://github.com/darecstowell/scratchboardWhat 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.00380 |
| Opus 5 | $0.00000 | $0.00190 |
| Sonnet 5 | $0.00000 | $0.00076 |
| Haiku 4.5 | $0.00000 | $0.00038 |
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.
What it actually says
Domain docs
How the engineering skills read this repo's domain documentation before they explore the code.
Before exploring, read these
CONTEXT.mdat the repo root.docs/adr/for the decisions that touch the area you are about to work in.
If a file does not exist, continue silently. Do not report that it is missing, and do not
propose to create it up front. The /domain-modeling skill, reached through /grill-with-docs
and /improve-codebase-architecture, writes these files when a term or a decision is actually
resolved.
AGENTS.md holds the rules of this repo and is not a domain doc, but read it first. It states
the constraints that a change must keep.
File structure
This repo is single-context:
/
├── AGENTS.md
├── CONTEXT.md
├── docs/adr/
│ ├── 0001-zero-dependencies.md
│ └── 0002-config-names-every-lane.md
└── src/
Use the glossary's vocabulary
When your output names a domain concept, in a ticket title, a refactor proposal, a hypothesis,
or a test name, use the term as CONTEXT.md defines it. Do not drift to a synonym the glossary
avoids.
If the concept is not in the glossary, that is a signal. Either you invent language the project
does not use, so think again, or there is a real gap, so note it for /domain-modeling.
Flag ADR conflicts
If your output contradicts an ADR, say so instead of overriding it quietly:
Contradicts ADR-0001 (zero dependencies), but worth reopening because...
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.
- 2d ago First seen · 46 lines · 0 tokens per session scan A 686e65a22321
domain is an agent published in the GitHub repository darecstowell/scratchboard (6 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 380 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
basic-agents
A basic agent uses a predefined strategy with a simple execution flow that works for most common use cases. It accepts a string input (a question, request, or task description) and sends this input to the configured LLM. The LLM may decide to call provided tools. The agent will execute the tools and send the results…
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
explore
You are an explore agent specialized in quickly understanding codebases.
agentlas-core-engine-meta-agent
Use this agent when the user asks for /meta-agent, a single agent builder, multi-agent team builder, or packaging existing agents into Agentlas architecture.
nw-nwave-buddy
Use for any nWave question — methodology, project navigation, command help, wave status, migration, and troubleshooting. The first agent to consult when unsure about anything in nWave.
implementation-subagent
Implements missing requirements for a task from the implementation plan.