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/write-testnpx skills add metabase/repro-bot --skill write-testgit 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.00062 | $0.01314 |
| Opus 5 | $0.00031 | $0.00657 |
| Sonnet 5 | $0.00012 | $0.00263 |
| Haiku 4.5 | $0.00006 | $0.00131 |
Grade A, and why
write-test 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Failing Test
This skill is invoked from the /repro workflow. The issue ID, repro dir, reproduction status, and root cause are in conversation context from prior phases.
Determine Test Type
| Bug Type | Test Type | Location |
|---|---|---|
| Backend logic, query processor, API | Clojure unit test | test/metabase/... |
| Frontend UI behavior, rendering | Jest unit/component test | frontend/test/... or co-located *.unit.spec.ts/*.unit.spec.tsx |
| End-to-end user workflow, UI interaction | Cypress acceptance test | e2e/test/scenarios/... |
| Mixed (backend + frontend) | Both — Clojure test for data + frontend/e2e test for UI |
Find Relevant Test File
Use the root cause to identify source file(s), then locate the corresponding test file:
Backend: src/metabase/foo/bar.clj → test/metabase/foo/bar_test.clj
Frontend: frontend/src/metabase/foo/Bar.tsx → frontend/src/metabase/foo/Bar.unit.spec.tsx or frontend/test/metabase/foo/Bar.unit.spec.tsx
E2E: UI workflow → e2e/test/scenarios/<category>/foo.cy.spec.ts
Use Grep to search for existing tests related to the buggy function/component. Consult CLAUDE.md in the source worktree for test conventions.
Choose Test Approach
Backend (Clojure):
| Root Cause Type | Test Approach |
|---|---|
| Query processor bug | mt/process-query or qp/process-query |
| API endpoint bug | mt/user-http-request |
| Model / data bug | mt/with-temp + t2/select |
| Pure logic / edge case | Direct function call with specific inputs |
Frontend (TypeScript):
| Root Cause Type | Test Approach |
|---|---|
| Component rendering bug | Jest + React Testing Library — render component, assert DOM |
| User interaction bug | Cypress — visit page, interact, assert visible result |
| Data display / formatting | Jest unit test on the formatting/transform function |
| State management bug | Jest — test reducer/action/selector with specific inputs |
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 · 93 lines · 62 tokens per session scan A 89a650bb44fb
write-test is a skill published in the GitHub repository metabase/repro-bot (10 stars, last pushed 5mo ago), licensed MIT. It adds 62 tokens to every session and 1,314 once invoked, about $0.0003 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…