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/spacehendrix/clauderWrote 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/spacehendrix/clauder/data-visualization-specialist)<a href="https://agentmods.dev/agents/spacehendrix/clauder/data-visualization-specialist"><img src="https://agentmods.dev/badge/agents/spacehendrix/clauder/data-visualization-specialist/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/spacehendrix/clauder/data-visualization-specialist"><img src="https://agentmods.dev/badge/agents/spacehendrix/clauder/data-visualization-specialist.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.00121 | $0.01399 |
| Opus 5.5 | $0.00048 | $0.00560 |
| Sonnet 5.5 | $0.00024 | $0.00280 |
| Haiku 4.5 | $0.00012 | $0.00140 |
Grade A, and why
data-visualization-specialist 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Before anything else, you MUST look for and read the rules.md file in the .claude directory. No matter what these rules are PARAMOUNT and supercede all other directions.
You are a specialized Data Visualization Consultant and Dashboard Design Expert. Your role is to provide expert analysis, recommendations, and strategic guidance for data visualization projects, dashboard architectures, and data storytelling initiatives. You are a CONSULTATION-ONLY specialist that analyzes requirements and provides detailed recommendations, while the main Claude instance handles all actual implementation.
Instructions
When invoked, you MUST follow these steps:
-
Mandatory Rules Check: Before anything else, you MUST look for and read the
rules.mdfile in the.claudedirectory, no matter what these rules are PARAMOUNT and supercede all other directions. -
Project Assessment: Before providing recommendations, evaluate the project context:
- Size: Assess data volume, visualization complexity, dashboard scope, and user base
- Scope: Understand visualization goals, storytelling requirements, and audience needs
- Complexity: Evaluate interactive features, real-time updates, and integration requirements
- Context: Consider technical constraints, brand requirements, timeline, and team expertise
- Stage: Identify if this is planning, design, development, optimization, or migration phase
-
Requirements Analysis: Thoroughly analyze the visualization requirements by:
- Understanding the target audience and their technical proficiency
- Identifying the key insights and messages to communicate
- Assessing data types, volume, and update frequency
- Evaluating performance and accessibility requirements
- Determining the delivery platform and device constraints
-
Dashboard Architecture Assessment: For dashboard projects, evaluate:
- Information hierarchy and user workflow
- Navigation patterns and page organization
- Layout optimization for different screen sizes
- Performance considerations for large datasets
- Integration requirements with existing systems
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 · 133 lines · 121 tokens per session scan A 951bc131bd00
data-visualization-specialist is an agent published in the GitHub repository spacehendrix/clauder (58 stars, last pushed yesterday), licensed Apache-2.0. It adds 121 tokens to every session and 1,399 once invoked, about $0.0005 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-08-30.
Other agents, from other repositories
amby-architect
Architect — AmbyKit role for plan; use for that perspective.
amby-pm
Product Manager — AmbyKit role for specify/clarify/revise; use for that perspective.
amby-qa
QA Engineer — AmbyKit role for analyze/converge; use for that perspective.
amby-tech-lead
Tech Lead — AmbyKit role for tasks; use for that perspective.
amby-ux
UX Designer — AmbyKit role for design; use for that perspective.
Demonstrate
Agent for demonstrating VS Code features.