Menu

Individual skill

security-review

0upvotes

Use when changes touch auth, parsing, dependencies, network, or pre-release, or a diff or baseline needs regression review, or the user asks for a security review, vulnerability audit, or OWASP review of a supplied file, diff, or component, covering injection, XSS, auth, or crypto, with high-confidence findings only (mode: confirmed), or an API, configuration schema, cryptographic interface, authentication surface, or library design is audited for misuse resistance or footguns at a caller-named target (mode: edges, inline or delegated specialist). Modes: full, differential, confirmed, edges. Not for adding controls: use security-hardening. Not for CodeQL analysis: use codeql-security-analysis.

.devin/skills/security-review/SKILL.md

Read pinned source

Source commit b0e8ce89a19fac880251dc3ea1babfeb4503a4fe

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
55
Repository last updated
Sep 28, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Security review

## Contract

| Field | Bound contract |
|---|---|
| Trigger | Changes touch auth, input parsing, dependencies, network I/O, or pre-release of a public-facing service; or a PR, commit, diff, or baseline is supplied for security regressions, blast radius, changed-code test gaps, or adversarial review of what changed; or the user asks for a security review, vulnerability audit, OWASP review, or review of injection, XSS, authentication, authorization, or cryptography of a supplied file, diff, or component (mode confirmed); or an API, configuration schema, cryptographic interface, authentication surface, or library design is questioned for misuse resistance, secure-by-default behavior, or footguns, inline or as a delegated specialist analysis (mode edges). |
| Authority | Reversible local. Write set: one review report file. Rollback: delete the report file. No remote mutation. Modes confirmed and edges are read-only: no file, VCS, credential, paid, published, deployed, or remote mutation; findings are reported in chat or returned to the delegating caller. |
| Side effect | A security-audit report; differential mode reads Git history for blame and regression checks and always writes the report file. No code edits; secret scanning reads and never mutates credentials. Modes confirmed and edges write nothing: the findings report is returned in the conversation or to the delegating caller. |
| Done | Full mode: audit report with STRIDE findings, OWASP walkthrough, supply-chain results, and severity contract (critical and high block merge). Differential mode: every in-scope change risk-classified at the declared depth, with evidence-backed findings, test gaps, blast radius, historical context, exploit paths where warranted, limitations, and a recommendation. Confirmed mode: only HIGH-confidence findings reported, each with attacker-controlled input confirmed, or a cleared report stating no high-confidence vulnerabilities were identified. Edges mode: security-relevant choice points checked across the seven edge cases with each reported edge carrying category, severity, location, reproducible misuse, and a misuse-resistant recommendation; specialist mode completes the four analysis phases with an exploitability determination per finding. |

## Not for

- Adding security controls during construction: use security-hardening.
Back to top