Borrowing it
Nothing to install: this file belongs to J0hnG4lt/metabase-flightsql-driver. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/J0hnG4lt/metabase-flightsql-driver/main/.claude/skills/driver-dev/SKILL.mdgit clone --depth 1 https://github.com/J0hnG4lt/metabase-flightsql-driverWrote 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/j0hng4lt/metabase-flightsql-driver/driver-dev)<a href="https://agentmods.dev/skills/j0hng4lt/metabase-flightsql-driver/driver-dev"><img src="https://agentmods.dev/badge/skills/j0hng4lt/metabase-flightsql-driver/driver-dev.svg" alt="Measured on agentmods" 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.01320 |
| Opus 5 | $0.00039 | $0.00660 |
| Sonnet 5 | $0.00015 | $0.00264 |
| Haiku 4.5 | $0.00008 | $0.00132 |
Grade A, and why
driver-dev 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 7d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flight SQL Driver Development
Two build paths — know which artifact you are running
| Path | Used by | What it produces |
|---|---|---|
bin/build-driver.sh arrow-flight-sql inside a Metabase checkout |
CI / releases | AOT-compiled arrow-flight-sql.metabase-driver.jar |
lein uberjar via the compose builder service |
local compose demo | driver source + Arrow JDBC classes; Metabase compiles the namespace at plugin load |
Consequence: the compose path surfaces compile errors only in Metabase's startup logs (podman logs metabase), not at build time. After any driver edit, always check the log for arrow-flight-sql load errors before testing behavior.
Rebuild/redeploy cycle (compose)
podman compose down metabase builder
podman compose up -d builder # ~30s: rebuilds the jar
podman compose up -d metabase
podman logs metabase 2>&1 | grep -i "plugin\|arrow-flight-sql" | tail -20
Or run the /rebuild-driver command.
Critical invariants (violating these caused real bugs)
- Stable connection spec hash.
connection-details->specmust return identical values for identical details — an anonymous fn in the map changes the hash every call and Metabase invalidates the pool constantly. Symptoms:Hash of database X details changed; marking pool invalid,connections: 0/0, random dashboard failures. That's why:castis a named fn (arrow-flight-sql-cast-fn). - Secret-typed properties never arrive as their own name. A
type: secretpropertyfooarrives asfoo-value(uploaded) orfoo-id(persisted). Always resolve viadriver-api/secret-value-as-string/secret-value-as-file!(seesecret-string/secret-file-pathhelpers). Plain keys are only a REST-API-created fallback. - No transaction-isolation probes.
DatabaseMetaData.supportsTransactionIsolationLevelNPEs on servers with incompleteGetSqlInfo(the reasondo-with-connection-with-optionsis overridden). Never add code that touches transaction metadata. - Feature keywords are validated. Declaring a feature Metabase doesn't know throws at load. Check
metabase.driver/featuresfor the pinned version before adding flags;describe-table-fksno longer exists on 0.63+. - Set connection options only at depth 0 (
sql-jdbc.execute/recursive-connection?guard) and honor(:write? options)— forcing read-only would break future uploads/actions.
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.
- 7d ago First seen · 71 lines · 77 tokens per session scan A 817c36fbda53
driver-dev is a skill published in the GitHub repository J0hnG4lt/metabase-flightsql-driver (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 77 tokens to every session and 1,320 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-30.
Other skills, from other repositories
printing-press-amend
Amend a published CLI from one of two input sources: (1) dogfood mode mines the active Claude Code session transcript for friction (missing flags, hand- rolled API payloads, silent-null returns); (2) direct-input mode accepts user-supplied asks (rename a command, add commands or feeds, fix a named bug, optionally…
convex-performance-audit
Audits Convex performance for reads, subscriptions, write contention, and function limits. Use for slow features, insights findings, OCC conflicts, or read amplification.
convex-insights
Query a running Convex app's logs + health in natural language (official MCP): failures, slow/expensive functions, deploy causality — scoped, evidence-backed, with a dashboard deep link.
ssl-proxy-troubleshoot
Systematic workflow for troubleshooting SSL/proxy connectivity issues with government websites.
diagnose-backend-bug
Diagnose a bounded backend or multi-service failure from GitHub Issues, Jira, Aone, user-provided exports, logs, traces, responses, stack traces, or job records. Use when a service, API, RPC, worker, queue, CLI, or scheduled job bug needs correlation through the project's existing observability route before repair; do…
axiom-networking
Use when implementing or debugging ANY network connection, API call, or socket. Covers URLSession, Network.framework, NetworkConnection, connection diagnostics.