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/marcusrbrown/systematic/reproduce-bugnpx skills add marcusrbrown/systematic --skill reproduce-buggit clone --depth 1 https://github.com/marcusrbrown/systematicWrote 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/skills/marcusrbrown/systematic/reproduce-bug)<a href="https://agentmods.dev/skills/marcusrbrown/systematic/reproduce-bug"><img src="https://agentmods.dev/badge/skills/marcusrbrown/systematic/reproduce-bug.svg" alt="Measured on agentmods" 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.00039 | $0.01809 |
| Opus 5 | $0.00019 | $0.00905 |
| Sonnet 5 | $0.00008 | $0.00362 |
| Haiku 4.5 | $0.00004 | $0.00181 |
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 6d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reproduce Bug
A framework-agnostic, hypothesis-driven workflow for reproducing and investigating bugs from issue reports. Works across any language, framework, or project type.
Phase 1: Understand the Issue
Fetch and analyze the bug report to extract structured information before touching the codebase.
Fetch the issue
If no issue number or URL was provided as an argument, ask the user for one before proceeding (using the platform's question tool -- e.g., question in OpenCode, request_user_input in Codex, ask_user in Gemini; in Pi, use the blocking-question extension if available, otherwise present numbered options in chat and wait -- or present a prompt and wait for a reply).
gh issue view $ARGUMENTS --json title,body,comments,labels,assignees
If the argument is a URL rather than a number, extract the issue number or pass the URL directly to gh.
Extract key details
Read the issue and comments, then identify:
- Reported symptoms -- what the user observed (error message, wrong output, visual glitch, crash)
- Expected behavior -- what should have happened instead
- Reproduction steps -- any steps the reporter provided
- Environment clues -- browser, OS, version, user role, data conditions
- Frequency -- always reproducible, intermittent, or one-time
If the issue lacks reproduction steps or is ambiguous, note what is missing -- this shapes the investigation strategy.
Phase 2: Hypothesize
Before running anything, form theories about the root cause. This focuses the investigation and prevents aimless exploration.
Search for relevant code
Use the native content-search tool (e.g., Grep in OpenCode) to find code paths related to the reported symptoms. Search for:
- Error messages or strings mentioned in the issue
- Feature names, route paths, or UI labels described in the report
- Related model/service/controller names
Form hypotheses
Based on the issue details and code search results, write down 2-3 plausible hypotheses. Each should identify:
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.
- 6d ago First seen · 196 lines · 39 tokens per session scan A 8dd8887071ee
reproduce-bug is a skill published in the GitHub repository marcusrbrown/systematic (24 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 1,809 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-30.
Other skills, from other repositories
ai-slop-cleaner
Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode.
smiles-validation
Strict SMILES validation, structural comparison, and modification verification. Catches invalid LLM-generated molecules.
perf-theory-gatherer
Use when generating performance hypotheses backed by git history and code evidence.
lcx-report-bug
Create a high-signal bug issue or PR in the repo that owns the defect. Use this whenever the user asks to report, file, open, or triage a LazyCodex, lazycodex-ai, omo-codex, Codex plugin, or upstream Codex CLI bug, especially when they need source-backed root cause, reproduction steps, fix guidance, and GitHub routing.
ast-grep
Searches and rewrites code by AST shape across 25 languages. Use when the target is a syntax pattern (every call/class/import shaped like X, a codemod, a YAML rule) rather than literal text; for plain strings, comments, or filenames, use rg.
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits. Triggers: remove dead code, dead code, cleanup, remove unused.