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 exasol-exportgit 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-export)<a href="https://agentmods.dev/skills/exasol-labs/exasol-agent-skills/exasol-export"><img src="https://agentmods.dev/badge/skills/exasol-labs/exasol-agent-skills/exasol-export/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-export"><img src="https://agentmods.dev/badge/skills/exasol-labs/exasol-agent-skills/exasol-export.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.00098 | $0.00835 |
| Opus 5 | $0.00049 | $0.00417 |
| Sonnet 5 | $0.00020 | $0.00167 |
| Haiku 4.5 | $0.00010 | $0.00084 |
Grade A, and why
exasol-export 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 7d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exasol Export Skill
This skill covers only workflows that move data out of Exasol.
Step 0: Establish Connection
Ensure a working exapump profile before giving terminal workflows that use
exapump export:
- If the user names a profile, test it with
exapump sql --profile <name> "SELECT 1"; always place--profileafter the subcommand. Otherwise test the default profile withexapump sql "SELECT 1". - On success, proceed — and keep the same
--profile <name>after the subcommand on every later command, such asexapump export --profile <name> --table <schema.table> --output <file> --format <format>. - On failure, run
exapump profile listto see which profiles exist. - If profiles exist, present them and ask which to use, then inspect that one with
exapump profile show <name>— it masks credentials — to confirm the required fields are set. Never read,cat, or print~/.exapump/config.toml; it stores credentials in clear text. If a credential value does appear in any command output, do not repeat it in the conversation. - If no usable profile exists, have the user create one locally with
exapump profile add <name>(omit--passwordand exapump prompts on a hidden line) orexapump profile init, then retry step 1. Never ask the user to paste a password into the conversation, and never pass one as a command-line argument.
Trigger when the user mentions EXPORT, EXPORT INTO, export table, export local file, exapump export, export CSV, export Parquet, export to S3, export to Azure Blob, export to GCS, export to FTP, export to SFTP, export to HTTP, export to HTTPS, REJECT LIMIT with export intent, or CREATE CONNECTION together with export target setup intent.
Routing Algorithm
-
Local files on the user machine
- Trigger phrases:
export local file,into local,to local,exapump export - Load:
references/export.md
- Trigger phrases:
-
Remote or cloud files reachable by Exasol
- Trigger phrases:
EXPORT,EXPORT INTO,S3,Azure Blob,GCS,FTP,SFTP,HTTP,HTTPS,REJECT LIMIT,CREATE CONNECTIONwith export target setup intent - Load:
references/export.md
- Trigger phrases:
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.
- 7d ago Changed · -2 lines · +43 tokens per session 1e19d94aa4b2
- 11d ago First seen · 48 lines · 55 tokens per session scan A e66425299116
exasol-export is a skill published in the GitHub repository exasol-labs/exasol-agent-skills (10 stars, last pushed 7d ago), licensed MIT. It adds 98 tokens to every session and 835 once invoked, about $0.0005 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.