chart

A set of instructions for making charts and graphs with a chart tool. It covers supported chart types such as bar, line, pie, scatter, and time-series charts, and distinguishes them from diagrams made with Mermaid.

In plain words
What is it for?
Creating charts, graphs, and plots from data, including bar charts, line charts, pie charts, scatter plots, and other supported chart types.
Why use it?
It ensures requests to visualize numerical data use the required chart format and do not confuse data charts with process or architecture diagrams.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/kilo-org/kilocode/chart
Any agent
npx skills add Kilo-Org/kilocode --skill chart
Clone the repo
git clone --depth 1 https://github.com/Kilo-Org/kilocode

Made for: Claude Code, Codex.

Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,320 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00037 $0.01320
Opus 5 $0.00018 $0.00660
Sonnet 5 $0.00007 $0.00264
Haiku 4.5 $0.00004 $0.00132

Measured yesterday against content hash a4d3b2e2e5e9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

chart 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 yesterday.

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.

.kilo/skills/chart/SKILL.md · 158 lines

What it actually says

Data Visualization

The chart tool is ALWAYS available in this environment. When the user asks to visualize data (charts, graphs, plots), you MUST call the chart tool. Never output the config as text, never say the tool is unavailable, never suggest external renderers. Always use the tool call — it is the only correct response for data visualization requests. Do NOT repeat or echo the config JSON in your text response.

Use the chart tool only when the user explicitly asks for a chart, graph, or plot. Only use these supported Chart.js v4 types: bar, bubble, pie, doughnut, line, mixed, polarArea, radar, scatter. For area charts, use line with fill: true on the dataset — do NOT use area as a type.

Use mermaid fenced code blocks (```mermaid) when:

  • The user asks for a diagram, flowchart, sequence diagram, ER diagram, or architecture diagram
  • Visualizing relationships, processes, or structure — not data values

Mermaid is NOT a tool and is NOT Chart.js — never call the chart tool for mermaid diagrams. Just write the mermaid syntax directly in your text response inside a fenced code block. No tool call needed.

Do not use either for: code, text, or data that is already clear in prose or table form.

The chart tool input accepts:

  • title (string) — short label shown in the tool header
  • description (string, optional) — subtitle shown below the title
  • spec (string) — a Chart.js config object as a JSON string

The spec field must be a Chart.js config JSON string with type, data, and optionally options. Examples:

Bar chart:

{
  "type": "bar",
  "data": {
    "labels": ["A", "B", "C"],
    "datasets": [{ "label": "Value", "data": [10, 20, 15] }]
  }
}

Area chart (line with fill):

{
  "type": "line",
  "data": {
    "labels": ["Jan", "Feb", "Mar", "Apr"],
    "datasets": [{ "label": "Value", "data": [10, 28, 19, 45], "fill": true }]
  }
}

Line chart:

{
  "type": "line",
  "data": {
    "labels": ["Jan", "Feb", "Mar", "Apr"],
    "datasets": [{ "label": "Value", "data": [10, 28, 19, 45], "fill": false }]
  }
}

Scatter plot:

{
  "type": "scatter",
  "data": {
    "datasets": [{
      "label": "Points",
      "data": [{ "x": 1, "y": 5 }, { "x": 2, "y": 8 }, { "x": 3, "y": 3 }]
    }]
  }
}

Time series:

{
  "type": "line",
  "data": {
    "labels": ["2024-01", "2024-02", "2024-03", "2024-04"],
    "datasets": [{ "label": "Value", "data": [120, 145, 132, 178], "fill": true }]
  }
}

Pie chart:

{
  "type": "pie",
  "data": {
    "labels": ["A", "B", "C"],
    "datasets": [{ "data": [30, 50, 20] }]
  }
}

Doughnut chart:

{
  "type": "doughnut",
  "data": {
    "labels": ["A", "B", "C"],
    "datasets": [{ "data": [30, 50, 20] }]
  }
}

Radar chart:

{
  "type": "radar",
  "data": {
    "labels": ["Speed", "Power", "Agility", "Stamina"],
    "datasets": [{ "label": "Player", "data": [80, 60, 90, 70] }]
  }
}

Bubble chart:

{
  "type": "bubble",
  "data": {
    "datasets": [{
      "label": "Group A",
      "data": [{ "x": 10, "y": 20, "r": 8 }, { "x": 15, "y": 10, "r": 5 }]
    }]
  }
}

Polar area chart:

{
  "type": "polarArea",
  "data": {
    "labels": ["A", "B", "C", "D"],
    "datasets": [{ "data": [11, 16, 7, 14] }]
  }
}

Mixed chart (bar + line):

{
  "type": "bar",
  "data": {
    "labels": ["Jan", "Feb", "Mar"],
    "datasets": [
      { "type": "bar", "label": "Revenue", "data": [100, 120, 90] },
      { "type": "line", "label": "Trend", "data": [95, 115, 100] }
    ]
  }
}

You may customize colors by setting backgroundColor and borderColor arrays on datasets. The renderer handles sizing — do not set width or height.

Only include scales in options for cartesian chart types: bar, line, scatter, bubble. Do NOT include scales for pie, doughnut, polarArea, radar, or mixed — it will cause them to fail.

Changes

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.

  1. yesterday First seen · 158 lines · 37 tokens per session scan A a4d3b2e2e5e9

Subscribe to this mod's changes

chart is a skill published in the GitHub repository Kilo-Org/kilocode (27,081 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 1,320 once invoked, about $0.0002 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.