adversarial-pr-review SKILL.md skillA
adversarial-pr-review from tomzx/agents is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tomzx/agents/adversarial-pr-review@git:20261028.55f5073Pins git:20261028.55f5073 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tomzx/agents
- Path
skills/adversarial-pr-review/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261028.55f5073, committed Oct 28, 2026
- Size
- 23,442 bytes
- Repository stars
- 14
- License
- MIT
Adversarially attack a GitHub pull request by finding the most likely ways the change breaks, then trying to make each one happen and reporting what was reproduced. Unlike static review it may execute throwaway probes outside the repo to reach L3 - Executed or L4 - Reproduced. Use when the user asks "how could this PR break", "red team this PR", "adversarial review this PR", "attack this change", "find failure modes", "verify this failure is possible", "what is the worst case for this PR", or…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Adversarial PR Review Answers the **adversarial** question: "what is the most likely way this change breaks, and can I make it break?" It assumes the change is broken and works to prove it, instead of checking that it does what it claims. It complements the other review steps and does not replace them: | Skill | Question | Evidence ceiling | |---|---|---| | `/review-pr` | Is the code well built? | `L2 - Ruled out` (static) | | `/verify-pr` | Does the accepted behavior work? | `L4 - Reproduced` | | `/validate-pr` | Is this the right product? | `L2 - Ruled out` (static plus issue reading) | | `/adversarial-pr-review` | Which plausible failure happens, and can I reproduce it? | `L4 - Reproduced` | Its contribution is adversarial reproduction: a ranked list of failure scenarios where the decisive ones were actually executed against the PR's code. A suspicion that was never tried is reported as unproven, never as a failure. ## Prerequisites - Apply the shared SDLC conventions in `skills/sdlc/references/shared.md` (PR Review Reports for report location and posting rules). …
Read the whole file at its exact version.
How to install
mdr add tomzx/agents/adversarial-pr-review@sha256:0df4078200d3e729The line at the top of this page pins the label git:20261028.55f5073, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_p6dzuoxgjcfinvxp)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 28, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (23442 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
tomzx/agents · 14 stars · license MIT · pushed 2026-10-28 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_p6dzuoxgjcfinvxp GET https://markdownregistry.com/api/v1/resolve?ref=tomzx/agents/adversarial-pr-review GET https://markdownregistry.com/api/v1/blob/0df4078200d3e729ee40df662ce0538b8d16ad496d5150735454c5d7f0d95fb3
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.