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-notebook-connectionsgit 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-notebook-connections)<a href="https://agentmods.dev/skills/exasol-labs/exasol-agent-skills/exasol-notebook-connections"><img src="https://agentmods.dev/badge/skills/exasol-labs/exasol-agent-skills/exasol-notebook-connections/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-notebook-connections"><img src="https://agentmods.dev/badge/skills/exasol-labs/exasol-agent-skills/exasol-notebook-connections.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.00064 | $0.00490 |
| Opus 5 | $0.00032 | $0.00245 |
| Sonnet 5 | $0.00013 | $0.00098 |
| Haiku 4.5 | $0.00006 | $0.00049 |
Grade A, and why
exasol-notebook-connections 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.
What it actually says
Exasol Notebook Connector Connections Skill
Trigger when the user mentions open_pyexasol_connection, open_sqlalchemy_connection, open_ibis_connection, open_bucketfs_bucket, BucketFS location, get_backend, connection helper, or use notebook-connector from Python.
Routing Algorithm
-
Database Connection Helpers
- Trigger phrases:
pyexasol,sqlalchemy,ibis,open connection - Load:
references/connections-api.md - Use scripts from:
scripts/
- Trigger phrases:
-
BucketFS Object Helpers
- Trigger phrases:
open_bucketfs_bucket,open_bucketfs_location,bucket path - Load:
references/connections-api.md - Use scripts from:
scripts/
- Trigger phrases:
-
Config Not Set Up Yet
- Activate exasol-notebook-connector-config
Validation
Validate the configured connection helpers in this order:
- run
scripts/check_backend.pyfirst to confirm the store resolves the expected backend - if helpers fail due to missing keys or placeholder values, activate exasol-notebook-connector-config and run its
scripts/validate_config.py - then run
scripts/open_pyexasol.py,scripts/open_sqlalchemy.py,scripts/open_ibis.py, orscripts/open_bucketfs.pyfor the helper family the user needs
Success signals:
open_pyexasol.pycan runSELECT 1open_sqlalchemy.pycan open an engine and execute a minimal statementopen_ibis.pycan list tablesopen_bucketfs.pycan resolve the bucket object and UDF-visible path
Expected failure mode:
- if the config still contains placeholder hostnames, PATs, or database IDs, these checks should fail until the real values are present
Notes
- This skill assumes the secure config store is already populated.
- Prefer these helpers over ad hoc connection construction when the user is already using notebook-connector.
What ships with it
6 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.
- 8d ago Changed adc816d412ad
- 12d ago First seen · 48 lines · 64 tokens per session scan A 00767940c34a
exasol-notebook-connections is a skill published in the GitHub repository exasol-labs/exasol-agent-skills (10 stars, last pushed 8d ago), licensed MIT. It adds 64 tokens to every session and 490 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.