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-datafiltergit 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-datafilter)<a href="https://agentmods.dev/skills/kxsystems/kx-skills/kx-datafilter"><img src="https://agentmods.dev/badge/skills/kxsystems/kx-skills/kx-datafilter/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-datafilter"><img src="https://agentmods.dev/badge/skills/kxsystems/kx-skills/kx-datafilter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 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 Excessive Agency · line 71 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 90 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 156 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 165 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.00156 | $0.01912 |
| Opus 5.5 | $0.00062 | $0.00765 |
| Sonnet 5.5 | $0.00031 | $0.00382 |
| Haiku 4.5 | $0.00016 | $0.00191 |
Grade A, and why
kx-datafilter 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KX DataFilter & QueryBuilder Components
Also read kx-dashboard-core for: envelope, screen/widget wrapper, data sources, ViewState, binding patterns, actions, notifications, and the pre-flight checklist.
⚠️ DataFilter-Specific Hazards
kdbStringmust be a ViewState reference — never an empty string. Set it to{ "_dashboardsType": "viewstate", "value": "<filterStrViewState>" }.- Always use the two-data-source bridge pattern (raw source for schema + filtered source for results). Components that should respond to the filter bind to the filtered source, not the raw one.
queryModelmust be initialised as"{\"operator\":\"AND\",\"children\":[]}"— not"".Items[].propertyNamemust exactly match the kdb+ column name.definitionIdis"48"(not"101"— that is an older value; always use"48").
DATAFILTER
key: "DataFilter" · definitionId: "48" · version: "v2.19.0"
Integration Pattern — Two-Data-Source Bridge
The DataFilter works via a three-part wiring:
DataFilter ──(reads schema from)──▶ rawDataSource (plain select)
DataFilter ──(writes filter to)───▶ filterStr ViewState
filteredDataSource ──(reads VS)───▶ .dfilt.apply[select from <Table>; s]
Datagrid ──(reads from)─────────▶ filteredDataSource
Any component responding to the filter must bind to filteredDataSource, not rawDataSource.
generate.js config
Set componentType: "datafilter".
| Field | Description |
|---|---|
dataSource |
Raw data source name (for schema discovery) |
filterItems |
Array of { column, dataSource?, items?, fieldSummaryThreshold? } |
bindings |
Array of { key, viewState } |
useViewStates |
Boolean — use ViewState bindings for filter values |
clearIfNotInSource |
Boolean — clear filters when source changes |
ViewState (string type)
"<filterStrViewState>": {
"_viewType": true,
"_type": "string",
"_default": ""
}
Raw Data Source
"<rawDataSource>": {
"_dataType": "query", "_dataSource": "kdb",
"_connection": "<connection-name>",
"_queryString": "select from <Table>",
"_queryParams": [],
"_autoExecute": true, "_autoExec": true,
"_subscriptionType": "static"
}
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 · 201 lines · 156 tokens per session scan A 9e3b490475a0
kx-datafilter is a skill published in the GitHub repository KxSystems/kx-skills (22 stars, last pushed 22d ago), licensed Apache-2.0. It adds 156 tokens to every session and 1,912 once invoked, about $0.0006 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-datafilter compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| kx-datafilterKxSystems/kx-skills | Skill | 22 | 22d ago | Apache-2.0 | A | 156 | 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 |