Unovis is a modular data-visualization framework for building charts, maps, network graphs, and other visual components in JavaScript or TypeScript applications. It supports React, Angular, Svelte, Vue, Solid, and vanilla projects, with packages that can be imported individually.
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 skills add f5/unovis --skill add-componentgit clone --depth 1 https://github.com/f5/unovisWrote 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/f5/unovis/add-component)<a href="https://agentmods.dev/skills/f5/unovis/add-component"><img src="https://agentmods.dev/badge/skills/f5/unovis/add-component/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/skills/f5/unovis/add-component"><img src="https://agentmods.dev/badge/skills/f5/unovis/add-component.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00074 | $0.01306 |
| Opus 5.5 | $0.00030 | $0.00522 |
| Sonnet 5.5 | $0.00015 | $0.00261 |
| Haiku 4.5 | $0.00007 | $0.00131 |
Grade A, and why
add-component 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adding a component to Unovis
Operational checklist. For the conceptual tutorial (data models, SVG vs HTML, transitions) read
packages/website/contributing/guides/adding-a-component.mdx. Before writing anything, open a
similar existing component and copy its shape — e.g. packages/ts/src/components/line (XY) or
packages/ts/src/components/donut (Core).
1. Build the core in packages/ts
Create packages/ts/src/components/<kebab-name>/ (kebab-case dir + files):
config.ts—ConfigInterface(JSDoc each prop, end withDefault: \...`) and aConfigclass with defaults. Extend the right superclass:XYComponentConfig*for XY components,ComponentConfig*` for Core components. Stand-alone components don't extend.index.ts— the component class. ExtendsXYComponentCore/ComponentCore(or stands alone). Declaresstatic selectors = s,static cssVariables = s.variables,config,events, and a_render(customDuration?)(orrender) with clear enter / update / exit D3 selections.style.ts— emotioncssselectors + acssVarDefaultsmap. CSS variables are named--vis-<component>-<selector>-<property>; every color var needs a--vis-dark-...counterpart. Importcss/injectGlobalfrom@/styles/emotion(not@emotion/cssdirectly) so styles respect theglobalThis.UNOVIS_NONCECSP nonce. Exportvariables = getCssVarNames(cssVarDefaults)and callinjectGlobalCssVariables(...).types.ts— component-specific types (optional).modules/— extract long render logic intocall-able helpers (optional).
Match the house style: no semicolons, single quotes, 2-space indent, explicit return types.
2. Export from core
- Add the component (and its public config/types) to
packages/ts/src/components.ts. - If you expose new public types, also export them from
packages/ts/src/types.ts.
3. Register in the shared registry
Add one entry to getComponentList() in packages/shared/integrations/components.ts. This is
the source of truth for the wrapper generators and for commitlint's Component scope.
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 · 101 lines · 74 tokens per session scan A e9bc56c6907d
add-component is a skill published in the GitHub repository f5/unovis (2,856 stars, last pushed yesterday), licensed Apache-2.0. It adds 74 tokens to every session and 1,306 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-03.
Other skills, from other repositories
bklit-ui
Install, compose, theme, and animate Bklit UI charts (the @bklit shadcn registry) in a React / Next.js app. Use when the user wants a chart, graph, or data visualization: line, area, bar, live/streaming line, composed, scatter, candlestick/OHLC, pie, ring/donut, radar, gauge, heatmap, funnel, sankey, sunburst, or…
globestudio
Creates, edits and embeds dotted world maps and animated 3D globes with Globestudio (globestudio.app), a free open source studio with 21 looks. Use when the user wants a dotted map, a dotted or 3D globe, a spinning earth or a stylized world map for a website hero, background, slide, social post or video; when they…
estimate-jira
Estimate complexity, effort, and risks for JIRA tickets, features, or projects. Generates structured reports with time estimates, dependencies, risk analysis, and known unknowns. Use when user asks to "estimate", "size", or "analyze complexity" of work items.
chart-defaults
Find the actual runtime default value of any AG Charts configuration option, and keep JSDoc Default: markers accurate. Use when documenting a default, verifying a change has not altered one, writing tests against default behaviour, or auditing whether a TypeScript comment matches the theme template.
hot-paths
AG Charts runtime hot paths: which files run per datum, per frame or per interaction, the invariants each tier must hold, and how to evidence a performance claim. Use when reviewing a change that touches series, scene, data-model, scale, interaction or DOM code, when asked whether a diff will cost performance, or when…
module-definitions
Add or change an AG Charts module definition: which options it owns, how community reports it when missing, how its theme defaults and validation reach the chart, and how the generated module tables stay in step. Use when creating a module, moving a feature into one, adding an option path a module owns, or when a…