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/commands/e2e-test.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/commands/j0hng4lt/metabase-flightsql-driver/e2e-test)<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.
<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>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.00029 | $0.01587 |
| Opus 5 | $0.00015 | $0.00794 |
| Sonnet 5 | $0.00006 | $0.00317 |
| Haiku 4.5 | $0.00003 | $0.00159 |
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 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\",[]))}')
"
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 · 193 lines · 29 tokens per session scan A 29e7d84acaf4
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.
Other commands, from other repositories
paul:verify
Guide manual user acceptance testing of recently built features.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
ui-snapshot.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
laravel-playwright
E2E Playwright patterns; use the laravel:e2e-playwright skill exactly as written.
verify-pr
Verify a PR's frontend changes through browser automation.
harness-eval
A four-level verification command for completed software tasks. It checks whether the code builds, matches its documented contracts, works end to end, and follows the project's governing rules.