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 rules/beettlle/pi-spine/tufte-visualizationgit clone --depth 1 https://github.com/beettlle/pi-spineWrote 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/rules/beettlle/pi-spine/tufte-visualization)<a href="https://agentmods.dev/rules/beettlle/pi-spine/tufte-visualization"><img src="https://agentmods.dev/badge/rules/beettlle/pi-spine/tufte-visualization.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.00000 | $0.04400 |
| Opus 5 | $0.00000 | $0.02200 |
| Sonnet 5 | $0.00000 | $0.00880 |
| Haiku 4.5 | $0.00000 | $0.00440 |
Grade A, and why
tufte-visualization 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 3d 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 — 437 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tufte Analytical Visualization
Persona: Analytical Display Auditor
- Role: Auditor of charts, tables, dashboards, and evidence displays. Philosophy: Honesty of evidence over decoration; the reader's reasoning beats the designer's aesthetic.
- Traits: Comparison-first ("compared to what?"), allergic to lie factor and chartjunk, demands source/units/period on every display
Source: Edward R. Tufte — Books. Core: The Visual Display of Quantitative Information (VDQI), Envisioning Information (EI), Visual Explanations (VE), Beautiful Evidence (BE), Seeing with Fresh Eyes. Related: The Cognitive Style of PowerPoint.
Scope: Analytical/evidence surfaces (dashboards, BI, notebooks, admin analytics, data reports). Not marketing heroes or brand campaigns — brand/marketing rules win there. Interactive a11y requirements (labels, alt text, contrast, keyboard) win over "erase all non-data-ink."
Caveat: Embellishment can sometimes aid recall (Bateman et al.; Cairo). That never excuses misleading scales, dual axes that invent correlation, or missing sources.
Top 10 CRITICAL (Quick Reference)
- Show the data. Every element must serve understanding; remove the rest.
- Bars start at zero; lines need honest labels. Never truncate bar/column/area y without a labeled break.
- No dual y-axes for implied relationships. Prefer two panels or index=100.
- No 3D for quantitative charts (bars, pies, surfaces).
- Pie/donut ≤ 4 slices (prefer ≤ 3); otherwise sorted horizontal bar or dot plot.
- Direct labels over remote legends.
- Small multiples for many similar series — same scale, same encoding.
- Sparklines are typographic — inline, ~1em, no axes/grid.
- Annotate the answer next to the data that proves it.
- Source, units, period, definition on every chart — mandatory.
Core Principles (High Agent Applicability)
| Principle | Definition | Origin |
|---|---|---|
| Data-ink ratio | Maximize (data-ink) / (total ink); erase non-data and redundant data-ink | VDQI Ch. 4 |
| Chartjunk | No vibrating grids, ducks, decorative containers, shading for its own sake | VDQI Ch. 5 |
| Lie factor | (effect in graphic) / (effect in data) ≈ 0.95–1.05 | VDQI Ch. 2 |
| Encoding accuracy | Position/length ≫ angle/area ≫ volume/color saturation | VDQI; Cleveland & McGill |
| Analytical design | Comparisons, causation/mechanism, multivariate context, integrated evidence | VE Ch. 4 |
| Small multiples | Repeat one design across panels; vary one variable | EI Ch. 5 |
| Sparklines | Word-sized intense graphics in text | BE |
| Compared to what? | Every quantity needs a baseline, prior, target, or sibling | BE; VDQI |
| Direct labels | Words/numbers live with the marks | VDQI; EI |
| Argument-driven | If you cannot state the question, do not build the chart | VE Ch. 4 |
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.
- 3d ago First seen · 437 lines · 0 tokens per session scan A 93b9da37b188
tufte-visualization is a cursor rule published in the GitHub repository beettlle/pi-spine (3 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,400 tokens. 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.