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.
git clone --depth 1 https://github.com/davekilleen/DexWrote 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/davekilleen/dex/reproduce-bug)<a href="https://agentmods.dev/commands/davekilleen/dex/reproduce-bug"><img src="https://agentmods.dev/badge/commands/davekilleen/dex/reproduce-bug/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/davekilleen/dex/reproduce-bug"><img src="https://agentmods.dev/badge/commands/davekilleen/dex/reproduce-bug.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.00020 | $0.00713 |
| Opus 5.5 | $0.00008 | $0.00285 |
| Sonnet 5.5 | $0.00004 | $0.00143 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
reproduce-bug 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- reproduce-bug — 94% identical, 1 lines differ
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reproduce Bug Command
Look at github issue #$ARGUMENTS and read the issue description and comments.
Phase 1: Log Investigation
Run the following agents in parallel to investigate the bug:
- Task rails-console-explorer(issue_description)
- Task appsignal-log-investigator(issue_description)
Think about the places it could go wrong looking at the codebase. Look for logging output we can look for.
Run the agents again to find any logs that could help us reproduce the bug.
Keep running these agents until you have a good idea of what is going on.
Phase 2: Visual Reproduction with Playwright
If the bug is UI-related or involves user flows, use Playwright to visually reproduce it:
Step 1: Verify Server is Running
mcp__plugin_compound-engineering_pw__browser_navigate({ url: "http://localhost:3000" })
mcp__plugin_compound-engineering_pw__browser_snapshot({})
If server not running, inform user to start bin/dev.
Step 2: Navigate to Affected Area
Based on the issue description, navigate to the relevant page:
mcp__plugin_compound-engineering_pw__browser_navigate({ url: "http://localhost:3000/[affected_route]" })
mcp__plugin_compound-engineering_pw__browser_snapshot({})
Step 3: Capture Screenshots
Take screenshots at each step of reproducing the bug:
mcp__plugin_compound-engineering_pw__browser_take_screenshot({ filename: "bug-[issue]-step-1.png" })
Step 4: Follow User Flow
Reproduce the exact steps from the issue:
-
Read the issue's reproduction steps
-
Execute each step using Playwright:
browser_clickfor clicking elementsbrowser_typefor filling formsbrowser_snapshotto see the current statebrowser_take_screenshotto capture evidence
-
Check for console errors:
mcp__plugin_compound-engineering_pw__browser_console_messages({ level: "error" })
Step 5: Capture Bug State
When you reproduce the bug:
- Take a screenshot of the bug state
- Capture console errors
- Document the exact steps that triggered it
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.
- 1mo ago First seen · 100 lines · 20 tokens per session scan A 950c240f55e2
reproduce-bug is a command published in the GitHub repository davekilleen/Dex (505 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 713 once invoked, about $0.0001 per session on Opus 5.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
performance-optimization
Orchestrate end-to-end application performance optimization from profiling to monitoring.
config-validate
Validate application configuration with schemas, per-environment rules, runtime checks, and secure handling of sensitive values.
smart-debug
AI-assisted smart debugging — parse error messages, stack traces, and failure patterns to identify root causes and produce a fix with automated observability steps.
verify-loop
A command that repeatedly checks recent code changes and tries to fix failures, with a configurable retry limit. It can run code review, builds, tests, linting, and type checks according to the project language.
browser-debug
A command for starting Yandex Browser with remote debugging enabled. Remote debugging lets developer tools connect to a running browser through the Chrome DevTools Protocol, a standard interface for inspecting web pages.
build-fix
A build-error fixing procedure for TypeScript projects. It runs the project build, groups and explains errors, applies fixes one at a time, and checks the build again.