agentleFS
NemesLaszloNemesLaszlo/claude-code-harness/.claude/skills/security-scan/SKILL.md

security-scan

Skill1 starsChanged 13 days agoMITView on GitHub

Security vulnerability scan using the Security Vulnerability Scanner agent workflow. Use when the user says security scan, check for vulnerabilities, security audit, is this secure, OWASP check, or before deploying to production.

89 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use django-security, deployment-patterns 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.
  • mstuder-slalomSkill

    django-security

    Django security best practices, authentication, authorization, CSRF protection, SQL injection prevention, XSS prevention, and secure deployment configurations.

    Also in 5 projects that use this

  • royaluniondesign-sysSkill

    deployment-patterns

    Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications.

    Also in 5 projects that use this

  • mstuder-slalomSkill

    springboot-security

    Spring Security best practices for authn/authz, validation, CSRF, secrets, headers, rate limiting, and dependency security in Java Spring Boot services.

    Also in 4 projects that use this

  • DonTiziSkill

    dependency-check

    Analyze project dependencies for outdated packages, security vulnerabilities, and licensing issues. Use for dependency audits and maintenance.

    Also in 3 projects that use this

  • RojiosSkill

    security-bounty-hunter

    Hunt for exploitable, bounty-worthy security issues in repositories. Focuses on remotely reachable vulnerabilities that qualify for real reports instead of noisy local-only findings.

    Also in 3 projects that use this

  • nek1987Skill

    postgres-patterns

    PostgreSQL patterns for reviewing migrations and writing efficient queries. Use when reviewing Alembic migrations, optimizing queries, or debugging database issues.

    Also in 6 projects that use this

  • +2 more from mstuder-slalom

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

    If no target is specified, scan recently modified files and critical paths (auth, API endpoints, data handling).

    line 22
  2. Distinctive:

    Only report actual vulnerabilities, not theoretical concerns.

    line 72

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

Context

  • Current branch: !git branch --show-current || true
  • Recently modified files: !git diff --name-only HEAD~5 || true

Your Task

You are the Security Vulnerability Scanner agent. Run a security vulnerability scan on the following:

Target: $ARGUMENTS

If no target is specified, scan recently modified files and critical paths (auth, API endpoints, data handling).

Scan Categories

Systematically analyze for:

  1. Injection — SQL, NoSQL, command, LDAP, XPath
  2. Authentication & Session — Weak auth, session fixation, token handling
  3. XSS — Reflected, stored, DOM-based
  4. IDOR — Insecure direct object references
  5. Security Misconfiguration — Default configs, unnecessary features, verbose errors
  6. Sensitive Data Exposure — Unencrypted data, leaked secrets, excessive logging
  7. Access Control — Missing authorization, privilege escalation
  8. CSRF — Cross-site request forgery
  9. Known Vulnerabilities — Dependencies with CVEs
  10. Logging & Monitoring — Insufficient audit trails
  11. Race Conditions — TOCTOU, concurrent access issues
  12. Cryptographic Weaknesses — Weak algorithms, improper key management
  13. Path Traversal — File system access control
  14. Deserialization — Unsafe object deserialization
  15. SSRF — Server-side request forgery
  16. Agent and tool surfaces — Prompt injection through tool results, over-broad MCP or hook permissions, secrets in CLAUDE.md or settings files

Output Format

## Security Scan Results

**Scan scope:** [what was scanned]
**Date:** [current date]

### Critical
- [Vulnerability] — `file:line` — [brief description]

### High
- [Vulnerability] — `file:line` — [brief description]

### Medium
- [Vulnerability] — `file:line` — [brief description]

### Low
- [Vulnerability] — `file:line` — [brief description]

---

**Summary:** X critical, X high, X medium, X low issues found.
**Recommendation:** [BLOCK DEPLOY | FIX BEFORE DEPLOY | ACCEPTABLE RISK | CLEAN]
**Next step:** `/fix-issues` for anything above Low.

Only report actual vulnerabilities, not theoretical concerns. Be specific about location and exploitability. Omit empty severity categories. Do not edit files.

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.