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/pacnpal/mcpelevator/domaingit clone --depth 1 https://github.com/pacnpal/mcpelevatorWhat 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.00290 |
| Opus 5 | $0.00000 | $0.00145 |
| Sonnet 5 | $0.00000 | $0.00058 |
| Haiku 4.5 | $0.00000 | $0.00029 |
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 should consume this repo's domain documentation when exploring the codebase.
Before exploring, read these
CONTEXT.mdat the repo root.docs/adr/: read ADRs that touch the area you're about to work in.
If either path doesn't exist, proceed silently. Don't flag its absence or suggest creating it upfront. The /domain-modeling skill, reached through /grill-with-docs and /improve-codebase-architecture, creates domain docs only when terms or decisions get resolved.
File structure
This repo uses a single-context layout:
/
|-- CONTEXT.md
|-- docs/
| `-- adr/
|-- backend/
`-- frontend/
Use the glossary's vocabulary
When your output names a domain concept in an issue title, refactor proposal, hypothesis, or test name, use the term defined in CONTEXT.md. Don't drift to synonyms the glossary explicitly avoids.
If the concept isn't in the glossary, either the proposed language doesn't belong in the project or the glossary has a real gap. Reconsider it or note it for /domain-modeling.
Flag ADR conflicts
If your output contradicts an existing ADR, surface it instead of silently overriding it:
Contradicts ADR-0007 (event-sourced orders), 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 · 36 lines · 0 tokens per session scan A c39452c5d254
domain is an agent published in the GitHub repository pacnpal/mcpelevator (5 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 290 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
skills-management
Skill 是一个可复用的能力包，通常包含一个 SKILL.md、提示词、参考资料和可选脚本。智能体先看到 Skill 的描述，再按需要读取 SKILL.md；Skill 声明的工具和 MCP 依赖会随激活状态加入模型请求。.
agent-evaluation
智能体评估用 Langfuse Dataset 保存一组固定任务，再让 Yuxi 按真实的 AgentRun、worker 和工具链路逐条执行。它适合比较一个智能体在研究、编程、文件处理或多步骤任务上的表现。.
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
txtify-qa
QA gatekeeper for Txtify. Use to run the full verification ladder on the current tree and report evidence — before merging, releasing, or when asked "does everything still work?".
piper-reviewer
Reviews Piper changes against this project's own rules — the pre-1.0 break-freely policy, the layering constraint, the no-cgo requirement, and the fixed status strings. Use when reviewing a diff, a PR, or a branch in this repo, in preference to a generic code review.
2026-04-20-relay-handoff
Demo Agent Ada found that Relay parser failures were caused by missing fenced-code terminators in synthetic notes.