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 exasol-labs/exasol-agent-skills --skill exasolgit clone --depth 1 https://github.com/exasol-labs/exasol-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/exasol-labs/exasol-agent-skills/exasol)<a href="https://agentmods.dev/skills/exasol-labs/exasol-agent-skills/exasol"><img src="https://agentmods.dev/badge/skills/exasol-labs/exasol-agent-skills/exasol/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/exasol-labs/exasol-agent-skills/exasol"><img src="https://agentmods.dev/badge/skills/exasol-labs/exasol-agent-skills/exasol.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.00056 | $0.01414 |
| Opus 5 | $0.00028 | $0.00707 |
| Sonnet 5 | $0.00011 | $0.00283 |
| Haiku 4.5 | $0.00006 | $0.00141 |
Grade A, and why
exasol 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 8d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exasol Router Skill
Use this skill whenever the user asks about Exasol. The user does not need to know internal skill names. Treat /exasol <task> and natural-language Exasol requests as the public interface.
Choose the narrowest skill whose front-matter description matches the request.
When several match, apply the precedence rules below; when several genuinely
apply, load them in dependency order.
Precedence Rules
Cloud Storage Extension over native import and export. When a request
mentions FROM SCRIPT CLOUD_STORAGE_EXTENSION, INTO SCRIPT CLOUD_STORAGE_EXTENSION, CLOUD_STORAGE_EXTENSION.IMPORT_PATH, or
CLOUD_STORAGE_EXTENSION.EXPORT_PATH, prefer
exasol-cloud-storage-extension over exasol-import or exasol-export.
Object-storage formats that only the extension reads. When a request
mentions importing Avro, ORC, or Delta from object storage such as S3,
Azure Blob Storage, Azure Data Lake, Google Cloud Storage, HDFS, or Alluxio,
prefer exasol-cloud-storage-extension unless the user clearly asks for
native IMPORT. Native import handles CSV, FBV, and Parquet; it does not read
those three formats, so a description match on "import from S3" alone routes
the request wrongly.
Import and export over general database work. When a request mentions
IMPORT, IMPORT INTO, or exapump upload, prefer exasol-import over
exasol-database even if the wording also contains generic terms such as
SQL or query. When it mentions EXPORT, EXPORT INTO, or exapump export,
prefer exasol-export the same way. A bare CREATE CONNECTION with no
import, export, or object-store file-movement intent belongs to
exasol-database.
Adapter development over adapter use. When a request mentions custom
virtual schema adapter implementation, source-specific JDBC dialect code,
custom document-file adapter code, virtual-schema-common-jdbc, adapter JAR
packaging, custom adapter properties, type mapping, pushdown capabilities,
metadata reader behavior, or adapter-side remote debugging, prefer
exasol-virtual-schema-adapter-development over
exasol-jdbc-virtual-schemas and exasol-document-virtual-schemas.
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.
- 8d ago Changed · -63 lines 1fdf25c11e7f
- 12d ago First seen · 177 lines · 56 tokens per session scan A 28729b861a7f
exasol is a skill published in the GitHub repository exasol-labs/exasol-agent-skills (10 stars, last pushed 8d ago), licensed MIT. It adds 56 tokens to every session and 1,414 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-31.
Other skills, from other repositories
dynamodb
AWS DynamoDB NoSQL database for scalable data storage. Use when designing table schemas, writing queries, configuring indexes, managing capacity, implementing single-table design, or troubleshooting performance issues.
rds
AWS RDS relational database service for managed databases. Use when provisioning databases, configuring backups, managing replicas, troubleshooting connectivity, or optimizing performance.
using-datavault4dbt
Builds Data Vault 2 models in dbt with the datavault4dbt package — staging, hubs, links, satellites, and business-vault entities — using the YAML-metadata macro pattern with correct hashkeys, hashdiffs, naming, and materializations. Use when creating or editing datavault4dbt models, setting up a raw vault, choosing…
configuring-datavault4dbt
Installs and configures the datavault4dbt package in a dbt project — packages.yml, copying the global vars into dbtproject.yml, hash and naming settings, and per-adapter setup. Use when setting up datavault4dbt, installing the package, changing hash/naming global variables, or adapting configuration for a specific…
rehashing-datavault4dbt-entities
Recalculates hashkeys and hashdiffs across an existing raw vault with datavault4dbt's rehashing macros after a change to the hash algorithm, datatype, trimming, or case sensitivity — including the v1→v2.0.0 upgrade. Use when changing hash global variables, migrating hash logic, or upgrading datavault4dbt without…
testing-a-datavault4dbt-project
Adds Data Vault 2 technical tests to a datavault4dbt project — hashkey uniqueness and not-null, link-to-hub referential integrity, and satellite key+load-date uniqueness — as dbt soft-constraint tests in YAML. Use when adding or reviewing tests for hubs, links, or satellites, or validating raw vault integrity.