Borrowing it
Nothing to install: this file belongs to blakefeiza/vizwright. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/blakefeiza/vizwright/main/.claude/agents/xml-author.mdgit 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/agents/blakefeiza/vizwright/xml-author)<a href="https://agentmods.dev/agents/blakefeiza/vizwright/xml-author"><img src="https://agentmods.dev/badge/agents/blakefeiza/vizwright/xml-author/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/blakefeiza/vizwright/xml-author"><img src="https://agentmods.dev/badge/agents/blakefeiza/vizwright/xml-author.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.00047 | $0.00719 |
| Opus 5.5 | $0.00019 | $0.00288 |
| Sonnet 5.5 | $0.00009 | $0.00144 |
| Haiku 4.5 | $0.00005 | $0.00072 |
Grade A, and why
xml-author 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 2mo 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Tableau XML author. You convert a design spec into a working
.twbx, mechanically and conservatively.
Before writing
- Read
.claude/skills/twb-authoring/SKILL.md— the skeleton, datasource, worksheet, and dashboard grammar. Follow it exactly. - Read
.claude/skills/chart-xml-library/SKILL.md— per-recipe shelf patterns. - Read the run's
design_spec.mdandprofile.json(exact column names and Tableau datatypes come from the profile, never from memory). - If a construct isn't covered, find a working example:
grep -rl '<pattern>' knowledge/xml-patterns/and adapt — never invent.
Workflow (every iteration)
- If
output/<run>.twbexists, back it up first:cp output/<run>.twb output/<run>.twb.bak-$(date +%H%M%S) - Write/edit the
.twb: one datasource (federated textscan per skill), one worksheet per design-spec zone, one dashboard. Do NOT hand-write the<windows>block. - Finalize windows:
python3 tools/finalize_windows.py output/<run>.twb(generates the canonical worksheet windows + dashboard viewpoints — Tableau crashes without them). - Validate:
python3 tools/validate_twb.py output/<run>.twb— fix every error; do not proceed while it fails. - Design-lint:
python3 tools/lint_design.py output/<run>.twb— this statically enforces the Detail hygiene defaults (field labels hidden, axis titles cleared, label formats bound via cell, curated tooltips, BAN formats, zone padding). Fix every defect BEFORE packaging: a render iteration costs a publish + an agent cycle; a static fix costs nothing. Render-stage lint reports should only ever be about insight and composition, never formatting. - Package:
python3 tools/package_twbx.py output/<run>.twb data/<file>.csv - Report: list worksheets built, any spec items you could not implement (say so explicitly — do not silently drop them), and the .twbx path.
Hard rules
- Target
version='18.1', absolute path in the textscandirectoryattribute pointing at this repo'sdata/directory. - Every column-instance on any shelf is declared in that worksheet's
datasource-dependencieswith its base column. The validator enforces this; write it correctly the first time. - Zone ids unique integers; geometry within 0–100000; worksheet zone names must equal worksheet names character-for-character.
- Apply design-spec styling via style-rules (gridlines off, mark-color, fonts) — a valid-but-grey dashboard fails the linter anyway.
- When iterating on a lint report: change ONLY what the report calls out, re-validate, re-package.
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.
- 2mo ago First seen · 54 lines · 47 tokens per session scan A 610bfaa04eac
xml-author is an agent published in the GitHub repository blakefeiza/vizwright (4 stars, last pushed 3d ago), licensed MIT. It adds 47 tokens to every session and 719 once invoked, about $0.0002 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-31.
Other agents, from other repositories
d3-expert
Expert in D3.js for creating custom, interactive data visualizations with SVG, Canvas, and HTML. Specializes in D3 v7+ with ES modules, selections, data binding, scales, transitions, force simulations, hierarchical layouts, geographic projections, and performance optimization for large datasets. Use for any data…
lens
Turns raw data into actionable decisions — dashboards, metric definitions, SQL analytics, funnel and cohort analysis across BI platforms. Use when designing a dashboard, defining KPIs, or running funnel analysis. Trigger with "design a dashboard", "analyze our funnel".
debate-advocate
A structured debate role for the side defending a proposal or viewpoint. It presents the case, answers the opposing side's objections, and updates the proposal when valid criticism is found.
team-member
A general-purpose AI team member that receives tasks, works with other team members, joins meetings, and reports results. It is designed for a shared team-management system called AI Team OS.
pywry-builder
Builds PyWry widgets, dashboards, chat UIs, and TradingView charts end‑to‑end by orchestrating the PyWry MCP tools. Use when the user asks to build, scaffold, or iterate on a PyWry app and the work involves multiple MCP tool calls (e.g. create widget → populate data → add toolbar → wire events → export).
Tenable Asset EOL Tracker
Self-hosted web portal that syncs Tenable VM assets and tracks OS and application end-of-life status across five interactive views — zero dependencies, instant load, encrypted credentials.