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-querygit 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-query)<a href="https://agentmods.dev/skills/kxsystems/kx-skills/kx-query"><img src="https://agentmods.dev/badge/skills/kxsystems/kx-skills/kx-query/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-query"><img src="https://agentmods.dev/badge/skills/kxsystems/kx-skills/kx-query.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.00069 | $0.01069 |
| Opus 5 | $0.00034 | $0.00535 |
| Sonnet 5 | $0.00014 | $0.00214 |
| Haiku 4.5 | $0.00007 | $0.00107 |
Grade A, and why
kx-query 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 10d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KX Query & Data Sources
Depends on kx-dashboard-core for the dashboard envelope, ViewState schema, and binding patterns.
This skill uses progressive disclosure: the hazards, workflow, and validation rules are here; the connection/data-source JSON schemas, query patterns, pivot config, reserved-word list, and dashboard-oriented q snippets live in reference/. Read only the reference file relevant to your current step.
Reference Files
| File | Read it when you need… |
|---|---|
| reference/schema.md | The connection file format, _dataType/_subscriptionType values, and the full JSON template for every data source kind (query, analytic, virtual, pykx, polling, streaming, update query, ViewState params). |
| reference/query-patterns.md | kdb+ query idioms, filtering by ViewState type (symbol / string like / list), component-side binding, and symbol-vs-string handling. |
| reference/pivot-grid.md | The Pivot Grid data source (key: "Datatable") — pivot attributes, _layout, _mappings, and the full template. |
| reference/reserved-words.md | The reserved-word list and the validation algorithm to run before accepting any kdb+ query string. |
| reference/q-language.md | Dashboard-oriented q snippets only — the few q patterns that matter specifically when writing KX Dashboards data sources (not general q fundamentals like operators, iterators, system commands, or data types). |
⚠️ Hazards
- Always write both
_autoExecuteand_autoExec— some versions only honour one. _connectionmust match the connection filenamefield exactly (case-sensitive)._subscriptionType: "streaming"requires a streaming-capable connection — don't use it with static kdb+ processes.- ViewState param
valuemust use the template syntax (<%group/name%>or<%name%>), not a raw value. _dataType: "pykx"requires PyKX to be installed on the kdb+ process.- Polling interval is in seconds (
_subscriptionInterval). Minimum meaningful value is1. - Reserved words must never appear as assignment targets — assigning to a reserved word (e.g.
sum: 5) raises'assignat runtime. Run reserved-word validation before accepting any query. See the Reserved Word Validation section below. - Analytics run a named function, not a query.
_selectedAnalyticis a dotted kdb+ function name (e.g..fx.sub), not a table. A streaming analytic must copy its_analyticParamsinto_streamingParameters(identical) — the subscription reads its arguments from_streamingParameters. See the Analytic Data Source section inreference/schema.md.
What ships with it
5 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.
- 10d ago First seen · 49 lines · 69 tokens per session scan A 46c285a1f6a6
kx-query is a skill published in the GitHub repository KxSystems/kx-skills (16 stars, last pushed 8d ago), licensed Apache-2.0. It adds 69 tokens to every session and 1,069 once invoked, about $0.0003 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
nornicdb-cypher-queries
Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…