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/enihcam/opencode-webmcp/domaingit clone --depth 1 https://github.com/enihcam/opencode-webmcpWhat 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.00389 |
| Opus 5 | $0.00000 | $0.00195 |
| Sonnet 5 | $0.00000 | $0.00078 |
| Haiku 4.5 | $0.00000 | $0.00039 |
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 yesterday.
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 engineering skills should consume this repo's domain documentation when exploring the codebase.
Before exploring, read these
CONTEXT.mdat the repo root — describes the project, domain terminology, architecture at a glance, key invariants, and dependency/toolchain info.docs/adr/— read ADRs that touch the area you're about to work in.
If any of these files don't exist, proceed silently. Don't flag their absence; don't suggest creating them upfront. The producer skill (/grill-with-docs) creates them lazily when terms or decisions actually get resolved.
File structure
Single-context repo:
/
├── CONTEXT.md
├── docs/adr/
│ ├── 0001-mcp-bridge-architecture.md
├── docs/agents/
│ ├── AGENT-BRIEF.md
│ ├── domain.md
│ ├── issue-tracker.md
│ └── triage-labels.md
├── lib/
│ └── config.mjs
├── server.js
└── test/
└── unit.mjs
No CONTEXT-MAP.md — this is a single-module project.
Use the glossary's vocabulary
When your output names a domain concept, use the term as defined in CONTEXT.md. Don't drift to synonyms the glossary explicitly avoids.
Key terms: MCP, WebMCP, bridge-native tool, page-discovered tool, declarative tool, imperative tool, monkey-patch, dispatch table, tab, ring buffer.
Flag ADR conflicts
If your output contradicts an existing ADR, surface it explicitly rather than silently overriding:
Contradicts ADR-0001 (section 6 — tab management auto-recovery) — 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.
- yesterday First seen · 46 lines · 0 tokens per session scan A 8645e71547bb
domain is an agent published in the GitHub repository enihcam/opencode-webmcp (1 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 389 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
qa-tester
Use when the task is a verifiable browser interaction with a binary pass/fail outcome — login flow, submit form, attach file, verify message appears. Returns a verdict + evidence. Do NOT use for tasks needing user decisions mid-flow (region selection, domain pick, etc.).
Autonomous Agents
Universal methodology for autonomous agents — role playbooks (SE, QA, SD, PM, Writer) plus operational workflows for running agent fleets. App-agnostic: works with any web application or codebase.
architect-gen
You are the Architecture Generator agent for Founder Mode — Phase 2.
scorer
Simulates Phoenix algorithm scoring on X post drafts. Returns detailed signal analysis and composite scores.
evaluator-innovation
You are the Innovation Scout subagent for the Architect evaluation system.
evaluator-impact
You are the Impact Evaluator subagent for the Architect evaluation system.