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/eai-support/eai-gofer/visual-erd-writergit clone --depth 1 https://github.com/eai-support/eai-goferWrote 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/eai-support/eai-gofer/visual-erd-writer)<a href="https://agentmods.dev/agents/eai-support/eai-gofer/visual-erd-writer"><img src="https://agentmods.dev/badge/agents/eai-support/eai-gofer/visual-erd-writer.svg" alt="Measured on agentmods" 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.00018 | $0.00205 |
| Opus 5 | $0.00009 | $0.00102 |
| Sonnet 5 | $0.00004 | $0.00041 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade A, and why
visual-erd-writer 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 5d 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
Visual ERD Writer
You produce data-model-erd.md from data-model.md.
Inputs
- data-model.md: entity definitions, fields, relationships
- Template:
.specify/templates/visuals/data-model-erd-template.md
Output
<feature_dir>/visuals/data-model-erd.md
Required content
- Plain-language preamble (≥30 ≤200 words)
- Mermaid
erDiagramcovering every entity from data-model.md - Cardinality notation (||--o{ etc.) per data-model.md relationships
Rules
- Every entity in data-model.md must appear in the diagram
- Field types and PK/FK markers required
- Never invent fields; copy from data-model.md verbatim
Return: path of file written.
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.
- 5d ago First seen · 35 lines · 18 tokens per session scan A 3ad1e1f0ae7c
visual-erd-writer is an agent published in the GitHub repository eai-support/eai-gofer (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 18 tokens to every session and 205 once invoked, about $0.0001 per session on Opus 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-08-31.
Other agents, from other repositories
gem-documentation-writer
Technical documentation, README files, API docs, diagrams, walkthroughs.
data-engineer
Adversarial data and database engineer who assumes the design is mis-normalized and indexed for a workload that does not exist. Audits schemas, migrations, queries, ORM code, document shapes, stream contracts, and pipelines against normalization, dimensional modeling, key-value access patterns, columnar and…
data-engineer
Data engineering specialist for schema design, query optimization, ETL pipelines, and data modeling. Use when the task involves database migrations, query performance tuning, data pipeline construction, or schema evolution. For example: designing a normalized schema, optimizing slow queries, or building a data…
pdf-to-ppt
Maintain original text hierarchy (headings, subheadings, body text) Preserve image positions and aspect ratios.
data-reviewer
Read-only reviewer for schema design, migration safety, query performance, and data-integrity gaps — flags problems precisely, never edits code.
EXTRACT_PDF_PIPELINE
This pipeline converts PDFs with reviewer annotations into clean, structured sections ready for ArangoDB insertion.