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-dashboard-coregit 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-dashboard-core)<a href="https://agentmods.dev/skills/kxsystems/kx-skills/kx-dashboard-core"><img src="https://agentmods.dev/badge/skills/kxsystems/kx-skills/kx-dashboard-core/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-dashboard-core"><img src="https://agentmods.dev/badge/skills/kxsystems/kx-skills/kx-dashboard-core.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 53 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Excessive Agency · line 201 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 343 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00089 | $0.03591 |
| Opus 5.5 | $0.00036 | $0.01436 |
| Sonnet 5.5 | $0.00018 | $0.00718 |
| Haiku 4.5 | $0.00009 | $0.00359 |
Grade A, and why
kx-dashboard-core 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 2mo 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 — 347 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KX Dashboard Core — Shared Infrastructure
Always read this skill before any component-specific skill. Every other
kx-*skill depends on the definitions here.
⚠️ Agent Hazards — Read First
id/hash/ filename must be identical. Generate the UUID once; use it forid,hash, and{uuid}.json.- ViewState names are case-sensitive and path-sensitive.
Trade Filters/sym≠trade filters/sym. Separator is/. keydrives the entire schema. Never copy a Datagrid options block under a ChartGL key or vice versa.possibleXColumns,possibleYColumns, etc. must list actual query column names.- Widget IDs must be unique across the entire dashboard, not just within one screen.
- Update
screenDetailsandscreenstogether. Mismatch corrupts navigation. - Connection name must match exactly.
_connection: "tradefeed"requires a file whosenameis also"tradefeed". Format: "General"ignoresPrecision. Use"Number"or"Formatted Number"to enforce decimal places.advancedCssis a JSON string. Escape quotes and newlines.- Navigation actions always fire last regardless of list order.
- Graph uses
"Basic"(singular), not"Basics". Unique inconsistency. - DataFilter
kdbStringmust be a ViewState reference, not an empty string.
Workflow
Step 1 — Gather inputs (AskUserQuestion)
Always ask:
- Component type (see Component Registry below)
- Dashboard name
- kdb+ connection name (e.g.
html5evalcongroup) - Query string and column names returned
- Theme:
DarkorLight - Deploy directly to
~/.kx/dashboards/data/dashboards/?
Step 2 — Generate JSON using generate.js
node generate.js --config my.config.json [--out output.json] [--deploy]
componentType values: "chartgl" | "chart3d" | "datagrid" | "datatable" | "datafilter" | "dataform" | "breadcrumbs" | "gauge" | "button" | "radar".
For other types, build the component object manually using the schema in the relevant kx-* skill.
What ships with it
1 file 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.
- 2mo ago First seen · 347 lines · 89 tokens per session scan A 4148ea751d68
kx-dashboard-core is a skill published in the GitHub repository KxSystems/kx-skills (22 stars, last pushed 22d ago), licensed Apache-2.0. It adds 89 tokens to every session and 3,591 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-08-30.
kx-dashboard-core compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| kx-dashboard-coreKxSystems/kx-skills | Skill | 22 | 22d ago | Apache-2.0 | A | 89 | Claude Code |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 103 | Claude Code |