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-cloud-storage-extensiongit 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-cloud-storage-extension)<a href="https://agentmods.dev/skills/exasol-labs/exasol-agent-skills/exasol-cloud-storage-extension"><img src="https://agentmods.dev/badge/skills/exasol-labs/exasol-agent-skills/exasol-cloud-storage-extension/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-cloud-storage-extension"><img src="https://agentmods.dev/badge/skills/exasol-labs/exasol-agent-skills/exasol-cloud-storage-extension.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.00122 | $0.00541 |
| Opus 5 | $0.00061 | $0.00270 |
| Sonnet 5 | $0.00024 | $0.00108 |
| Haiku 4.5 | $0.00012 | $0.00054 |
Grade A, and why
exasol-cloud-storage-extension 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 Cloud Storage Extension Skill
Trigger when the user mentions Cloud Storage Extension, FROM SCRIPT CLOUD_STORAGE_EXTENSION, INTO SCRIPT CLOUD_STORAGE_EXTENSION, CLOUD_STORAGE_EXTENSION.IMPORT_PATH, CLOUD_STORAGE_EXTENSION.EXPORT_PATH, Avro/ORC/Delta object-storage import, extension-based object-storage loading, extension-based Parquet reader, Avro through Cloud Storage Extension, ORC through Cloud Storage Extension, Delta through Cloud Storage Extension, extension-based Parquet export, or extension-based file reader.
Routing Algorithm
- Object storage and file-reader extension workflows
- Trigger phrases:
Cloud Storage Extension,FROM SCRIPT CLOUD_STORAGE_EXTENSION,INTO SCRIPT CLOUD_STORAGE_EXTENSION,CLOUD_STORAGE_EXTENSION.IMPORT_PATH,CLOUD_STORAGE_EXTENSION.EXPORT_PATH,Avro from object storage,ORC from object storage,Delta from object storage,ORC from S3,Avro from S3,Delta from S3,extension-based object-storage loading,extension-based Parquet reader,ORC through Cloud Storage Extension,Avro through Cloud Storage Extension,Delta through Cloud Storage Extension,extension-based Parquet export - Load:
references/cloud-storage-extension.md
- Trigger phrases:
Notes
- Use this skill when the user needs the Cloud Storage Extension UDF path rather than direct native
IMPORTorEXPORT. - Use exasol-import for direct local-file and native SQL import behavior.
- Use exasol-export for direct native SQL export behavior and local
exapump export. - Use exasol-bucketfs when the user needs to upload, list, or remove the extension JAR in BucketFS.
- Use exasol-document-virtual-schemas for federated read-only access to object or file storage.
- Use exasol-extension-catalog only when the user is still comparing federation, copy, connector, or extension families.
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.
- 8d ago Changed · +60 tokens per session 114810ea4732
- 12d ago First seen · 24 lines · 62 tokens per session scan A 7c33e2e95beb
exasol-cloud-storage-extension is a skill published in the GitHub repository exasol-labs/exasol-agent-skills (10 stars, last pushed 8d ago), licensed MIT. It adds 122 tokens to every session and 541 once invoked, about $0.0006 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
rds
AWS RDS relational database service for managed databases. Use when provisioning databases, configuring backups, managing replicas, troubleshooting connectivity, or optimizing performance.
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"…
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.
cloudformation
AWS CloudFormation infrastructure as code for stack management. Use when writing templates, deploying stacks, managing drift, troubleshooting deployments, or organizing infrastructure with nested stacks.
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.
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.