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/clay-good/openlore/domaingit clone --depth 1 https://github.com/clay-good/OpenLoreWhat 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.00635 |
| Opus 5 | $0.00000 | $0.00318 |
| Sonnet 5 | $0.00000 | $0.00127 |
| Haiku 4.5 | $0.00000 | $0.00064 |
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.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domain Docs
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
Layout: single-context. One context for the whole repository (a single TypeScript package), with one ADR corpus.
Before exploring, read these
CONTEXT.mdat the repo root — does not exist yet. Proceed silently; don't flag its absence and don't scaffold one upfront./grill-with-docscreates it lazily, once terms actually get resolved.- ADRs:
openspec/decisions/adr-*.md— notdocs/adr/. This repo's ADRs are written by OpenLore's ownrecord_decisiontool and numberedadr-NNNN-<slug>.md. Read the ones touching the area you're about to work in.
There is no CONTEXT-MAP.md and no per-context src/<context>/docs/adr/ — a lookup
there is expected to find nothing.
File structure
/
├── CONTEXT.md ← not present yet
├── openspec/
│ ├── decisions/ ← THE ADR corpus (adr-0001-….md …)
│ ├── specs/<domain>/spec.md ← the spec corpus, one directory per domain
│ └── changes/<change-id>/ ← in-flight change proposals
└── src/
Specs are part of the domain record here
Beyond ADRs, openspec/specs/<domain>/spec.md carries the requirements and the
domain vocabulary in force. openspec/specs/overview/spec.md is the entry point (domain
table + technical stack). When a skill asks for "the project's domain language" and
CONTEXT.md is absent, read the overview spec plus the spec for the domain you're
touching, rather than inferring vocabulary from code identifiers.
Structural questions ("who calls this", "what's the blast radius", "which spec covers
this symbol") are answered by the OpenLore MCP tools described in the root CLAUDE.md —
prefer those over grepping.
Use the established vocabulary
When your output names a domain concept (an issue title, a refactor proposal, a hypothesis, a test name), use the term as the specs define it. Don't drift to synonyms.
If the concept isn't in the specs yet, that's a signal — either you're inventing language the project doesn't use (reconsider), or there's a real gap (note it).
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 · 63 lines · 0 tokens per session scan A 8e91160f1a21
domain is an agent published in the GitHub repository clay-good/OpenLore (290 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 635 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.
Other agents, from other repositories
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
ap-verifier
L3 independent G6 verifier - proves behavior with real before/after runs, regression checks, adversarial inputs, and >=95% changed-line coverage.
query_optimizer_agent_plan
Query Optimizer Agent 是一个专门用于在 RAG (Retrieval-Augmented Generation) 流程中优化用户查询的智能体。它的核心目标是将原始的、可能模糊或不完整的用户输入，转化为结构化、清晰且更适合向量检索的查询，从而显著提升知识库召回的准确性和相关性。.
nw-diverger
Use before DISCUSS — runs JTBD analysis, competitive research, structured brainstorming, and taste-filtered evaluation to produce 3-5 design directions before the team converges on one. Use when the team has a validated problem but hasn't chosen a solution approach.
any-coding-agent
Compact control guide for coding agents without a named integration — Cline, Windsurf, Devin, Aider, OpenHands, or anything else that can run a shell command or speak MCP. The named guides (codex.md, claude-code.md, cursor.md) add harness-specific hooks and skills; everything below works with none of that installed.
designer
Visual designer, UX/UI agent, and Open Design handoff producer.