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 agentmods add skills/openlinksoftware/ai-agent-skills/xmla-clientnpx skills add OpenLinkSoftware/ai-agent-skills --skill xmla-clientgit clone --depth 1 https://github.com/OpenLinkSoftware/ai-agent-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/openlinksoftware/ai-agent-skills/xmla-client)<a href="https://agentmods.dev/skills/openlinksoftware/ai-agent-skills/xmla-client"><img src="https://agentmods.dev/badge/skills/openlinksoftware/ai-agent-skills/xmla-client.svg" alt="Measured on agentmods" 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 | $0.00062 | $0.00874 |
| Opus 5 | $0.00031 | $0.00437 |
| Sonnet 5 | $0.00012 | $0.00175 |
| Haiku 4.5 | $0.00006 | $0.00087 |
Grade A, and why
xmla-client 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 4d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
XMLA Client
Use scripts/xmla_client.py to speak XMLA directly over SOAP 1.1. It uses only the Python standard library.
Workflow
- Start with
DISCOVER_DATASOURCES. Do not reject an endpoint because HTTPGETreturns 404; XMLA is exercised by a SOAPPOSTand a service may accept only that method. - Inspect the returned
DataSourceInfo, provider name, provider type, URL, and authentication mode. - Continue with
DISCOVER_SCHEMA_ROWSETSfor the selected data source. Then use an advertised schema rowset such asDBSCHEMA_CATALOGS,MDSCHEMA_CUBES, orMDSCHEMA_MEASURESwith appropriate restrictions. - Use
executeonly when the user wants a statement run. XMLA providers may accept MDX, SQL, or another command dialect. Treat data-changing statements as mutations and require explicit authorization before sending them. - On failure, preserve the HTTP status and SOAP Fault. Retry only when a changed binding, credential, property, or restriction is supported by evidence.
Read references/xmla-protocol.md when choosing discovery rowsets, properties, output handling, or authentication. Read references/demo-openlink-proof.md for the live OpenLink proof that motivated this client.
Read README.md when the user wants runnable, verified SQL or SPASQL/SPARQL-FED examples.
Commands
Discover data sources:
python3 scripts/xmla_client.py \
--endpoint https://example.com/XMLA \
discover --request-type DISCOVER_DATASOURCES
Discover catalogs for one advertised data source:
python3 scripts/xmla_client.py \
--endpoint https://example.com/XMLA \
--data-source-info 'DSN=Local_Instance' \
discover --request-type DBSCHEMA_CATALOGS
Execute a statement from a file:
python3 scripts/xmla_client.py \
--endpoint https://example.com/XMLA \
--data-source-info 'DSN=Local_Instance' \
--catalog Demo \
execute --statement-file query.mdx --output-format pretty-xml
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.
- 4d ago First seen · 65 lines · 62 tokens per session scan A fe6afa506012
xmla-client is a skill published in the GitHub repository OpenLinkSoftware/ai-agent-skills (38 stars, last pushed today), licensed MIT. It adds 62 tokens to every session and 874 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…