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-jdbc-virtual-schemasgit 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-jdbc-virtual-schemas)<a href="https://agentmods.dev/skills/exasol-labs/exasol-agent-skills/exasol-jdbc-virtual-schemas"><img src="https://agentmods.dev/badge/skills/exasol-labs/exasol-agent-skills/exasol-jdbc-virtual-schemas/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-jdbc-virtual-schemas"><img src="https://agentmods.dev/badge/skills/exasol-labs/exasol-agent-skills/exasol-jdbc-virtual-schemas.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.00077 | $0.00538 |
| Opus 5 | $0.00039 | $0.00269 |
| Sonnet 5 | $0.00015 | $0.00108 |
| Haiku 4.5 | $0.00008 | $0.00054 |
Grade A, and why
exasol-jdbc-virtual-schemas 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 — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exasol JDBC Virtual Schemas Skill
Use this skill only for JDBC or database-source virtual schemas where Exasol queries external data in place.
Trigger when the user mentions JDBC virtual schema, database-source federation, query external database through a virtual schema, JDBC source adapter, supported JDBC dialect, or EXPLAIN VIRTUAL together with a JDBC/database-source virtual schema context.
Routing Algorithm
-
Create or query a JDBC virtual schema
- Trigger phrases:
JDBC virtual schema,query external database,database-source virtual schema,JDBC source adapter - Load:
references/jdbc-virtual-schemas.md
- Trigger phrases:
-
Refresh, explain, or troubleshoot a JDBC virtual schema
- Trigger phrases:
EXPLAIN VIRTUALwith JDBC context,ALTER VIRTUAL SCHEMAwith JDBC context,REFRESH TABLES,partial refresh,connection validation,pushdown - Load:
references/jdbc-virtual-schemas.md
- Trigger phrases:
-
Choose a JDBC adapter family
- Trigger phrases:
supported JDBC dialect,dedicated adapter,PostgreSQL virtual schema,Oracle virtual schema,SQL Server virtual schema,MySQL virtual schema,DB2 virtual schema - Load:
references/jdbc-virtual-schemas.md
- Trigger phrases:
Notes
- Use this skill for federated access through JDBC/database-source virtual schemas.
- Use exasol-import or exasol-cloud-storage-extension when the user wants to efficiently bulk-copy data into Exasol instead of querying it in place.
- Use exasol-export when the user wants to move Exasol data out to another system.
- Use exasol-virtual-schema-adapter-development when no maintained JDBC dialect fits and the user needs custom dialect code, packaging, or adapter-side debugging.
- Use exasol-extension-catalog when the source is not clearly JDBC/database-based or the user is still choosing between Virtual Schema, extension, connector, or integration families.
- Use exasol-bucketfs when the task is specifically about uploading, listing, or removing adapter and driver JARs in BucketFS.
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 · +25 tokens per session 08873e8efdfd
- 12d ago First seen · 34 lines · 52 tokens per session scan A 94bc7a5c804e
exasol-jdbc-virtual-schemas is a skill published in the GitHub repository exasol-labs/exasol-agent-skills (10 stars, last pushed 8d ago), licensed MIT. It adds 77 tokens to every session and 538 once invoked, about $0.0004 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
web-backend-builder
Scaffold backend API, data models, ORM setup, and endpoint inventory with OpenAPI output.
backend-mean
Node.js + Express + MongoDB backend development for MEAN stack apps. Use when implementing server code: models, routes, controllers, middleware, config, and database connections.
express-api-mean
Express.js API architecture for MEAN stack apps. Use when designing REST endpoints, middleware chains, authentication flows, error handling contracts, and request/response schemas.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
cqrs-implementation
Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.
api-gateway
AWS API Gateway for REST and HTTP API management. Use when creating APIs, configuring integrations, setting up authorization, managing stages, implementing rate limiting, or troubleshooting API issues.