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-itdegit 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-itde)<a href="https://agentmods.dev/skills/exasol-labs/exasol-agent-skills/exasol-itde"><img src="https://agentmods.dev/badge/skills/exasol-labs/exasol-agent-skills/exasol-itde/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-itde"><img src="https://agentmods.dev/badge/skills/exasol-labs/exasol-agent-skills/exasol-itde.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.00055 | $0.00564 |
| Opus 5 | $0.00028 | $0.00282 |
| Sonnet 5 | $0.00011 | $0.00113 |
| Haiku 4.5 | $0.00006 | $0.00056 |
Grade A, and why
exasol-itde 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exasol ITDE Skill
Trigger when the user mentions ITDE, docker-db, local Exasol Docker database, bring_itde_up, restart_itde, take_itde_down, or local notebook-connector database setup.
Routing Algorithm
-
Start local Docker DB
- Trigger phrases:
bring_itde_up,start local exasol,docker-db - Load:
references/itde-lifecycle.md - Use scripts from:
scripts/
- Trigger phrases:
-
Check status / restart / tear down
- Trigger phrases:
get_itde_status,restart_itde,take_itde_down,container status - Load:
references/itde-lifecycle.md - Use scripts from:
scripts/
- Trigger phrases:
-
Config not present yet
- Activate exasol-notebook-connector-config
Validation
Use the lifecycle scripts to validate the stored ITDE setup:
- run
scripts/check_itde_status.pyafter setup changes - after
bring_itde_up, expectItdeContainerStatus.READY - if the next step is the shared exasol-notebook-connector-config validation flow, save
storage_backend=onpremfirst becausebring_itde_up(...)does not populate that key itself - set
db_schemayourself before handing off to schema-dependent workflows such as SQLAlchemy, Ibis, TE, or TXAIE validation - after teardown, expect
ABSENTor a clean no-container state
Expected failure mode:
scripts/restart_itde.pyshould raise a runtime error if the Docker-DB container does not exist yet- shared setup validation can fail with missing
storage_backendordb_schemaeven when ITDE itself is healthy, because those keys are not written bybring_itde_up(...) - if status checks fail because the store is missing, switch back to exasol-notebook-connector-config
Notes
- ITDE is the easiest local development database path for notebook-connector.
bring_itde_uppopulates the secure config store with the generated DB and BucketFS connection details automatically.bring_itde_updoes not populatestorage_backendordb_schema.- After ITDE is ready, other notebook-connector connection APIs can be used without manual DB/BucketFS entry.
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.
- 8d ago Changed 9452b744264f
- 12d ago First seen · 47 lines · 55 tokens per session scan A 96a04bb1071b
exasol-itde is a skill published in the GitHub repository exasol-labs/exasol-agent-skills (10 stars, last pushed 7d ago), licensed MIT. It adds 55 tokens to every session and 564 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
ecs
AWS ECS container orchestration for running Docker containers. Use when deploying containerized applications, configuring task definitions, setting up services, managing clusters, or troubleshooting container issues.
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.
eks
AWS EKS Kubernetes management for clusters, node groups, and workloads. Use when creating clusters, configuring IRSA, managing node groups, deploying applications, or integrating with AWS services.
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…