agentleFS
rpraharajrpraharaj/ai-sdlc/skills/security-pass/SKILL.md

security-pass

Skill0 starsChanged 16 days agoMITView on GitHub

Threat-model this diff only — new reachable surface, authorization, injection, secrets, and PII. Use when the change touches auth, input, files, HTML, URLs, or secrets, when ready-to-merge dispatches it, or when the user asks for a security review of the change.

5 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Write references/security-template.md.

    line 41

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Security pass

Adversarial review of this delta. Do not edit product code unless they asked you to fix what you found.

Is this the right skill?

SignalDo this instead
Data classification of a changeclassify-data
Whole-company auditstop — this skill is the diff
Merge gateready-to-merge (it dispatches this)

Required inputs

  • The current diff
  • AGENTS.md

Human decisions (do not invent)

  • Broadening authz to “fix” a fail (forbidden)

Procedure

  1. Inventory new/changed reachable surfaces, trust boundaries, authz, secrets/PII. If empty, report no new reachable surface and still scan for leaked secrets.
  2. For each surface walk: authorization (IDOR), untrusted input to sinks, injection/traversal, SSRF, uploads, secrets, PII. Skip items the diff cannot hit.
  3. Severity: bug / suggestion / nit.
  4. Write references/security-template.md. Findings need file:line.

Output

  • Path: reply
  • Template: references/security-template.md

Quality bar

  • Inventory listed
  • Secrets pass or fail
  • No theoretical issue without a path from this change

Done

Pass | fail. Fixes are implement-change + write-tests.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.