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/mcp-server --skill exasol-import-exportgit clone --depth 1 https://github.com/exasol/mcp-serverWrote 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/mcp-server/exasol-import-export)<a href="https://agentmods.dev/skills/exasol/mcp-server/exasol-import-export"><img src="https://agentmods.dev/badge/skills/exasol/mcp-server/exasol-import-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/mcp-server/exasol-import-export"><img src="https://agentmods.dev/badge/skills/exasol/mcp-server/exasol-import-export.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 Tool Misuse · line 69 Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.Fix: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
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.00049 | $0.02424 |
| Opus 5.5 | $0.00020 | $0.00970 |
| Sonnet 5.5 | $0.00010 | $0.00485 |
| Haiku 4.5 | $0.00005 | $0.00242 |
Grade A, and why
exasol-import-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 1mo 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 — 331 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exasol IMPORT and EXPORT
When to Use What
| Scenario | Tool |
|---|---|
| Remote or cloud files (S3, Azure, GCS, FTP, HTTP) | SQL IMPORT / EXPORT |
| Files on a local machine (EXAplus/JDBC only) | FROM LOCAL CSV FILE / INTO LOCAL CSV FILE |
| Federated queries without copying data | Virtual Schemas |
Use IMPORT/EXPORT when the data source or destination is a remote location accessible from the Exasol cluster. Execute IMPORT and EXPORT statements via the execute_exasol_write_query MCP tool. FROM LOCAL CSV FILE and INTO LOCAL CSV FILE only work from EXAplus or JDBC clients; they do not work inside UDF scripts or through the MCP server.
Connection Objects
Connection objects store credentials for remote data sources. They are required for all cloud IMPORT/EXPORT operations.
-- Create or replace a connection
CREATE OR REPLACE CONNECTION my_conn
TO 'https://...'
USER 'username' IDENTIFIED BY 'password';
-- List connections (DBA only)
SELECT * FROM EXA_DBA_CONNECTIONS;
-- Drop a connection
DROP CONNECTION my_conn;
Cloud Connection Strings
Amazon S3:
CREATE OR REPLACE CONNECTION s3_conn
TO 'https://my-bucket.s3.eu-west-1.amazonaws.com'
USER '' IDENTIFIED BY 'S3_ACCESS_KEY=AKIA...;S3_SECRET_KEY=secret...';
Azure Blob Storage (SAS token):
CREATE OR REPLACE CONNECTION azure_conn
TO 'https://myaccount.blob.core.windows.net/mycontainer'
USER '' IDENTIFIED BY 'AZURE_SAS_TOKEN=sv=2021-06-08&ss=b&srt=co...';
Azure Blob Storage (Entra ID / client secret):
CREATE OR REPLACE CONNECTION azure_conn
TO 'https://myaccount.blob.core.windows.net/mycontainer'
USER 'myaccount' IDENTIFIED BY 'ClientSecret'
CLIENT ID 'app-id' TENANT ID 'tenant-id';
Google Cloud Storage:
CREATE OR REPLACE CONNECTION gcs_conn
TO 'https://storage.googleapis.com/my-bucket'
USER '' IDENTIFIED BY 'GCS_ACCESS_KEY=GOOG...;GCS_SECRET_KEY=secret...';
TLS: Append ;VERIFY=FALSE to the IDENTIFIED BY string to skip certificate verification (not recommended for production).
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.
- 1mo ago First seen · 331 lines · 49 tokens per session scan A b855fbbd3d1c
exasol-import-export is a skill published in the GitHub repository exasol/mcp-server (18 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 2,424 once invoked, about $0.0002 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.
Other skills, from other repositories
catalog-import-export
Import and export your entire product catalog in bulk using your platform's native tools or dedicated apps, with validation and scheduled sync support.
pg-vacuum-tuning
Monitors and tunes PostgreSQL vacuum operations including autovacuum configuration, vacuum progress tracking, wraparound prevention, and per-table vacuum strategy. Provides tuning recommendations for high-churn OLTP and large analytical tables.
pg-bloat-analysis
Detects and remediates table and index bloat in PostgreSQL using pgstattuple analysis. Identifies fragmentation, dead tuples, and wasted space with prioritized maintenance actions including VACUUM, REINDEX, and pgrepack recommendations.
pg-health-check
Performs comprehensive PostgreSQL database health assessments covering connections, cache performance, locks, replication, wait events, active queries, and configuration review. Produces a scored health report with prioritized recommendations.
pg-index-optimization
Performs comprehensive PostgreSQL index optimization including unused index cleanup, duplicate detection, missing index recommendations, and hypothetical index testing with HypoPG. Provides actionable CREATE/DROP INDEX statements with estimated impact.
pg-lock-diagnosis
Diagnoses PostgreSQL lock contention including blocking lock chains, deadlock patterns, idle-in-transaction problems, and wait event analysis. Guides the agent through identifying blockers, understanding lock types, and recommending transaction and configuration changes.