metabase-flightsql-driver: Command for Claude Code

.claude/commands/e2e-test.md

e2e-test is a command for Claude Code from J0hnG4lt/metabase-flightsql-driver. It costs 29 tokens per session (1,587 once invoked), scanned A, original, Apache-2.0.

A command that runs a complete end-to-end test of the Metabase Arrow Flight SQL driver. End-to-end testing starts the connected services and checks the whole workflow from setup to a working dashboard.

In plain words
What is it for?
Use it to rebuild the Podman-based test environment, configure its services, wait for Metabase, and verify that the dashboard works.
Why use it?
It creates a fresh environment and catches failures between the driver, databases, Flight SQL servers, containers, and Metabase.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is J0hnG4lt/metabase-flightsql-driver's own configuration. It tells Claude Code how to work on metabase-flightsql-driver itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything metabase-flightsql-driver configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python scripts/metabase_setup.py.

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/J0hnG4lt/metabase-flightsql-driver/main/.claude/commands/e2e-test.md
Clone the repo
git clone --depth 1 https://github.com/J0hnG4lt/metabase-flightsql-driver

Made for: Claude Code.

Wrote 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.

agentmods badge for e2e-test

README.md
[![agentmods](https://agentmods.dev/badge/commands/j0hng4lt/metabase-flightsql-driver/e2e-test/github.svg)](https://agentmods.dev/commands/j0hng4lt/metabase-flightsql-driver/e2e-test)
Your own site
<a href="https://agentmods.dev/commands/j0hng4lt/metabase-flightsql-driver/e2e-test"><img src="https://agentmods.dev/badge/commands/j0hng4lt/metabase-flightsql-driver/e2e-test/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.

agentmods 80×15 button for e2e-test

Your own site · 80×15
<a href="https://agentmods.dev/commands/j0hng4lt/metabase-flightsql-driver/e2e-test"><img src="https://agentmods.dev/badge/commands/j0hng4lt/metabase-flightsql-driver/e2e-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,587 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00029 $0.01587
Opus 5 $0.00015 $0.00794
Sonnet 5 $0.00006 $0.00317
Haiku 4.5 $0.00003 $0.00159

Measured 8d ago against content hash 29e7d84acaf4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

e2e-test scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

if podman exec metabase curl -s -f "http://localhost:3000/api/health" >/dev/null 2>&1; then
.claude/commands/e2e-test.md · 193 lines

How it starts

The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.

End-to-End Test for Metabase Arrow Flight SQL Driver

Run a complete end-to-end test of the driver by starting all services fresh and validating functionality.

Pre-requisites

  • Podman must be installed and running
  • Python 3 must be available

Test Steps

1. Clean up existing environment

cd $PROJECT_ROOT
podman compose down -v
rm -f .env

This stops all containers, removes volumes, and deletes any stale .env file for a fresh start.

Important: The .env file contains API keys from previous runs. If not deleted, the setup script will try to use the old (now invalid) key and fail with 401 errors.

2. Start all services

podman compose up -d

This starts:

  • builder: Compiles the driver JAR using Leiningen
  • postgres: Metabase application database
  • spiced: Spice.ai Flight SQL server (port 50051)
  • gizmosql: GizmoSQL Flight SQL server (port 31337)
  • metabase: Metabase BI tool (port 3000)

3. Wait for Metabase to be ready

for i in {1..60}; do
  if podman exec metabase curl -s -f "http://localhost:3000/api/health" >/dev/null 2>&1; then
    echo "Metabase is ready!"
    break
  fi
  echo "Waiting... attempt $i"
  sleep 5
done

4. Run the setup script

python scripts/metabase_setup.py

This script:

  • Performs initial Metabase setup (creates admin user)
  • Creates API key and saves to .env
  • Creates GizmoSQL and Spice database connections
  • Syncs database schemas
  • Creates a comprehensive test dashboard with 32 cards and 5 field filters

5. Validate the dashboard

Open in browser: http://localhost:3000/dashboard/2

Or test via API (read API key from .env and use it directly):

# Read the API key from .env file
API_KEY=$(grep METABASE_API_KEY .env | cut -d'=' -f2)

# Validate dashboard exists with expected cards and parameters
podman exec metabase curl -s -H "x-api-key: $API_KEY" \
  "http://localhost:3000/api/dashboard/2" | python -c "
import sys,json
d=json.load(sys.stdin)
print(f'Dashboard: {d.get(\"name\")}')
print(f'Cards: {len(d.get(\"dashcards\",[]))}')
print(f'Parameters: {len(d.get(\"parameters\",[]))}')
"

Read the full file on GitHub · 193 lines

Changes

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.

  1. 8d ago First seen · 193 lines · 29 tokens per session scan A 29e7d84acaf4

Subscribe to this mod's changes

e2e-test is a command published in the GitHub repository J0hnG4lt/metabase-flightsql-driver (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 29 tokens to every session and 1,587 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.