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 agentmods add skills/metabase/repro-bot/metabase-referencenpx skills add metabase/repro-bot --skill metabase-referencegit clone --depth 1 https://github.com/metabase/repro-botWhat 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 | $0.00047 | $0.02020 |
| Opus 5 | $0.00023 | $0.01010 |
| Sonnet 5 | $0.00009 | $0.00404 |
| Haiku 4.5 | $0.00005 | $0.00202 |
Grade A, and why
metabase-reference 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 2d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Metabase Reference
REPL Recipes
Inspect tables: (t2/select [:model/Table :id :name :db_id] :db_id 1)
Check settings: (t2/select-one :model/Setting :key "site-name")
Create saved question (native SQL):
(mt/user-http-request :crowberto :post 200 "card"
{:name "Test Question" :database_id 1
:dataset_query {:database 1 :type :native :native {:query "SELECT 1"}}
:display :table :visualization_settings {} :collection_id nil})
Create MBQL question (via API — preferred for card creation):
api_call(method="POST", path="/card", body='{"name":"Test Question","database_id":1,"dataset_query":{"database":1,"type":"query","query":{"source-table":3,"aggregation":[["count"]],"breakout":[["field",63,{"temporal-unit":"month"}],["field",18,null]],"order-by":[["asc",["field",63,{"temporal-unit":"month"}]]]}},"display":"bar","visualization_settings":{},"collection_id":null}')
Key fields: database_id (top-level, required), dataset_query.database (must match), dataset_query.type = "query" for MBQL. Use "native" only for raw SQL.
Create MBQL question (via REPL — use only for non-UI bugs):
(mt/user-http-request :crowberto :post 200 "card"
{:name "Test Question" :database_id 1
:dataset_query {:database 1 :type :query
:query {:source-table 3
:aggregation [[:count]]
:breakout [[:field 63 {:temporal-unit :month}]
[:field 18 nil]]}}
:display :bar :visualization_settings {} :collection_id nil})
Returns the full card map with :id. Do NOT use t2/insert-returning-instance! for cards — it silently fails due to internal validation.
Card creation pitfall: Never use
t2/insert-returning-instance!for:model/Card— it silently returnsnilwhen the internal pMBQL validation rejects the query format. Always useapi_callormt/user-http-requestwhich give clear error messages on schema violations.
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.
- 2d ago First seen · 150 lines · 47 tokens per session scan A 0fb3732322e0
metabase-reference is a skill published in the GitHub repository metabase/repro-bot (10 stars, last pushed 5mo ago), licensed MIT. It adds 47 tokens to every session and 2,020 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…