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-virtual-schema-adapter-developmentgit 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-virtual-schema-adapter-development)<a href="https://agentmods.dev/skills/exasol-labs/exasol-agent-skills/exasol-virtual-schema-adapter-development"><img src="https://agentmods.dev/badge/skills/exasol-labs/exasol-agent-skills/exasol-virtual-schema-adapter-development/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-virtual-schema-adapter-development"><img src="https://agentmods.dev/badge/skills/exasol-labs/exasol-agent-skills/exasol-virtual-schema-adapter-development.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.00094 | $0.00542 |
| Opus 5 | $0.00047 | $0.00271 |
| Sonnet 5 | $0.00019 | $0.00108 |
| Haiku 4.5 | $0.00009 | $0.00054 |
Grade A, and why
exasol-virtual-schema-adapter-development 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 Virtual Schema Adapter Development Skill
Trigger when the user mentions build a custom virtual schema adapter, virtual-schema-common-jdbc, remote debugging for a virtual schema adapter, new SQL dialect adapter, source-specific JDBC dialect, custom document-file adapter implementation, custom adapter properties, pushdown capabilities, type mapping, metadata reader, or adapter JAR packaging.
Routing Algorithm
-
Build or customize an adapter
- Trigger phrases:
custom adapter,build virtual schema adapter,new SQL dialect,source-specific JDBC dialect,custom document-file adapter,virtual-schema-common-jdbc,SqlDialect,AdapterFactory,VirtualSchemaAdapter,metadata reader - Load:
references/adapter-development.md
- Trigger phrases:
-
Design adapter behavior
- Trigger phrases:
custom adapter properties,pushdown capabilities,type mapping,identifier quoting,literal rendering,function pushdown,custom dialect tests,adapter integration tests - Load:
references/adapter-development.md
- Trigger phrases:
-
Install or update adapter artifacts
- Trigger phrases:
adapter JAR,driver JAR,BucketFS,JAVA ADAPTER SCRIPT,deploy adapter - Load:
references/adapter-development.md
- Trigger phrases:
-
Validate and debug adapter behavior
- Trigger phrases:
EXPLAIN VIRTUAL,connection validation,remote debugging for virtual schema adapters,pushdown debugging,adapter-side issue - Load:
references/adapter-development.md
- Trigger phrases:
Notes
- Use this skill when the work is about adapter code, packaging, installation, or adapter-side debugging.
- Use exasol-jdbc-virtual-schemas or exasol-document-virtual-schemas when the user only needs to create, refresh, or query an existing virtual schema.
- Use exasol-extension-catalog first when the user is still choosing which existing adapter family or maintained extension to use.
- Use exasol-bucketfs if the task is specifically about generic BucketFS file management outside the adapter deployment flow.
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 · +24 tokens per session 7ea0af2d9ce4
- 12d ago First seen · 34 lines · 70 tokens per session scan A dd0b6203f952
exasol-virtual-schema-adapter-development is a skill published in the GitHub repository exasol-labs/exasol-agent-skills (10 stars, last pushed 7d ago), licensed MIT. It adds 94 tokens to every session and 542 once invoked, about $0.0005 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.
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.