Skip to content
SkillModel-led653 tokens in use

reproduce-bug

The reproduction stage of patching-bugs: build the baseline, exercise the named bug with a PoC or compiler run, and save the raw receipts.

8,319 stars on the repository CC-BY-SA-4.0trailofbits/skills · plugins/patching-bugs/skills/reproduce-bug
/plugin marketplace add trailofbits/skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing reproduce-bug costs

21tokens idle
653tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter12/15
  • Structure23/25
  • Examples6/15
  • Output2/15
  • Size11/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity100
  • Maintenance52
  • Community64
  • Maturity32
  • Momentum40

Reproduce-bug takes one finding and a local baseline checkout and tries to make the bug happen before anything is edited. For a runtime bug it builds the project and runs a proof of concept against the built artifact. For a compile failure it records the target compiler diagnostic from the failed invocation.

The agent saves raw stdout, stderr, exit status and timing, writes a reproduce record with the outcome (reproduced, not reproduced or blocked), updates the finding status and writes a manifest of the whole step directory.

What You Get

  • A reproduce.json with baseline commit, command argument arrays, artifact path, observed result, outcome and agent identity
  • An unchanged PoC saved under reproduce/poc for later stages
  • Raw receipts for the build and each run
  • A manifest and a record check before handoff

Common Use Cases

  • Confirming that a reported runtime crash or path-escape happens on the current baseline
  • Capturing the exact compiler diagnostic for a reported build failure
  • Reporting a blocker when setup cannot exercise the claim

What Makes It Unique

A unit test that imitates the bug does not count. A runtime PoC must record that it loaded the built artifact and print PATCH_REACHED right before the assertion, and a nonzero exit alone is not accepted as proof. A compile case needs the target diagnostic.

Under The Hood

The agent reads SKILL.md and a record contract, reads project guidance files from Git objects, runs the project’s own build command and the PoC it writes, and saves outputs into a run directory. It uses a bundled Python helper through uv to write the manifest and check records. It writes files only inside the run directory, and its commands are those of the project under test.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers