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-setup-personalgit 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-setup-personal)<a href="https://agentmods.dev/skills/exasol-labs/exasol-agent-skills/exasol-setup-personal"><img src="https://agentmods.dev/badge/skills/exasol-labs/exasol-agent-skills/exasol-setup-personal/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-setup-personal"><img src="https://agentmods.dev/badge/skills/exasol-labs/exasol-agent-skills/exasol-setup-personal.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.00121 | $0.00761 |
| Opus 5 | $0.00060 | $0.00380 |
| Sonnet 5 | $0.00024 | $0.00152 |
| Haiku 4.5 | $0.00012 | $0.00076 |
Grade A, and why
exasol-setup-personal 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exasol Personal Setup Skill
Exasol Personal is a full Exasol analytics database, free for personal use, run
either in a VM on the user's Mac or on compute in their own cloud account. This
skill gives high-level direction — which flavor, in what order, with what
confirmations — and defers every command that installs, provisions, or destroys
to the upstream exasol/exasol-personal documentation.
Routing Algorithm
-
Any setup, install, or deployment work — always start here
- Trigger phrases:
set up Exasol Personal,install Exasol,deploy Exasol,Exasol on my Mac,local deployment,AWS,Azure,Exoscale,STACKIT,exasol install,preset,named deployment,sample data - Load:
references/upstream-docs.mdandreferences/setup-walkthrough.md
- Trigger phrases:
-
A deployment that already exists is failing — diagnosis and cleanup
- Trigger phrases:
exasol diag local,install failed,interrupted install,exasol destroy,exasol cache,launcher not found,deployment stuck - Load:
references/troubleshooting.mdandreferences/upstream-docs.md
- Trigger phrases:
The two setup references are a pair: references/upstream-docs.md says which
upstream document to fetch and what to do when a fetch fails,
references/setup-walkthrough.md gives the phase order and the questions to
ask. Never run a walkthrough phase without the upstream document it names.
Non-Negotiable Rules
- Never reproduce install, provisioning, or account-setup commands from memory. Exasol Personal changes frequently and stale commands break setups. Fetch the upstream document and follow it.
- Ask at every decision point. Never assume answers or skip confirmations. This applies equally to Claude Code and OpenAI Codex.
- Use
exasol connect, notexapump, for SQL during setup. The launcher's client reads deployment credentials automatically; this skill never installs or configures exapump. - Never read files that may hold credentials, including the launcher's
deployment directory and provider credential or environment files. Use the
launcher's own commands, such as
exasol infoandexasol connect, and never print a credential value into the conversation. - Warn before cloud installs. They take 10–20 minutes, must not be interrupted, and incur cloud costs. An interrupted install can leave billable resources behind.
What ships with it
3 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 First seen · 53 lines · 121 tokens per session scan A d3190ac48c75
exasol-setup-personal is a skill published in the GitHub repository exasol-labs/exasol-agent-skills (10 stars, last pushed 8d ago), licensed MIT. It adds 121 tokens to every session and 761 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-09-04.
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.