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-extension-cataloggit 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-extension-catalog)<a href="https://agentmods.dev/skills/exasol-labs/exasol-agent-skills/exasol-extension-catalog"><img src="https://agentmods.dev/badge/skills/exasol-labs/exasol-agent-skills/exasol-extension-catalog/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-extension-catalog"><img src="https://agentmods.dev/badge/skills/exasol-labs/exasol-agent-skills/exasol-extension-catalog.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.00144 | $0.01687 |
| Opus 5 | $0.00072 | $0.00843 |
| Sonnet 5 | $0.00029 | $0.00337 |
| Haiku 4.5 | $0.00014 | $0.00169 |
Grade A, and why
exasol-extension-catalog 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exasol Extension Catalog Skill
Last reviewed: 2026-08-12.
Use this skill to discover or compare Exasol capability families. It helps the user choose a tool, extension, connector, integration, or architecture pattern; it is not an alternate execution guide for workflows that already have a dedicated skill.
If the request asks to execute, configure, or troubleshoot a dedicated workflow such as Text AI, Transformers, Cloud Storage Extension, native import/export, JDBC or document virtual schemas, adapter development, BucketFS, UDF/SLC, distributed ML, notebook-connector setup, or Exasol Personal setup, use that specialized skill. Keep comparison and selection requests in this catalog even when they name one or more of those options, then hand off after the choice.
The catalog organizes Exasol capabilities into six categories:
- DEPLOY: provision, install, package, configure, schedule, and operate Exasol.
- LOAD: ingest, import, federate, stream, move, or query external data.
- EXPLORE: inspect schemas, query data, use notebooks, BI tools, catalogs, and agentic query interfaces.
- ENRICH: add AI, ML, UDFs, text processing, semantic interpretation, agents, and custom computation.
- SURFACE: expose Exasol to humans, applications, BI, APIs, low-code tools, and agents.
- SCALE: improve scale-out, performance, reliability, governance, observability, testing, repeatability, and enterprise operations.
Important Use Rules
- Prefer official Exasol docs or GitHub repositories when giving installation or configuration instructions.
- Distinguish between Exasol-owned or Exasol-maintained tools, Exasol Labs/community tools, and third-party ecosystem integrations.
- For customer-facing recommendations, state support level when known. If support level is not explicit in the reference, verify the linked source before presenting it as supported.
- For current versions, latest releases, security status, or support status, check the linked source before answering.
- For destructive operations, deployment changes, credential management, RBAC, Terraform, or agent automation, include safety and rollback guidance.
- For agentic workflows, prefer governed patterns: MCP Server, Agent Control Plane, semantic layer, SQL guardrails, audit logs, and least-privilege credentials.
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 · -3 lines · +92 tokens per session ea39388d56fe
- 12d ago First seen · 97 lines · 52 tokens per session scan A 9a1451bb3e67
exasol-extension-catalog is a skill published in the GitHub repository exasol-labs/exasol-agent-skills (10 stars, last pushed 8d ago), licensed MIT. It adds 144 tokens to every session and 1,687 once invoked, about $0.0007 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
tool-calling-tutor
Use when a tool-calling agent does not call a tool, sends wrong arguments, loops without stopping, or needs a function schema. Guides a four-branch diagnosis and five-step schema repair. Do not use for framework-specific, MCP-server, or production-observability questions.
ec2
AWS EC2 virtual machine management — instances, security groups, key pairs, AMIs, EBS volumes, Auto Scaling Groups, Spot Instances, Session Manager, placement groups, and instance lifecycle automation. Trigger on ANY of these, even when EC2 isn't named explicitly: - Launching or provisioning: "spin up a server"…
cloudwatch
AWS CloudWatch monitoring for logs, metrics, alarms, and dashboards. Use when setting up monitoring, creating alarms, querying logs with Insights, configuring metric filters, building dashboards, or troubleshooting application issues.
cognito
AWS Cognito user authentication and authorization service. Use when setting up user pools, configuring identity pools, implementing OAuth flows, managing user attributes, or integrating with social identity providers.
eventbridge
AWS EventBridge serverless event bus for event-driven architectures. Use when creating rules, configuring event patterns, setting up scheduled events, integrating with SaaS, or building cross-account event routing.
s3
AWS S3 object storage for bucket management, object operations, and access control. Use when creating buckets, uploading files, configuring lifecycle policies, setting up static websites, managing permissions, or implementing cross-region replication.