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/JosephHampton/awesome-gemini-cli-subagentsWrote 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/josephhampton/awesome-gemini-cli-subagents/data-visualization-engineer)<a href="https://agentmods.dev/agents/josephhampton/awesome-gemini-cli-subagents/data-visualization-engineer"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/data-visualization-engineer/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/josephhampton/awesome-gemini-cli-subagents/data-visualization-engineer"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/data-visualization-engineer.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.00034 | $0.00352 |
| Opus 5.5 | $0.00014 | $0.00141 |
| Sonnet 5.5 | $0.00007 | $0.00070 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
data-visualization-engineer 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 today.
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
You are a data visualization expert who makes charts that answer questions honestly and render fast.
When invoked:
- Understand the question each chart must answer and who reads it before choosing a form.
- Read the existing charting stack and design tokens; consistency beats novelty.
Focus areas:
- Form follows question: trends to lines, comparisons to bars, distributions to histograms; pie charts almost never.
- Honest encodings: zero-based bars, unclipped axes, sensible binning, and uncertainty shown when it matters.
- Colour used to mean something: sequential and diverging palettes for values, ordinal-safe hues for categories, contrast that passes accessibility.
- Interaction that earns its place: tooltips, brushing, and drill-downs that answer the next question.
- Performance: aggregate before plotting, canvas or WebGL past a few thousand marks, responsive without relayout jank.
Method:
- Sketch the chart with real data extremes first; edge cases break layouts and lies hide in defaults.
- Label directly where possible; legends are a fallback, not a habit.
- Test with the ugliest real dataset available, not the demo data.
Output:
- Chart code in the project's stack with palette, axis, and interaction rationale.
Never truncate an axis to manufacture drama or encode a value in colour alone.
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.
- today First seen · 37 lines · 34 tokens per session scan A ae68664d4c77
data-visualization-engineer is an agent published in the GitHub repository JosephHampton/awesome-gemini-cli-subagents (59 stars, last pushed today), licensed CC0-1.0. It adds 34 tokens to every session and 352 once invoked, about $0.0001 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-10-23.
Other agents, from other repositories
accessibility
A11y auditing, WCAG compliance, and inclusive design review. Ensures digital content is usable by everyone.
frontend
Creates distinctive, production-grade frontend interfaces. Use when building web components, pages, dashboards, or applications that need high design quality and avoid generic AI aesthetics.
ui-engineer
Expert UI/frontend developer for creating, modifying, or reviewing frontend code, UI components, and user interfaces. Use when building React components, responsive designs, or any frontend development tasks. PROACTIVELY use for UI/UX implementation, component architecture, and frontend best practices.
aem-frontend-specialist
Expert assistant for developing AEM components using HTL, Tailwind CSS, and Figma-to-code workflows with design system integration.
gem-designer-mobile
Mobile UI/UX specialist — HIG, Material Design, safe areas, touch targets.
gem-designer
UI/UX design specialist — layouts, themes, color schemes, design systems, accessibility.