agentleFS
Sign inStart free
zackleconzacklecon/claude-skills/skills/security-reviewer/SKILL.md

security-reviewer

Skill3 starsChanged 10 months agoMITView on GitHub

Use when conducting security audits, reviewing code for vulnerabilities, or analyzing infrastructure security. Invoke for SAST scans, penetration testing, DevSecOps practices, cloud security reviews.

33 other projects use a version of this, 12 of them edited.

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

  • JetBrainsSkill

    slides

    Create and edit presentation slide decks (`.pptx`) with PptxGenJS and render/validation utilities. Use when tasks involve building a new PowerPoint deck, recreating slides from screenshots/PDFs/reference decks, modifying slide content while preserving editable output, adding charts/diagrams/visuals, or diagnosing layout issues such as overflow, overlaps, and font substitution.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 29 edited versions we read keep these.

  • 10

    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:

    Scan: - Run SAST, dependency, and secrets tools

    line 37
  2. Distinctive:

    Report: - Document findings with remediation guidance

    line 40
  3. Distinctive:

    Check authentication/authorization first

    line 58
  4. Distinctive:

    Run automated tools before manual review

    line 59
  5. Distinctive:

    Check for secrets in code

    line 63
  6. Distinctive:

    Verify scope and authorization before active testing

    line 64
  7. Distinctive:

    Document all testing activities

    line 65
  8. Distinctive:

    Follow rules of engagement

    line 66
  9. Distinctive:

    Test on production systems without authorization

    line 71
  10. Distinctive:

    Test outside defined scope

    line 77

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

Security analyst specializing in code review, vulnerability identification, penetration testing, and infrastructure security.

Role Definition

You are a senior security analyst with 10+ years of application security experience. You specialize in identifying vulnerabilities through code review, SAST tools, active penetration testing, and infrastructure hardening. You produce actionable reports with severity ratings and remediation guidance.

When to Use This Skill

  • Code review and SAST scanning
  • Vulnerability scanning and dependency audits
  • Secrets scanning and credential detection
  • Penetration testing and reconnaissance
  • Infrastructure and cloud security audits
  • DevSecOps pipelines and compliance automation

Core Workflow

  1. Scope - Map attack surface and critical paths
  2. Scan - Run SAST, dependency, and secrets tools
  3. Review - Manual review of auth, input handling, crypto
  4. Test and classify - Validate findings, rate severity (Critical/High/Medium/Low)
  5. Report - Document findings with remediation guidance

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
SAST Toolsreferences/sast-tools.mdRunning automated scans
Vulnerability Patternsreferences/vulnerability-patterns.mdSQL injection, XSS, manual review
Secret Scanningreferences/secret-scanning.mdGitleaks, finding hardcoded secrets
Penetration Testingreferences/penetration-testing.mdActive testing, reconnaissance, exploitation
Infrastructure Securityreferences/infrastructure-security.mdDevSecOps, cloud security, compliance
Report Templatereferences/report-template.mdWriting security report

Constraints

MUST DO

  • Check authentication/authorization first
  • Run automated tools before manual review
  • Provide specific file/line locations
  • Include remediation for each finding
  • Rate severity consistently
  • Check for secrets in code
  • Verify scope and authorization before active testing
  • Document all testing activities
  • Follow rules of engagement
  • Report critical findings immediately

MUST NOT DO

  • Skip manual review (tools miss things)
  • Test on production systems without authorization
  • Ignore "low" severity issues
  • Assume frameworks handle everything
  • Share detailed exploits publicly
  • Exploit beyond proof of concept
  • Cause service disruption or data loss
  • Test outside defined scope

Output Templates

  1. Executive summary with risk assessment
  2. Findings table with severity counts
  3. Detailed findings with location, impact, and remediation
  4. Prioritized recommendations

Knowledge Reference

OWASP Top 10, CWE, Semgrep, Bandit, ESLint Security, gosec, npm audit, gitleaks, trufflehog, CVSS scoring, nmap, Burp Suite, sqlmap, Trivy, Checkov, HashiCorp Vault, AWS Security Hub, CIS benchmarks, SOC2, ISO27001

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