agentleFS
Gaurav890Gaurav890/everything-agentic-engineering/.claude/skills/security-gate/SKILL.md

security-gate

Skill1 starsChanged 2 months agoMITView on GitHub

Perform a structured security gate before merging sensitive changes, covering threat model, auth/authz, secrets, injection, SSRF, uploads, webhooks, MCP/browser permissions, dependencies, and verification.

4 other projects use a version of this.

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, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No finding without evidence.

    line 59

“Common” is measured: kept by at least 6 in 10 of the 4 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 gate

1. Classify risk

High-risk examples:

  • auth/authz,
  • payments,
  • secrets,
  • user-generated files,
  • webhooks,
  • admin actions,
  • production data,
  • arbitrary URLs,
  • AI tool execution,
  • browser session reuse,
  • MCP write tools.

2. Threat model

Identify:

  • assets,
  • actors,
  • entry points,
  • trust boundaries,
  • privileged operations,
  • abuse cases.

3. Review

Check:

  • authentication,
  • authorization/object ownership,
  • validation and encoding,
  • injection,
  • SSRF/open redirect,
  • CSRF/CORS where relevant,
  • file/path traversal,
  • upload limits/type validation,
  • webhook signatures/replay,
  • secret leakage,
  • logs/PII,
  • dependency risk,
  • rate limiting/abuse,
  • MCP permissions,
  • prompt injection.

4. Rank findings

  • P0 critical
  • P1 high
  • P2 medium
  • P3 low

No finding without evidence.

5. Verify fixes

Re-run the exploit path or failure case after remediation.

6. Record

Update:

  • docs/30-engineering/SECURITY_MODEL.md
  • docs/50-evals/SECURITY_EVIDENCE.md
  • docs/40-execution/RISKS.md when unresolved.

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.