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 KxSystems/kx-skills --skill kx-piegit clone --depth 1 https://github.com/KxSystems/kx-skillsWrote 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/kxsystems/kx-skills/kx-pie)<a href="https://agentmods.dev/skills/kxsystems/kx-skills/kx-pie"><img src="https://agentmods.dev/badge/skills/kxsystems/kx-skills/kx-pie/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/kxsystems/kx-skills/kx-pie"><img src="https://agentmods.dev/badge/skills/kxsystems/kx-skills/kx-pie.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00142 | $0.01257 |
| Opus 5 | $0.00071 | $0.00629 |
| Sonnet 5 | $0.00028 | $0.00251 |
| Haiku 4.5 | $0.00014 | $0.00126 |
Grade A, and why
kx-pie 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 11d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KX PieJS Component — Pie / Donut Chart
key: "PieJS" · definitionId: "1009" · version: "v2.3.0.1"
Also read kx-dashboard-core for: envelope, screen/widget wrapper, data sources, ViewState, binding patterns, actions, notifications, and the pre-flight checklist.
This skill uses progressive disclosure: the hazards, workflow, field summary, and output checklist are here; the full JSON schema blocks, field tables, the 30-value Animations easing list, and the worked example live in reference/. Read only the reference file relevant to your current step.
Reference Files
| File | Read it when you need… |
|---|---|
| reference/component-schema.md | The canonical options object plus every sub-section schema and field table — Basics, DataSet, Layers, HighlightRules, Legend, InnerLabel, Style, the full Animations easing list, Padding, and FileExport. |
| reference/examples.md | The copy-ready Minimal Working Example (donut chart). |
⚠️ PieJS-Specific Hazards
DataSet.Layersis an array — each layer maps one data column to a pie segment. At least one layer is required.DataSet.Labelis the categorical column (segment labels).DataSet.Layers[n].Segmentis the numeric value column. They must be different columns.- Set
DonutRatio: 0for a standard pie chart; any value above0makes it a donut. possibleLabels/possibleColumnsare auto-populated by the UI — always emit as[]or[""]when building from scratch.Basics.FocusandBasics.Selectedexpect ViewState paths (not literal values).Style.chartBarColorsdrives the segment colour palette. Supply at least as many colours as there are unique label values, or segments will cycle and repeat.HighlightRulesoverride the layer colour for matching rows — evaluated in order, first match wins.
Workflow
- Confirm pie vs donut. Set
DataSet.DonutRatio: 0for a solid pie, or a value 1–100 for a donut. If the user wants a KPI/gauge, stop and use kx-gauge; for line/bar/area, use kx-chartgl. - Identify the columns.
DataSet.Label= the categorical column (segment labels);DataSet.Layers[0].Segment= the numeric value column. They must be different columns. - Build the component — envelope +
optionswithBasics,DataSet,Legend,Style,InnerLabel,Padding,Animations,FileExport. Full schema and field tables inreference/component-schema.md. - Wire the palette. Populate
Style.chartBarColorswith at least as many colours as there are unique label values (see Hazards). - Add interactivity if requested —
Basics.Focus/Basics.SelectedViewState paths for cross-filtering, andBasics.Actionsfor click/hover behaviour (see kx-actions). - Match the example. Copy the Minimal Working Example from
reference/examples.mdand adapt it. - Validate against the Hazards above and the Output Checklist below.
What ships with it
2 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.
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.
- 11d ago First seen · 77 lines · 142 tokens per session scan A 5b33cd52f349
kx-pie is a skill published in the GitHub repository KxSystems/kx-skills (16 stars, last pushed 8d ago), licensed Apache-2.0. It adds 142 tokens to every session and 1,257 once invoked, about $0.0007 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…