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/upgrade-metabase.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/upgrade-metabase)<a href="https://agentmods.dev/commands/j0hng4lt/metabase-flightsql-driver/upgrade-metabase"><img src="https://agentmods.dev/badge/commands/j0hng4lt/metabase-flightsql-driver/upgrade-metabase/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/upgrade-metabase"><img src="https://agentmods.dev/badge/commands/j0hng4lt/metabase-flightsql-driver/upgrade-metabase.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.00022 | $0.00372 |
| Opus 5 | $0.00011 | $0.00186 |
| Sonnet 5 | $0.00004 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
upgrade-metabase 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 11d 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.
What it actually says
Upgrade Metabase Pin to $1
1. Read the driver changelog FIRST
Fetch the driver changelog at the target ref and review every section between the current pin and $1:
gh api -H "Accept: application/vnd.github.raw" \
"repos/metabase/metabase/contents/docs/developers-guide/driver-changelog.md?ref=$1" | head -200
Checklist per section:
- Removed multimethods we implement? (a
defmethodon a removed defmulti fails the namespace load) - Removed/renamed feature keywords we declare? (unknown keywords throw)
- Signature changes to:
describe-fields-sql,do-with-connection-with-options,connection-details->specconventions, secrets API? - New required methods for features we claim (
:describe-fields, etc.)? - MBQL5 (
:sql-mbql5) migration notes — oursql.qp/->honeysqloverrides use the legacy clause shape.
2. Apply the bump
docker-compose.yaml:metabase/metabase:<current>→ closest release image for$1..github/workflows/build.yaml: update/extend themetabase-refmatrix entry for that line.README.md: update the Compatibility table.
3. Verify
Run /rebuild-driver, then /e2e-test. Both must pass before committing. Commit as chore: upgrade Metabase to $1.
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.
- 11d ago First seen · 34 lines · 22 tokens per session scan A d5d900247dea
upgrade-metabase is a command published in the GitHub repository J0hnG4lt/metabase-flightsql-driver (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 22 tokens to every session and 372 once invoked, about $0.0001 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 commands, from other repositories
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
access
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
check-release-health
Summarize the CI health of an OpenShift release using live data from the openshift-ci-mcp server.
analyst
Use when performing local analyst review before pushing PR changes. Assesses code quality, impact analysis, and maintainability.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.
ADO: Get Build Info
Query Azure DevOps build pipeline status and failure details, optionally linking results to work items.