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/vod-studio/violet/domaingit clone --depth 1 https://github.com/VOD-Studio/violetWhat 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.00543 |
| Opus 5 | $0.00000 | $0.00271 |
| Sonnet 5 | $0.00000 | $0.00109 |
| Haiku 4.5 | $0.00000 | $0.00054 |
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.
How it starts
The opening of the file, as written. The whole thing — 43 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.
Before exploring, read these
CONTEXT.mdat the repo root — single-context layout; holds the glossary for all domains (authentication, article navigation/authorship, announcement presentation) in sectioned form.docs/adr/— read ADRs that touch the area you're about to work in. This repo has auth-series ADRs (0001/0002/0003/auth-architecture-selection).
If any of these files don't exist, proceed silently. Don't flag their absence; don't suggest creating them upfront. The /domain-modeling skill (reached via /grill-with-docs and /improve-codebase-architecture) creates them lazily when terms or decisions actually get resolved.
File structure
Single-context repo:
/
├── CONTEXT.md # glossary, all domains in sections
├── docs/
│ ├── adr/ # auth-series ADRs
│ ├── prd/ # PRDs (numbered)
│ └── issues/ # archived local-markdown issues (historical)
├── api/ # blog backend (Chi + DDD)
└── web/ # blog frontend (React + Vite)
Note: 网易云音乐能力服务（原 mimo-music，现 kite）已迁移至独立仓库 github.com/VOD-Studio/kite，本仓库不再保留其代码与域语言。api/internal/infrastructure/music/ 保留 KiteProvider stub 作为 blog 文章音乐嵌入的服务消费方。
Use the glossary's vocabulary
When your output names a domain concept (in an issue title, a refactor proposal, a hypothesis, a test name), use the term as defined in CONTEXT.md. Don't drift to synonyms the glossary explicitly avoids.
Notable vocabulary to respect:
- Auth: opaque Session ID (not "access token"), Session Envelope, 命门不变量
If the concept you need isn't in the glossary yet, that's a signal — either you're inventing language the project doesn't use (reconsider) or there's a real gap (note it for /domain-modeling).
Flag ADR conflicts
If your output contradicts an existing ADR, surface it explicitly rather than silently overriding:
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 · 43 lines · 0 tokens per session scan A bf48192d47d2
domain is an agent published in the GitHub repository VOD-Studio/violet (2 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 543 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
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.