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 petrkindlmann/qa-skills --skill bug-reproductiongit clone --depth 1 https://github.com/petrkindlmann/qa-skillsWrote 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/petrkindlmann/qa-skills/bug-reproduction)<a href="https://agentmods.dev/skills/petrkindlmann/qa-skills/bug-reproduction"><img src="https://agentmods.dev/badge/skills/petrkindlmann/qa-skills/bug-reproduction/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/petrkindlmann/qa-skills/bug-reproduction"><img src="https://agentmods.dev/badge/skills/petrkindlmann/qa-skills/bug-reproduction.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- 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.00252 | $0.06064 |
| Opus 5.5 | $0.00101 | $0.02426 |
| Sonnet 5.5 | $0.00050 | $0.01213 |
| Haiku 4.5 | $0.00025 | $0.00606 |
Grade A, and why
bug-reproduction 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 4d 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 — 430 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick Route
| You have… | Go to |
|---|---|
| A thin report and no idea how to trigger it | Step 1: Extract the implicit repro |
| A messy 14-step repro to clean up | Step 2: The reproduce-minimize-isolate-capture loop |
| "Worked last month, broken now" | Step 3: Bisect to the introducing commit |
| A repro that passes/fails inconsistently | Step 4: Make the repro deterministic |
| A clean repro, no fix yet | Step 5: Write the failing regression test (red) first |
| "The dev says it's fixed, test is green" | Step 6: Verify the fix actually fixes it |
| "It won't reproduce for me but does for the user" | Step 7: Flaky vs environment vs not-reproducible |
| Repro + test done | Step 8: Write the evidence back into the ticket |
Discovery Questions
First, check .agents/qa-project-context.md in the project root — it carries the tech
stack, test runner, known-flaky areas, and environment matrix. Pass over any question it
already answers. If it is missing, suggest creating one with the qa-project-context skill; an
unfilled template answers nothing, so treat it as missing.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago Changed · +19 lines 7ffa5d3d0c25
- 1mo ago First seen · 411 lines · 252 tokens per session scan A 617d59812df6
bug-reproduction is a skill published in the GitHub repository petrkindlmann/qa-skills (214 stars, last pushed 5d ago), licensed MIT. It adds 252 tokens to every session and 6,064 once invoked, about $0.0010 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 skills, from other repositories
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
hotpath_init_ci_forks
Set up the hotpath Cloud CI integration in a public Rust project that benchmarks pull requests from forks. Adds the hotpath-cloud feature, a regression policy file, a GitHub Actions benchmark workflow that writes hotpath reports as artifacts and a relay workflow that uploads them, so every pull request, forks…
hotpath_init_ci
Set up the hotpath Cloud CI integration in a Rust project whose pull requests come from branches of the same repository (private repositories, or public ones that do not benchmark fork pull requests). Adds the hotpath-cloud feature, a regression policy file and a GitHub Actions benchmark workflow that uploads hotpath…
CI Pipeline Optimizer
Optimize CI test pipelines through intelligent test splitting, parallelization, caching strategies, and selective test execution based on code changes.
Flaky Test Quarantine
Detect, quarantine, and systematically fix flaky tests with automated retry analysis, root cause categorization, and CI pipeline integration for test reliability.
CI/CD Pipeline Advanced
Expert-level CI/CD pipeline skill for test automation. Covers GitHub Actions, Jenkins, GitLab CI, Azure DevOps, parallel execution, matrix strategies, caching, artifact management, and deployment gates.