A command that investigates a Metabase bug report in a new, isolated copy of Metabase and records the findings in a Linear comment. Metabase is an open-source tool for exploring and sharing data.

Reproducing bugs from GitHub issue links or Linear issue IDs, running the relevant checks, searching the local code, and posting structured findings to Linear.

It removes the manual work of setting up a clean test environment and checking whether a reported bug can be reproduced. It also gives the team a consistent written report.

repro — Command for Claude Code by metabase: A command that investigates a Metabase bug report in…

Install

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.

agentmods

npx agentmods add commands/metabase/repro-bot/repro

Clone the repo

git clone --depth 1 https://github.com/metabase/repro-bot

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/metabase/repro-bot/repro.svg)](https://agentmods.dev/commands/metabase/repro-bot/repro)

Your own site

<a href="https://agentmods.dev/commands/metabase/repro-bot/repro"><img src="https://agentmods.dev/badge/commands/metabase/repro-bot/repro.svg" alt="Measured on agentmods" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 5,753 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.05753
Opus 5	$0.00000	$0.02877
Sonnet 5	$0.00000	$0.01151
Haiku 4.5	$0.00000	$0.00575

Measured 4d ago against content hash 8247adbb860b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

repro 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 4d 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.

- **MCP tools only**: Use `mcp__metabase-repro__*` for ALL Metabase ops. Never raw Bash (curl, java, docker). `curl` is not available — use `api_call`. If any MCP tool fails (connection error OR output error like "auto-s

.claude/commands/repro.md · 443 lines

How it starts

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

/repro — Metabase Issue Auto-Reproduction

Investigate and reproduce a Metabase bug report against a fresh, isolated Metabase instance. Post findings as a structured Linear comment.

Input: $ARGUMENTS — a GitHub issue URL or Linear ID.

Usage: /repro <github-issue-url-or-linear-id>

Examples:

/repro https://github.com/metabase/metabase/issues/12345
/repro MB-12345

Rules

No commits: The worktree is ephemeral — discard any source edits when the worktree is removed in Phase 7.
MCP tools only: Use mcp__metabase-repro__* for ALL Metabase ops. Never raw Bash (curl, java, docker). curl is not available — use api_call. If any MCP tool fails (connection error OR output error like "auto-setup failed"), STOP immediately and report the exact error.
No clojure CLI: Use repl_eval or run_test. Never clojure -M/-X (wastes 30-60s per invocation).
Local code search only: Grep/Glob against ./repro/ worktrees. Never gh search code.
No subagents for code search: Direct Grep (~100 tokens) vs subagent (50K-100K tokens).
Grep/Glob tools for ALL code searches: Use the Grep and Glob tools for ALL code searches. Never use grep, find, or rg via Bash. The dedicated tools are faster, cheaper, and easier to review.
Browser: playwright-cli via Bash. Never mcp__playwright__*. See .claude/skills/playwright-cli/SKILL.md.
Linear: Call mcp__linear-server__* tools directly, not via subagents (subagents can't access MCP tools).
No web search: Never use WebSearch/WebFetch for issue details. All data from gh CLI or Linear MCP.
File reads: Read whole files or large 500+ line chunks — never scan in 60-line windows. Anti-pattern: reading the same file 5+ times with small offsets. Read the whole file once.
File searches: Never search outside ./repro/. Never find / or search the home directory.
Git commands: Use git -C <path> instead of cd <path> && git ....
CI environment failures are fatal: If a CI infrastructure issue blocks progress (git repo missing branches/tags, Docker unavailable, missing tools, filesystem permission errors), do NOT attempt to diagnose or work around it. Post a CI failure to Linear with the exact error and STOP immediately. These are workflow configuration bugs that must be fixed in repro-bot.yml, not worked around at runtime.
Parallelism: ALWAYS batch independent tool calls in the same turn. Saves 30%+ on turns. Enforced parallel checkpoints:
- Phase 0: Both ToolSearch calls (metabase-repro + linear-server)
- Phase 1: gh issue view ∥ list_issues (GitHub + Linear fetch)
- Phase 3: setup_worktree ∥ start_appdb (worktree + Docker)
- Phase 4: Multiple independent repl_eval calls, multiple Grep calls, git log + git show
No wait-for-selector: playwright-cli does NOT have a wait-for-selector command. Use snapshot + click instead.
Time budget: ~25 min total. Prioritize reproduction over exploration.

Read the full file on GitHub · 443 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.

4d ago First seen · 443 lines · 0 tokens per session scan A 8247adbb860b

Subscribe to this mod's changes

repro is a command published in the GitHub repository metabase/repro-bot (10 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,753 tokens. 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-31.

Debugging Project management

repro

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Makes network callslowCapability

How it starts

/repro — Metabase Issue Auto-Reproduction

Rules

What this file has done since we first saw it

Other commands, from other repositories

project-recap

os-meeting

workspace

standup

m-task-planner

triage-issues