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/vscarpenter/gsd-task-manager/domaingit clone --depth 1 https://github.com/vscarpenter/gsd-task-managerWhat 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.00386 |
| Opus 5 | $0.00000 | $0.00193 |
| Sonnet 5 | $0.00000 | $0.00077 |
| 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 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.
This is a copy
80% identical to domain — 32 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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, orCONTEXT-MAP.mdat the repo root if it exists — it points at oneCONTEXT.mdper context. Read each one relevant to the topic.docs/adr/— read ADRs that touch the area you're about to work in. In multi-context repos, also checksrc/<context>/docs/adr/for context-scoped decisions.
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-client-side-only-indexeddb.md
│ ├── 0002-pocketbase-cloud-sync.md
│ └── ... (12 ADRs)
└── src/
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.
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 /grill-with-docs).
Flag ADR conflicts
If your output contradicts an existing ADR, surface it explicitly rather than silently overriding:
Contradicts ADR-0007 (notification-system-design) — 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 · 38 lines · 0 tokens per session scan A 70ee2aee96c4
domain is an agent published in the GitHub repository vscarpenter/gsd-task-manager (24 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 386 tokens. A static security scan graded it A with 0 findings. It is 80% identical to domain, differing in 32 lines, and is treated as a copy.
Other agents, from other repositories
mcp-tool-developer
MCP tool developer agent for building S&P 500 MCP server tools.
ot-architect
Usar para decisiones de arquitectura de OpenTicket — límites del core framework-free (core/), diseño del AgentCommerceAdapter, nuevos rails, extracción del paquete OSS, o cualquier cambio que cruce core/ ↔ lib/ ↔ app/. Invocar ANTES de escribir código que toque core/adapter o ports.ts.
ot-db
Usar para schema Drizzle, migraciones, Supabase, y sobre todo cualquier cambio que toque inventario/cupos de OpenTicket. Invocar antes de modificar db/schema.ts o db/store.ts, y para operar la DB (push, seed, advisors de Supabase).
ot-devops
Usar para CI/CD, deploy a Vercel, variables de entorno, GitHub Actions, y configuración de Supabase/Stripe/Resend en producción para OpenTicket. Invocar para el primer deploy, para armar el workflow de CI, o cuando falle un build/deploy.
ot-frontend
Usar para la web humana de OpenTicket — landing dev-native estética CLI, ticker en vivo, página pública de evento, dashboard organizador, página de orden. Invocar para cualquier cambio de UI/UX en app/.
ot-payments
Usar para todo lo que toque Stripe en OpenTicket — Checkout Sessions, webhooks, idempotencia, reembolsos, expiración de reservas, o bugs de doble emisión/doble cobro. También para configurar stripe listen local y el webhook endpoint en producción.