agentleFS
hugobatistahugobatista/agent-skills/skills/review/security-reviewer/SKILL.md

security-reviewer

Skill1 starsChanged 58 days agoMITView on GitHub

Use when performing security-focused code reviews, threat modeling, or assessing OWASP Top 10 / LLM security risks. Covers Zero Trust and enterprise security standards.

35 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use api-contract-reviewer, ddd-architect and 10 more.

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.
  • conectlensSkill

    api-contract-reviewer

    Review Supabase RPC/PostgREST API contracts for DTO correctness, response consistency, validation quality, and backward-compatibility risk. Use when changing libs/api/*, shared response types, or API-facing behavior.

    Also in 4 projects that use this

  • u9401066Skill

    ddd-architect

    Ensure code follows DDD architecture and DAL separation principles. Triggers: DDD, arch, 架構, 新功能, 新模組, new feature, scaffold, 骨架, domain.

    Also in 4 projects that use this

  • JohnJBorenSkill

    test-engineer

    Testing strategy, test patterns, and coverage optimization for unit, integration, and E2E tests

    Also in 3 projects that use this

  • u9401066Skill

    test-generator

    Generate comprehensive test suites including static analysis, unit tests, integration tests, E2E tests, and coverage reports. Triggers: TG, test, 測試, 寫測試, coverage, 覆蓋率, pytest, unittest, 驗證.

    Also in 3 projects that use this

  • victoralbinoSkill

    spec-writer

    Activity planning via deep interview. Use when the user asks to plan, specify, or detail any activity. Accepts an existing file or a direct description. Interviews with AskUserQuestion and writes the final spec.

    Also in 3 projects that use this

  • StrayDragonSkill

    ui-ux-pro-max

    UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.

    Also in 8 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 32 edited versions we read keep these.

  • 2

    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:

    Check for these (see OWASP Top 10):

    line 40
  2. Distinctive:

    Every request must be authenticated and authorized regardless of network origin.

    line 53

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

Prevent production security failures through comprehensive security review.

Your Mission

Review code for security vulnerabilities with focus on OWASP Top 10, Zero Trust principles, and AI/ML security (LLM and ML specific threats).

Step 0: Create Targeted Review Plan

Analyze what you're reviewing:

  1. Code type?
    • Web API -> OWASP Top 10
    • AI/LLM integration -> OWASP LLM Top 10
    • ML model code -> OWASP ML Security
    • Authentication -> Access control, crypto
  2. Risk level?
    • High: Payment, auth, AI models, admin
    • Medium: User data, external APIs
    • Low: UI components, utilities
  3. Business constraints?
    • Performance critical -> Prioritize performance checks
    • Security sensitive -> Deep security review
    • Rapid prototype -> Critical security only

Create Review Plan:

Select 3-5 most relevant check categories based on context.

Step 1: OWASP Top 10 Security Review

Check for these (see OWASP Top 10):

  • A01 - Broken Access Control: Missing auth, IDOR, privilege escalation. Verify authorization on every endpoint, not just authentication.
  • A02 - Cryptographic Failures: Weak hashes (MD5, SHA1), hardcoded secrets, missing TLS. Use scrypt/bcrypt/argon2 for passwords; env vars for secrets.
  • A03 - Injection: SQL, NoSQL, command, template injection. Use parameterized queries, ORMs, input sanitization. Never interpolate user input.

Step 1.5: OWASP LLM Top 10 (AI Systems)

  • LLM01 - Prompt Injection: Sanitize user input before LLM prompts. Isolate instructions from user content with clear delimiters.
  • LLM06 - Information Disclosure: Strip PII/sensitive data from LLM context. Filter outputs before returning to user.

Step 2: Zero Trust Implementation

Every request must be authenticated and authorized regardless of network origin. Validate all inputs, verify service tokens on internal APIs, apply least-privilege access.

Step 3: Reliability

External calls need timeouts, retries with exponential backoff, and circuit breakers. Handle network failures and non-2xx responses explicitly.

Document Creation

After Every Review, CREATE:

Code Review Report - Save to docs/code-review/[date]-[component]-review.md

  • Include specific code examples and fixes
  • Tag priority levels
  • Document security findings

Report Format:

# Code Review: [Component]
**Ready for Production**: [Yes/No]
**Critical Issues**: [count]

## Priority 1 (Must Fix) :no_entry:
- [specific issue with fix]

## Recommended Changes
[code examples]

Remember: Goal is enterprise-grade code that is secure, maintainable, and compliant.

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.