agentleFS
Sign inStart free
LazyIsEfficientLazyIsEfficient/agentic-os/.claude/skills/security-engineering/SKILL.md

security-engineering

Skill17 starsChanged 22 days agoMITView on GitHub

Cross-stack security review — auditing vulnerabilities across infrastructure, smart contracts, CI/CD pipelines, and AI agent systems, plus auth/sessions/crypto and validating user input at API and infrastructure boundaries. Triggers on mentions of "vulnerability", "pentest", "OWASP", "access control", "injection", "CSRF", "JWT", "smart contract audit", "supply chain", "OIDC", or any review of security-sensitive code paths spanning more than one layer. For PII sanitization see [security](../security/SKILL.md).

  • Reads credentials

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 3 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:

    When reviewing code, think like a senior security researcher: trace user input through to sensitive operations, prefer fail-closed designs, …

    line 22

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

Cross-stack security rules covering API security, infrastructure hardening, Web3 smart contracts, CI/CD review automation, and agentic AI risks. Aligned to OWASP Top 10:2025, ASVS 5.0, and OWASP Agentic Security Initiative 2026.

When reviewing code, think like a senior security researcher: trace user input through to sensitive operations, prefer fail-closed designs, and never trust the client.

Universal Rules

  • Validate every input server-side with Zod (or equivalent) at the API boundary.
  • Parameterize all queries — Prisma/Drizzle, never string concatenation.
  • Authorize on every request — deny by default, verify ownership.
  • Hash passwords with Argon2 or bcrypt — never MD5/SHA1, never plaintext.
  • No hardcoded secrets — env vars validated at startup, secrets in vault, .env in .gitignore.
  • TLS everywhere, encryption at rest on all data stores.
  • Fail-closed on auth/permission errors. Never expose stack traces to users.
  • Log security events with sanitization — redact authorization, cookie, CSRF headers.
  • Least-privilege IAM — scope to specific actions and resource ARNs, not *.
  • OIDC for CI/CD — no long-lived credentials in GitHub.
  • Smart contracts: ReentrancyGuard, SafeERC20, signed data must include chainid + address(this) + deadline, replay-prevention via usedHashes.

References

  • references/owasp-top-10.md — OWASP Top 10:2025 quick reference table
  • references/cicd-security.md — CI/CD security review methodology, scanned vulnerability categories, supply-chain check
  • references/api-security.md — auth patterns, Zod validation, rate limiting, CORS, headers, log sanitization, error handling
  • references/infrastructure-security.md — VPC isolation, Cloudflare Zero Trust, secrets management, encryption, IAM principles
  • references/web3-smart-contracts.md — required patterns, signature verification, on-chain rate limits, audit findings, Slither
  • references/code-review-checklist.md — full checklist by category (input, auth, access control, data, errors, Web3)
  • references/secure-code-patterns.md — SQLi, command injection, access control, fail-closed, password storage examples
  • references/agentic-ai-security.md — OWASP 2026 ASI01-10 + agent security checklist
  • references/asvs-5.md — L1/L2/L3 requirements
  • references/language-specific.md — JS/TS, Solidity, Python, Go, Bash risks + deep analysis mindset

Related skills

  • web3-smart-contract-engineering — Solidity patterns, signature verification, replay protection (consult alongside references/web3-smart-contracts.md when auditing contracts)
  • deployment-pipelines — pipeline hardening, OIDC, untrusted-input handling in CI
  • godot-engineer (games pack) — multiplayer games have real security concerns: cheating, save tampering, server-side validation, anti-replay. Pull this in for any networked game.

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.

Check your setup, free