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/yonatangross/orchestkitWrote 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/yonatangross/orchestkit/chart-encoding-standard)<a href="https://agentmods.dev/rules/yonatangross/orchestkit/chart-encoding-standard"><img src="https://agentmods.dev/badge/rules/yonatangross/orchestkit/chart-encoding-standard/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/rules/yonatangross/orchestkit/chart-encoding-standard"><img src="https://agentmods.dev/badge/rules/yonatangross/orchestkit/chart-encoding-standard.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.00067 | $0.01018 |
| Opus 5.5 | $0.00027 | $0.00407 |
| Sonnet 5.5 | $0.00013 | $0.00204 |
| Haiku 4.5 | $0.00007 | $0.00102 |
Grade A, and why
chart-encoding-standard 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chart Encoding Standard
Load when: generating any output that renders quantitative data marks — a bar, line, area, heatmap, KPI tile, meter, or sparkline — in HTML (playground, dashboard), an infographic, an MCP visual, or a multi-surface target. Skip for: the ASCII floor (monochrome + emoji —
/datavizis HTML-only, no overlap).
OrchestKit does not own chart form or color. For the data-mark layer, defer to Claude
Code's bundled /dataviz skill exactly the way visualize-plan defers ASCII to
glyph — it is an upstream dependency, not something ork reimplements. ork owns
the domain (what the chart is about) and the chrome (frame/persona); /dataviz owns
the marks (which form, which colors, is it accessible).
The three steps — all via /dataviz
- Form (
choosing-a-form): first ask is it even a chart? — a single value is a stat tile, a ratio-to-limit is a meter, >7 meaningful classes is a table. Only then pick bar / line / heatmap by the data's job. Never a one-bar bar chart. - Color (the six-check formula): every mark color does exactly one job — categorical
(8 fixed hues, fixed order), sequential (one hue, light→dark), diverging (two hues
- neutral midpoint), or status (fixed scale, always icon+label). No hand-picked hex.
- Validate (
validate_palette.js): run it; exit 0 is required. A CVD WARN (ΔE 8–12) is legal only with secondary encoding; a contrast WARN obligates a relief channel — ship visible direct labels or the table-view twin.
The chrome ↔ marks boundary (the one real seam)
Chrome and marks are different pixels — do not let one palette govern both:
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 · 70 lines · 67 tokens per session scan A 124f010dab24
chart-encoding-standard is a cursor rule published in the GitHub repository yonatangross/orchestkit (298 stars, last pushed today), licensed MIT. It adds 67 tokens to every session and 1,018 once invoked, about $0.0003 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-09-09.
Other cursor rules, from other repositories
pn-design-system
Design system rule: enforces token usage when editing CSS, SCSS, or styled components. Use tokens for color, spacing, typography; avoid one-off values. For establishing or auditing a design system, use the pn-design-system skill.
pn-figma
Figma design-to-code conventions: token extraction, component mapping, naming alignment. Use when implementing designs from Figma or maintaining design-code sync.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.