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 skills/blakefeiza/vizwright/chart-xml-librarynpx skills add blakefeiza/vizwright --skill chart-xml-librarygit clone --depth 1 https://github.com/blakefeiza/vizwrightWrote 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/skills/blakefeiza/vizwright/chart-xml-library)<a href="https://agentmods.dev/skills/blakefeiza/vizwright/chart-xml-library"><img src="https://agentmods.dev/badge/skills/blakefeiza/vizwright/chart-xml-library.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 | $0.00066 | $0.07550 |
| Opus 5 | $0.00033 | $0.03775 |
| Sonnet 5 | $0.00013 | $0.01510 |
| Haiku 4.5 | $0.00007 | $0.00755 |
Grade A, and why
chart-xml-library 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 4d 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 — 571 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chart XML Library (mined from VOTD winners)
Each recipe gives the <mark>, <rows>, <cols>, and <encodings> deltas.
Boilerplate (datasource-dependencies, style, panes wrapper) is in the
twb-authoring skill. [ds] = your datasource name, e.g. [federated.superstore].
Raw examples: knowledge/xml-patterns/<chart-type>/*.xml.
Chart selection guide, organized by question intent (FT Visual Vocabulary).
Every recipe below is RENDER-VERIFIED via the specimen book
(tools/build_specimen.py → output/chart-specimen.twbx — regenerate and
publish it after changing any recipe).
| Intent | Question shape | Chart | Recipe |
|---|---|---|---|
| Magnitude | "How much overall?" | BAN / KPI card | 1 |
| Ranking | "Compare categories" | Horizontal bar, sorted | 2 |
| Ranking | "Compare, minimal ink" | Lollipop / dot plot | 9 |
| Change over time | "Trend?" | Line (month-truncated) | 3 |
| Change over time | "Trend + magnitude" | Area | 4 |
| Change over time | "Trend in a card" | Sparkline | 14 |
| Change over time | "Then vs now (2 periods)" | Slope | 16 |
| Deviation | "Before vs after / A vs B" | Dumbbell | 10 |
| Deviation | "Actual vs target" | Bullet | 11 |
| Correlation | "Two measures related?" | Scatter | 5 |
| Spatial | "Where geographically?" | Filled map | 6 |
| Magnitude | "Two dims × measure" | Heatmap / highlight table | 7 |
| Part-to-whole | "Composition (per category)" | Stacked bar | 15 |
| Ranking | "Compare within groups" | Grouped bar (nested dims) | 15 |
| Part-to-whole | "Share of total, 2-3 parts ONLY" | Pie | 13 |
| Part-to-whole | "Many parts, hierarchy" | Treemap | 18 |
| Flow | "Stage drop-off" | Funnel | 12 |
| Distribution | "Value spread" | Histogram (calc bins) | 17 |
| — | "Exact values / detail" | Text table (sparingly) | 8 |
Not yet in the library (need table-calc grammar; do not improvise): waterfall, bump chart, box plot, 100%-stacked via percent-of-total.
1. BAN / KPI card
Text mark, measure on Text shelf, empty rows/cols. One BAN per sheet.
<panes><pane>
<view><breakdown value='auto' /></view>
<mark class='Text' />
<encodings><text column='[ds].[sum:Sales:qk]' /></encodings>
</pane></panes>
<rows></rows>
<cols></cols>
Format the number big via pane style:
<style-rule element='mark'>
<format attr='font-size' value='28' />
<format attr='font-weight' value='bold' />
<format attr='color' value='#333333' />
</style-rule>
VOTD pattern: BAN row = 3–4 cards across the top, each with a small caption (worksheet title, 9–10pt grey) above the number.
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.
- 4d ago First seen · 571 lines · 66 tokens per session scan A b12db098c2d3
chart-xml-library is a skill published in the GitHub repository blakefeiza/vizwright (3 stars, last pushed 1mo ago), licensed MIT. It adds 66 tokens to every session and 7,550 once invoked, about $0.0003 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 skills, from other repositories
dashboard-design
Use this skill first when the user wants to design or plan a dashboard, especially Vizro dashboards. Enforces a 3-step workflow (requirements, layout, visualization) before implementation. Activate when the user asks to create, design, or plan a dashboard. For implementation, use the dashboard-build skill after…
wiring-vizro-actions
Use this skill when adding cross-filter, cross-highlight, drill-through, or data export interactions to a Vizro dashboard — both for choosing the right interaction pattern during design and for implementing actions in code. Activate when the user wants clicks on a chart or table to filter or highlight other charts…
writing-vizro-yaml
Use this skill when writing or debugging Vizro YAML dashboard configurations — component syntax, datamanager registration, custom function wiring, filter/parameter setup, or AG Grid tables. Activate when the user is building a Vizro app, encountering YAML or runtime errors, or asking about Vizro component patterns.
selecting-vizro-charts
Use this skill when choosing chart types, applying Plotly Express conventions, configuring colors, building KPI cards, or adding tables (AG Grid) to Vizro dashboards. Activate when the user asks which chart fits their data, needs custom chart functions, wants to set colors or palettes, is creating KPI metric cards, or…
designing-vizro-layouts
Use this skill when designing or building Vizro dashboard layouts — grid configuration, component sizing, filter/parameter placement, selector types, or container patterns. Activate when the user is creating wireframes, defining page structure, placing controls, or sizing charts.
dashboard-build
Use this skill to build, implement, and test Vizro dashboards (Phase 2). Activate when the user wants to create a working app, says "just build it", or has data ready for implementation. Requires spec files from the dashboard-design skill (Phase 1), or user confirmation to skip design.