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 skills add tomzx/agents --skill reproduce-issuegit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/reproduce-issue)<a href="https://agentmods.dev/skills/tomzx/agents/reproduce-issue"><img src="https://agentmods.dev/badge/skills/tomzx/agents/reproduce-issue/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/skills/tomzx/agents/reproduce-issue"><img src="https://agentmods.dev/badge/skills/tomzx/agents/reproduce-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00033 | $0.02402 |
| Opus 5 | $0.00016 | $0.01201 |
| Sonnet 5 | $0.00007 | $0.00480 |
| Haiku 4.5 | $0.00003 | $0.00240 |
Grade A, and why
reproduce-issue 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: Bash(gh:*, git:*, ghx:*, asciinema:*, agg:*, npx:*, node:*, uv:*, python:*, python3:*, curl:*, ~/.agents/scripts/get-env:*), Read, Write, Edit, Glob, Grep How it starts
The opening of the file, as written. The whole thing — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reproduce Issue
Takes a GitHub issue that describes a bug, creates a git worktree on a fix branch, and attempts to reproduce the reported behavior. Posts the reproduction results as a comment on the issue.
Assumes check-duplicates has already been run to verify no duplicates or existing fix PRs.
This skill stops after reproduction. Use fix-issue to continue with the fix, or
call create-implementation directly if the issue is already reproduced.
Prerequisites
- Apply the shared SDLC conventions in
skills/sdlc/references/shared.md. - If no argument is provided, target the issue from
$ISSUE_NUMBER(and$REPO). ghCLI authenticated with write access to the target repository- A GitHub issue number describing a bug
- Git worktree support (
git worktreeavailable) - Read any files present under
.sdlc/context/and apply any artifact style rules found there - For before/after visual proof (optional, best-effort):
asciinema+ renderer for CLI bugs, or Playwright for web UI bugs. If unavailable, the recording step is skipped silently.
Skill attribution (GitHub)
Before posting to GitHub, read ../github-post-attribution/SKILL.md and append the footer for SKILL_DIR = reproduce-issue.
Workflow
Fetch bug report issue
|
v
Create git worktree on fix branch
|
v
Analyze issue + explore codebase
|
v
Attempt to reproduce
|
v
Bug reproduced?
/ \
Yes No
| |
v v
Record before Post comment
(if surface (unable to reproduce,
classifiable) ask for details)
|
v
Post comment
(reproduced,
ready to fix)
Steps
1. Fetch the bug report
Fetch the issue details to understand the bug:
ghx issue view $ISSUE_NUMBER --repo $REPO
Extract from the issue:
- Expected behavior
- Actual behavior
- Steps to reproduce
- Environment details (version, OS, etc.)
- Error messages, stack traces, or logs
- Any labels that indicate severity or area
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 · 263 lines · 33 tokens per session scan A 62faa24d05ca
reproduce-issue is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 2,402 once invoked, about $0.0002 per session on Opus 5. 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-09-03.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.