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/yuqie6/productflow/domaingit clone --depth 1 https://github.com/yuqie6/ProductFlowWhat 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.00251 |
| Opus 5 | $0.00000 | $0.00125 |
| Sonnet 5 | $0.00000 | $0.00050 |
| Haiku 4.5 | $0.00000 | $0.00025 |
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 the engineering skills should consume this repo's domain documentation when exploring the codebase.
Layout
This repo uses a single-context domain documentation layout.
Expected files, when they exist:
CONTEXT.mdat the repo rootdocs/adr/for architectural decision records
These files do not need to exist before a skill can run. If they are absent, proceed silently. Producer skills such as /grill-with-docs can create them later when real terminology or decisions need to be recorded.
Before exploring, read these
CONTEXT.mdat the repo root, if it exists.- ADRs under
docs/adr/that touch the area about to be changed, if any exist.
Use the glossary's vocabulary
When output names a domain concept in an issue title, refactor proposal, hypothesis, or test name, use the term as defined in CONTEXT.md.
If the concept is missing from the glossary, either reconsider whether that term belongs in the project language, or note it as a gap for /grill-with-docs.
Flag ADR conflicts
If output contradicts an existing ADR, surface it explicitly instead of silently overriding the decision.
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 · 30 lines · 0 tokens per session scan A 07e7aa5a9c33
domain is an agent published in the GitHub repository yuqie6/ProductFlow (301 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 251 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
domain
How engineering skills consume this repository’s domain documentation.
issue-tracker
Issues and specs for this repo live as GitHub issues. Use the gh CLI for all operations.
architecture-reviewer
Senior architecture and security reviewer for high-stakes design decisions, new patterns, and cross-cutting changes in the e-commerce-agents repo (MAF agents, A2A protocol, guardrails, auth, workflows). Use when reviewing system design, agent/tool boundaries, security posture, or any non-trivial structural change …
planner
Senior implementation planner and design-thinking partner for non-trivial features, refactors, and architecture decisions in the e-commerce-agents repo. Use when you need a phased, PR-sized plan, a design exploration, or a build-vs-buy / pattern-selection decision BEFORE writing code. Produces plans, not code.
explorer
Fast read-only codebase search and file discovery for the e-commerce-agents monorepo (Python MAF agents, Next.js web, .NET port). Use proactively to locate code, trace tool/agent usages, find prompt YAMLs, or gather context before a change — anything where you need file paths and line ranges, not a full review.
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.