repro-issue

repro-issue is a skill for Claude Code, Codex from Jmsa/argus. It costs 44 tokens per session (667 once invoked), scanned A, original, MIT.

A workflow for reproducing bugs while controlling the API responses a website receives.

In plain words
What is it for?
Reproducing frontend bugs, recording network requests and console errors, taking screenshots, and testing different API responses.
Why use it?
Changing mocked responses helps show whether a failure comes from the page interface or from particular data returned by an API.

Skill for Claude CodeCodex

Part of the argus plugin — 6 skills, 1 MCP server shipped together

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 skills/jmsa/argus/repro-issue
Any agent
npx skills add Jmsa/argus --skill repro-issue
Clone the repo
git clone --depth 1 https://github.com/Jmsa/argus

Made for: Claude Code, Codex.

Or install argus, the plugin that ships this one along with the rest of its 6 skills, 1 MCP server.

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.

agentmods badge for repro-issue

README.md
[![agentmods](https://agentmods.dev/badge/skills/jmsa/argus/repro-issue.svg)](https://agentmods.dev/skills/jmsa/argus/repro-issue)
Your own site
<a href="https://agentmods.dev/skills/jmsa/argus/repro-issue"><img src="https://agentmods.dev/badge/skills/jmsa/argus/repro-issue.svg" alt="Measured on agentmods" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 667 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.

ModelPer sessionOnce invoked
Fable 5 $0.00044 $0.00667
Opus 5 $0.00022 $0.00333
Sonnet 5 $0.00009 $0.00133
Haiku 4.5 $0.00004 $0.00067

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

Security

Grade A, and why

repro-issue 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.

skills/repro-issue/SKILL.md · 79 lines

How it starts

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

Reproduce and isolate the following issue using Argus: $ARGUMENTS

Steps

  1. Launch and set up recording

    browser_launch
    tab_open { url: "about:blank" }
    console_start { targetId }
    network_start_recording { targetId }
    
  2. Add mocks for controlled API responses

    network_add_mock {
      targetId,
      urlPattern: "**/api/endpoint",
      responseCode: 200,
      responseBody: '{"key": "value"}',
      responseHeaders: { "content-type": "application/json" }
    }
    
    • Use ** to match any prefix/suffix
    • Mock the API state expected to trigger the bug
  3. Navigate and trigger the issue

    tab_navigate { targetId, url: "https://your-site.com/path" }
    page_evaluate { targetId, expression: "document.querySelector('.submit-btn').click()" }
    
  4. Capture failure evidence

    console_get_logs { targetId, type: "error" }
    network_get_requests { targetId, hasError: true }
    tab_screenshot { targetId, fullPage: true }
    
  5. Iterate mocks to find the root cause

    • Remove the mock: network_remove_mock { targetId, mockId }
    • Add a different mock with different data
    • Reload and check if the bug disappears: page_reload { targetId }
    • Compare screenshots and logs to pinpoint the problematic state
  6. Verify the fix

    network_clear_mocks { targetId }
    network_add_mock { targetId, urlPattern: "**/api/endpoint", responseCode: 200, responseBody: '{"fixed": true}' }
    page_reload { targetId }
    console_get_logs { targetId, type: "error" }   ← should be empty
    tab_screenshot { targetId }                     ← should show fixed state
    
  7. Report findings — include:

    • Which mock configuration reproduced the bug
    • Which change made it disappear
    • Screenshot evidence of both states
    • Recommended fix

Common Mock Patterns

Scenario Mock setup
Empty API response responseBody: '[]' or '{}'
API error responseCode: 500, responseBody: '{"error":"Internal Server Error"}'
Auth failure responseCode: 401, responseBody: '{"error":"Unauthorized"}'

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

  1. 2d ago First seen · 79 lines · 44 tokens per session scan A 3cd67cec9c0f

Subscribe to this mod's changes

repro-issue is a skill published in the GitHub repository Jmsa/argus (0 stars, last pushed 5mo ago), licensed MIT. It adds 44 tokens to every session and 667 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-31.

Related

Other skills, from other repositories

opencli-browser

Use when an agent needs to drive a real Chrome window via opencli — inspect a page, fill forms, click through logged-in flows, or extract data ad-hoc. Covers the selector-first target contract, compound form fields, stale-ref handling, network capture, and the agent-native envelopes the CLI returns. Not for writing…

jackwener/OpenCLI · 80 tokens

cloud

Documentation reference for using Browser Use Cloud — the hosted API and SDK for browser automation. Use this skill whenever the user needs help with the Cloud REST API (v2, v3, or v4), browser-use-sdk (Python or TypeScript), X-Browser-Use-API-Key authentication, cloud sessions, browser profiles, profile sync, CDP…

browser-use/browser-use · 177 tokens

opencli-sitemap-author

Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.

jackwener/OpenCLI · 67 tokens

pinchtab-mcp

Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.

pinchtab/pinchtab · 52 tokens

pinchtab-stealth-score

Run the PinchTab stealth-score sweep against 15 bot-detection / fingerprint sites (sannysoft, rebrowser, deviceandbrowserinfo, iphey, whoer, browserscan, pixelscan, fingerprint-scan, incolumitas, fvision, amiunique, browserleaks, creepjs, coveryourtracks, fingerprint-demo). Starts a Docker PinchTab container per…

pinchtab/pinchtab · 168 tokens

pinchtab-dev

Develop and contribute to the PinchTab project. Use when working on PinchTab source code, adding features, fixing bugs, running tests, or preparing PRs. Triggers on "work on pinchtab", "pinchtab development", "contribute to pinchtab", "fix pinchtab bug", "add pinchtab feature".

pinchtab/pinchtab · 77 tokens