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/duyet/oma/data-viznpx skills add duyet/oma --skill data-vizgit clone --depth 1 https://github.com/duyet/omaWrote 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/duyet/oma/data-viz)<a href="https://agentmods.dev/skills/duyet/oma/data-viz"><img src="https://agentmods.dev/badge/skills/duyet/oma/data-viz.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.00077 | $0.01164 |
| Opus 5 | $0.00039 | $0.00582 |
| Sonnet 5 | $0.00015 | $0.00233 |
| Haiku 4.5 | $0.00008 | $0.00116 |
Grade A, and why
data-viz 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
data-viz
Turn data into a visualization that reads correctly in five seconds. Default output is a single self-contained HTML file (no CDN, no external assets) so it opens anywhere and survives being emailed or dropped into an artifact.
Workflow
- Know the data first. Inspect shape before drawing: how many rows, how many series, are the categories ordered, is there a time axis, what are the units and ranges. Never plot a column you haven't looked at.
- Pick the chart from the question, not the data type (see heuristics).
- Render to self-contained HTML. Inline everything. Prefer hand-written SVG for <= a few hundred marks; reach for a bundled JS lib only when you need interactivity, and inline the library source.
- Check it renders — open/convert it, confirm axes, legend, and labels are present and not overlapping. A chart with a clipped legend is a bug.
Chart-choice heuristics
| The question is about… | Use | Avoid |
|---|---|---|
| Comparing values across categories | horizontal bar (sort by value) | pie beyond 2-3 slices |
| A part-to-whole split | stacked bar, or a single 100% bar | 3-D anything |
| Change over time | line (continuous) / bar (few discrete periods) | line for unordered categories |
| Relationship between two numbers | scatter | dual y-axes (usually misleading) |
| Distribution of one variable | histogram / box plot | bar chart of raw values |
| Ranking | sorted bar, or a small table | radar/spider |
| One key number | big number + a sparkline of context | a gauge |
Rules that override the table:
- Sort bars by value, not alphabetically, unless the category has a natural order (age buckets, weekdays, months).
- Bar/area y-axes start at 0. Line charts may crop the axis to show change, but say so.
- More than ~7 series on one chart = small multiples instead of a rainbow.
- If a table answers the question better than a chart (few precise numbers), ship the table.
Color and accessibility
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 89 lines · 77 tokens per session scan A 34ee00292c3a
data-viz is a skill published in the GitHub repository duyet/oma (5 stars, last pushed 14d ago), licensed Apache-2.0. It adds 77 tokens to every session and 1,164 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…