Individual skill

secure-code-review

The sinks and boundaries that belong to no framework: passing input to a shell or an evaluator, letting input choose a filesystem path, validating at a boundary that is not an HTTP request, and handling regulated data (PII, PHI, cardholder data) so it does not spread into paths nobody reviews. Use when generating or reviewing code that shells out, touches the filesystem, reads a queue message, CLI argument, or parsed file, or when a change crosses a PII, PHI, or PCI boundary.

skills/secure-code-review/SKILL.md

Read pinned source

Source commit eaba88102d91df65a9aa6397e8507c315c018f5e

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Network or broad shell
Last checked: Nov 6, 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.

Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.

Repository context

Repository stars (not skill ratings): 23
Repository last updated: Aug 14, 2026
License: MIT

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

claude-skills Repository topic
llm Repository topic
security Repository topic
skills Repository topic
data Derived category

Files and excerpt

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

Browse files

SKILL.mdcore · 7,379 bytes
checklists/injection_patterns.yamlasset · 1,941 bytes
checklists/owasp_top10.yamlasset · 2,653 bytes
references/verifying-compliance-findings.mddoc · 3,971 bytes
references/verifying-findings.mddoc · 3,310 bytes
tests/corpus.jsonasset · 4,230 bytes

Read excerpt


# Secure Code Review

## Rules (for AI agents)

### ALWAYS
- Validate input at **every** trust boundary, not only the HTTP one. A CLI argument, an
  environment variable, a queue message, a filename, a parsed config or spreadsheet
  cell all arrive from outside and none of them pass through the request-validation
  layer. Check type, length, allowed characters and allowed range, and reject before
  processing. `api-security` owns the HTTP request body and its schema; this rule is
  every other way input gets in.
- Build a command as an **argument vector**, never as a string a shell will parse:
  `subprocess.run([...])` without `shell=True`, `execFile`/`spawn` with an array,
  `exec.Command(name, args...)`. Passing an array is what removes the shell, and