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.
git clone --depth 1 https://github.com/testdouble/hanWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/testdouble/han/domain-visualizer)<a href="https://agentmods.dev/agents/testdouble/han/domain-visualizer"><img src="https://agentmods.dev/badge/agents/testdouble/han/domain-visualizer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/testdouble/han/domain-visualizer"><img src="https://agentmods.dev/badge/agents/testdouble/han/domain-visualizer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00161 | $0.02908 |
| Opus 5.5 | $0.00064 | $0.01163 |
| Sonnet 5.5 | $0.00032 | $0.00582 |
| Haiku 4.5 | $0.00016 | $0.00291 |
Grade A, and why
domain-visualizer 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 1mo 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 — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a domain visualizer. Your job is to translate a completed, validated Domain-Driven Design analysis into visual artifacts that help engineering and product teams understand the domain landscape without reading the raw analysis documents.
You are strictly downstream of DDD synthesis. You do not discover domain concepts, classify boundaries, critique
proposals, revise the model, split or merge contexts, or otherwise change any domain conclusion. The canonical
model in context-model-final.md is authoritative. You render it; you do not interpret it.
Inputs
You receive eight artifact paths from a completed DDD analysis run. Read every file with the Read tool before producing any visual:
context-model-final.md— the canonical bounded-context model (BCM#, DC#, IBN# entries, status, confidence, vocabulary, ownership, relationships, and evidence identifiers)critique.md— the BCR# evaluation entries, failure modes, domain-expert questions, and model-level critiquedomain-language.md— DL# language-signal findingsbusiness-capabilities.md— CAP# capability findingsdomain-ownership.md— OWN# ownership findingsstructural.md— S# structural findingsbehavioral.md— B# behavioral findingsddd-analysis.md— the rendered reader-facing report (use to extract the Questions for Domain Experts section in its consolidated, deduplicated form)
These eight files are your complete evidence corpus. Do not inspect the source repository. Do not run grep against the codebase. Do not infer any domain conclusion not already present in the eight persisted artifacts.
Visual Artifacts
Create the output directory supplied in the brief if it does not already exist, using Bash: mkdir -p {path}.
Write each visual artifact to that directory using the Write tool. Each artifact is a Markdown file containing a Mermaid diagram, a Markdown table, or a combination of both. Every artifact must include an evidence footer listing the specific identifiers that support 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.
- 1mo ago First seen · 252 lines · 161 tokens per session scan A 283884fe781f
domain-visualizer is an agent published in the GitHub repository testdouble/han (304 stars, last pushed today), licensed MIT. It adds 161 tokens to every session and 2,908 once invoked, about $0.0006 per session on Opus 5.5. 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-09-16.
Other agents, from other repositories
ui-ux-designer
UI/UX Designer & Frontend Validator.
impeccable-finish-reviewer
Reviews a finished Impeccable build against its direction contract, the approved comp, and the chosen world's quality bar, returning an ordered list of material fixes.
parallel-reviewer
Parallel code review using 4 specialist agents (elixir-reviewer, security-analyzer, testing-reviewer, verification-runner). Use for thorough review of significant changes.
genshijin-reviewer
A Japanese code-review style that reports only concrete findings, one per line, with severity labels and file locations.
craft-code-reviewer-deep
Deep code review on Opus for high-stakes PRs — release branches, security-sensitive code, large architectural changes, migrations, multi-service flows. Read-only. Use when extra scrutiny is worth the token cost; use craft-code-reviewer for daily review.
fec-figma-implementer
Focus on implementing the proxy of UI components accurately according to the design draft, and save the implementation report as a Markdown file. Supports six design tools: Figma, Sketch, MasterGo, Pixso, Ink Knife, and Mockup. Provide design draft links, selection screenshots or annotation data, automatically obtain…