Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/mendixlabs/mxclinpx agentmods add skills/mendixlabs/mxcli/mendix-vega-chartsWrote 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/mendixlabs/mxcli/mendix-vega-charts)<a href="https://agentmods.dev/skills/mendixlabs/mxcli/mendix-vega-charts"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/mendix-vega-charts/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/mendixlabs/mxcli/mendix-vega-charts"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/mendix-vega-charts.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.00106 | $0.02901 |
| Opus 5.5 | $0.00042 | $0.01160 |
| Sonnet 5.5 | $0.00021 | $0.00580 |
| Haiku 4.5 | $0.00011 | $0.00290 |
Grade A, and why
mendix-vega-charts 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 12d 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vega-Lite charts in Mendix
What this is
A pluggable widget, roughly 150 lines of TSX, with two properties that matter:
| Property | What it carries |
|---|---|
spec |
A Vega-Lite or Vega specification, as JSON text. Static, authored once, committed. |
chartData |
A string attribute holding a JSON array of row objects. Built by a microflow. |
The widget folds the data into the spec under the name given by datasetName and hands the result to vega-embed, which picks Vega or Vega-Lite from the spec's own $schema. Nothing else happens at runtime.
The split is the whole point. The model emits a table of facts; the specification decides what that table looks like. A microflow that concatenates a chart payload — series, axes, colours — is a microflow that has to be edited every time the chart changes, and it cannot be checked without running the app. A microflow that emits [{"cat":"Groceries","m":"2026-06-01","v":697.70}, ...] can be checked against the database with a SQL query, and the spec beside it can be compiled and measured without a browser at all (see Verifying).
Who this is for
An agent. The tradeoff is deliberate: a hand-authored Vega-Lite spec is a large piece of JSON, which is uncomfortable to maintain in Studio Pro's property editor and comfortable for a coding agent that can compile it, render it headless, and measure the result. If a human will maintain the chart by hand in Studio Pro, use Studio Pro's chart widgets instead.
What makes this usable without deep Vega-Lite knowledge is specs/ — working specifications for the common shapes, each with a sample data file, each of which compiles and renders. Start from the closest one and change fields, not structure.
Getting the widget into a project
See references/install.md. Summary: copy the widget source, npm ci, npm run build, put the built .mpk in the project's widgets/ folder, and commit it — a gitignored widgets/ makes every other clone unbuildable.
What ships with it
31 files 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.
- pack.yaml 1.7 KB
- references/failure-modes.md 8.2 KB
- references/install.md 4.5 KB
- references/properties.md 3.5 KB
- scripts/check-spec.mjs 4.9 KB runs code
- scripts/package.json 341 B
- specs/bar-ranked.data.json 232 B
- specs/bar-ranked.json 740 B
- specs/calendar-heatmap.data.json 5.0 KB
- specs/calendar-heatmap.json 1.0 KB
- specs/line-timeseries.data.json 2.0 KB
- specs/line-timeseries.json 1.2 KB
- specs/README.md 2.8 KB
- specs/scatter-brushed.data.json 12 KB
- specs/scatter-brushed.json 1.0 KB
- specs/small-multiples-table.data.json 22 KB
- specs/small-multiples-table.json 3.3 KB
- specs/sparkline-cell.data.json 837 B
- specs/sparkline-cell.json 2.0 KB
- specs/stacked-area-by-group.data.json 10 KB
- specs/stacked-area-by-group.json 1.3 KB
- widget/package-lock.json 946 KB
- widget/package.json 1001 B
- widget/src/csrf.ts 3.7 KB runs code
- widget/src/package.xml 418 B
- widget/src/ui/VegaChart.css 913 B
- widget/src/VegaChart.tsx 7.8 KB
- widget/src/VegaChart.xml 4.1 KB
- widget/test/csrf.test.ts 5.0 KB runs code
- widget/tsconfig.json 468 B
- widget/typings/VegaChartProps.d.ts 1.2 KB runs code
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.
- 12d ago Changed e7f00f7e18c5
- 24d ago Changed · +45 lines 1e2ac69d2b84
- 1mo ago First seen · 145 lines · 106 tokens per session scan A 1a438d52d1ff
mendix-vega-charts is a skill published in the GitHub repository mendixlabs/mxcli (131 stars, last pushed yesterday), licensed Apache-2.0. It adds 106 tokens to every session and 2,901 once invoked, about $0.0004 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
stuck
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.
e2e-testing
Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic inspection. Use this skill whenever you need to verify CLI behavior with real model calls, reproduce user-reported bugs end-to-end, test MCP tool integrations, or inspect raw API request/response…
structured-debugging
Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…
desktop-brand-builder
Generate a branded Qwen Code desktop package from the Tauri desktop shell using a minimal brandId and logo. Use when the user wants a custom, white-label, or rebranded desktop client, installer, DMG/EXE/AppImage/deb, or one-click brand build on top of packages/desktop.
batch-api
Prepare a many-file, single-turn transform (translate, rewrite, extract) as a plan and submit it to the asynchronous, half-price DashScope Batch API; results are delivered as new files hours later. Invoke explicitly with /batch-api.
workflow-creator
Create or update reusable Dynamic Workflow JavaScript files under .qwen/workflows. Use when the user asks to create, save, edit, or reuse a Dynamic Workflow, including requests started from the Web Shell Workflows page.