agentleFS
ku5icku5ic/claude-kit/skills/security-patterns/SKILL.md

security-patterns

Skill2 starsChanged 8 days agoMITView on GitHub

Security checklist covering XSS, injection, authentication, authorization, sessions, CSRF, CSP, secrets, dependency CVEs, input validation, and severity calls. Use when writing or reviewing code that handles auth, sessions, secrets, user input, or external data, or when the user asks about security, hardening, vulnerabilities, authentication, authorization, cookies, XSS, CSRF, SQL injection, CSP, or headers, even if "security" is not mentioned by name. Not loaded just because a project has such code.

9 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use security-fuzzing and security-payloads.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • EyadkellehSkill

    security-fuzzing

    Essential fuzzing payloads: SQL injection, command injection, special characters. Curated essentials for vulnerability testing.

    Also in 3 projects that use this

  • EyadkellehSkill

    security-payloads

    Essential exploitation payloads: anti-virus test files, file name exploits, malicious files. Curated for testing.

    Also in 3 projects that use this

The file

Files
SKILL.md

Security patterns

Apply the references that match the detected stack. Severity rubric below applies cross-cuttingly.

Severity rubric

  • failure: exploitable, or direct leak of credentials, or missing CSRF on authenticated mutating endpoint.
  • warning: mitigated but weak (e.g. CSP present but with unsafe-inline), or pattern that will become exploitable if misused.
  • info: hardening opportunity, not currently exploitable.

Reference files

FileCovers
reference/anti-patterns.mdCross-cutting severity-labeled anti-patterns: SQLi, XSS injection, CSRF, secrets
reference/frontend.mdXSS, Next.js client/server boundary, auth/sessions, JWT vs sessions, strict CSP (nonce/strict-dynamic/hash)
reference/backend-django.mdORM safety, views/middleware, auth, templates, file uploads
reference/backend-node.mdExpress/Fastify/Nest hardening, CSRF on JSON-only APIs
reference/dependencies.mdLockfile audit vs OSV-Scanner, SLSA build levels
reference/secrets.mdDetection (gitleaks, trufflehog, push protection), rotation cadence

References

Version notes

Checked: 2026-09-26 against https://slsa.dev/spec/v1.2/build-track-basics, https://docs.djangoproject.com/en/stable/ref/csp/, https://docs.npmjs.com/cli/v12/commands/npm-audit

  • SLSA 1.2: current spec; 1.0 retired. Build track is L0 (no requirements) through L3.
  • Django 6.0: built-in CSP middleware (SECURE_CSP, csp_nonce); 6.1 adds the {% csp_nonce_attr %} tag.
  • npm 12 (12.1.0): current CLI docs; v10 and v11 docs marked Legacy.

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.