security-review SKILL.md skillA
security-review from patrickserrano/lacquer is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add patrickserrano/lacquer/security-review@git:20260712.d1d6fcaPins git:20260712.d1d6fca in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- patrickserrano/lacquer
- Path
core/skills/security-review/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260712.d1d6fca, committed Jul 12, 2026
- First version recorded
- Jul 8, 2026
- Size
- 2,888 bytes
- Repository stars
- 5
- License
- MIT
Adversarial security review of a change (branch diff, PR, or working tree) before merge. Use when the user asks to "review this for security", "security review", "check for vulnerabilities", "is this safe to merge", or before merging anything that touches a trust boundary — auth/authz, input parsing, secrets/keychains, file writes, shelling out, untrusted-input-into-shell/YAML, CI workflows that run on privileged runners, or generated LLM instructions. Also the standing gate this repo runs on…
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
Review the change adversarially — assume the diff is hostile until proven safe. Report only findings you can tie to a concrete failure scenario; do not pad with generic advice. ## Scope the diff 1. Establish the base: `git diff <base>...HEAD` for a branch, `gh pr diff <n>` for a PR, or `git diff` for the working tree. Read enough surrounding context to judge each hunk — never review a hunk in isolation. 2. If the change is large, fan out: one reviewer per trust boundary (auth, input parsing, secrets, CI/exec, file I/O), then dedupe. A single pass misses cross-cutting issues. ## What to hunt for - **Injection**: untrusted input (user data, `github.event.*`, PR titles/branch names, file contents, tool output, dependency changelogs) reaching a shell, `eval`, SQL, YAML, or an LLM instruction context. Trace the value from source to sink; quote both. - **Path/traversal & symlink**: writes that can escape a root, TOCTOU between check and write, following a symlink, absolute paths sneaking in through a config field. - **Secrets**: keys/tokens echoed, written to files that become artifacts, passed on a …
Read the whole file at its exact version.
How to install
mdr add patrickserrano/lacquer/security-review@sha256:160dfedbdb22deb2The line at the top of this page pins the label git:20260712.d1d6fca, 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_7tam265jbq6jtths)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jul 8, 2026 and Jul 12, 2026, about one every 5 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260712.d1d6fca latest | 2026-07-12 | d1d6fca | 2,888 B | A | view · diff |
| git:20260708.cd5aa36 | 2026-07-08 | cd5aa36 | 2,888 B | A | view |
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 (2888 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
patrickserrano/lacquer · 5 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7tam265jbq6jtths GET https://markdownregistry.com/api/v1/resolve?ref=patrickserrano/lacquer/security-review GET https://markdownregistry.com/api/v1/blob/160dfedbdb22deb240a3fc3d57595eb2b3e6fde57e053f930f75de43584a1b34
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.
More from patrickserrano/lacquer
Every file in patrickserrano/lacquer