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/microsoft/flint-chart/flint-chart-authornpx skills add microsoft/flint-chart --skill flint-chart-authorgit clone --depth 1 https://github.com/microsoft/flint-chartWrote 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/microsoft/flint-chart/flint-chart-author)<a href="https://agentmods.dev/skills/microsoft/flint-chart/flint-chart-author"><img src="https://agentmods.dev/badge/skills/microsoft/flint-chart/flint-chart-author.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.00081 | $0.07585 |
| Opus 5 | $0.00041 | $0.03793 |
| Sonnet 5 | $0.00016 | $0.01517 |
| Haiku 4.5 | $0.00008 | $0.00758 |
Grade A, and why
flint-chart-author 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 4d 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 — 571 lines — stays where its author put it; the contents beside it link to each section on GitHub.
flint-chart: authoring and using a chart spec
What you produce (and what you do NOT)
Your output is the spec: the chart_spec and semantic_types of a
ChartAssemblyInput. You reference data columns by name. The host
passes the resulting input to assembleVegaLite, assembleECharts,
or assembleChartjs to get a backend spec.
You write the input spec, not the output spec. And critically:
- DO emit
chart_spec(chart type, channel→field mapping, properties) andsemantic_types(field → semantic type). - Reference columns by name. How
dataitself gets bound depends on the situation — a URL, a host-side variable, or embedded rows (see "How data gets bound"). Embedding is fine for small tables; just don't re-serialize a large dataset by hand, since that risks truncation and silent value corruption and wastes tokens. - Transform data before Flint. If the requested chart needs aggregation, filtering, joins, pivots, derived columns, or long/wide reshaping beyond Flint's built-in static-series fold, use a coding, notebook, SQL, or data tool first. Then author the Flint spec against the transformed table.
- Style after Flint, only when needed. Author structure in Flint. For a
presentation tweak Flint does not express (a reference line, annotation, or
shaded band), use the Vega-Lite escape hatch — see "Post-Flint style
customization". Never feed edited Vega-Lite JSON back to
render_chart.
When the user wants more than a spec
First decide which workflow the user is asking for:
- Spec authoring only: return a
ChartAssemblyInputor itssemantic_types+chart_specpieces. Do not install packages or write renderer code unless asked. - MCP chart output: if Flint MCP tools are available, default to
create_chart_viewwhenever the user asks to see a chart — it opens an interactive, live-rendered view with a customization panel, and it validates the spec for you. Only fall back torender_chart(PNG/SVG) when the host has no App UI support or the user explicitly wants a static image. Usevalidate_chartto check a spec without rendering,compile_chartwhen the user wants backend-native JSON, andlist_chart_typeswhen you need the supported chart catalog. - Project integration, only when the user asks for code: add Flint to an
app, notebook, script, or agentic product, install/import the library, and
call an assembler in code. Keep the same
ChartAssemblyInputcontract, then let the host render the backend result.
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.
- 4d ago First seen · 571 lines · 81 tokens per session scan A 032a2735c683
flint-chart-author is a skill published in the GitHub repository microsoft/flint-chart (4,094 stars, last pushed 2d ago), licensed MIT. It adds 81 tokens to every session and 7,585 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-30.
Other skills, from other repositories
build-power-bi-report
Use when the user wants to build, design, or scaffold a Power BI report or dashboard. Triggers on phrases like "build a Power BI report", "create a dashboard", "make a sales report", "design a Power BI page", "add a page to my report", "I need a report for X". Covers requirements elicitation — what to ask the user…
wireframe-power-bi-page
Use when planning the layout of a Power BI report page. Triggers on phrases like "wireframe a page", "layout for a dashboard", "where should I put the visuals", "design the page layout", "how should I arrange these visuals". Covers canvas geometry (1280x720), 5 validated layouts, the pbirlayoutgrid tool, spacing math.
design-power-bi-report
Use when polishing or theming a Power BI report — typography, colors, KPI cards, slicer placement, formatting taste decisions. Triggers on phrases like "make my report look better", "improve the design", "what colors should I use", "format this dashboard", "report doesn't look professional".
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — errors, failed tool calls, latency, regressions, and low online-eval scores — plus Diagnostics issues. Reads live/production traces via the SDK (searchtraces and agentinsights) and works with no MCP; uses the MCP issue entity when connected.…