Skip to content
Skills Library
Security · Review & audit

security-audit

/security-audit

This skill should be used when the user says \"security audit\", \"check for vulnerabilities\", \"security review\", \"harden project\", \"dependency audit\", \"credential scan\", \"check for secrets\", \"scan for secrets\", \"OWASP review\", \"security checklist\", \"audit dependencies\", \"find vulnerabilities\", or wants to review their project for security issues, exposed credentials, or vulnerable dependencies.

Licence
BSD-3-Clause
Last repository change
23.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 23.10.2026, without references to retired models or APIs.

Licence

BSD-3-Clause, otwarta.

What it does and when to use it

This skill should be used when the user says \"security audit\", \"check for vulnerabilities\", \"security review\", \"harden project\", \"dependency audit\", \"credential scan\", \"check for secrets\", \"scan for secrets\", \"OWASP review\", \"security checklist\", \"audit dependencies\", \"find vulnerabilities\", or wants to review their project for security issues, exposed credentials, or vulnerable dependencies.

Triggers from the description

security audit\check for vulnerabilities\security review\harden project\dependency audit\credential scan\check for secrets\scan for secrets\
Original author description

This skill should be used when the user says \"security audit\", \"check for vulnerabilities\", \"security review\", \"harden project\", \"dependency audit\", \"credential scan\", \"check for secrets\", \"scan for secrets\", \"OWASP review\", \"security checklist\", \"audit dependencies\", \"find vulnerabilities\", or wants to review their project for security issues, exposed credentials, or vulnerable dependencies.

How it works

  1. When to Use
  2. Audit Checklist
  3. Output Format
  4. Additional Resources
Original SKILL.md headings · 162 lines, 671 words
SKILL.md preview
---
name: security-audit
description: "This skill should be used when the user says \"security audit\", \"check for vulnerabilities\", \"security review\", \"harden project\", \"dependency audit\", \"credential scan\", \"check for secrets\", \"scan for secrets\", \"OWASP review\", \"security checklist\", \"audit dependencies\", \"find vulnerabilities\", or wants to review their project for security issues, exposed credentials, or vulnerable dependencies."
version: 0.1.0
---

# Security Audit

Systematic security review of a project covering dependency vulnerabilities, credential exposure, common code vulnerabilities, and configuration hardening.

## When to Use

- Before a release or deployment
- After adding new dependencies
- When onboarding to a new codebase
- Periodic security reviews
- After receiving a vulnerability report

## Audit Checklist

### 1. Credential and Secret Scanning

Check for exposed secrets in the codebase:

```bash
# Check for common secret patterns in tracked files
git grep -n -i -E '(api_key|apikey|secret|password|token|credential|private_key)\s*[:=]' -- ':!*.md' ':!*.lock'

# Check for .env files tracked in git
git ls-files | grep -i '\.env'

# Check .gitignore covers sensitive files
for f in .env .env.local credentials.json secrets.yaml; do
  git check-ignore "$f" 2>/dev/null || echo "WARNING: $f not in .gitignore"
done
```

Files that must never be committed:
- `.env`, `.env.*` (environment variables)
- `credentials.json`, `service-account.json` (cloud credentials)
- `*.pem`, `*.key` (private keys)
- `*.p12`, `*.pfx` (certificates with private keys)

### 2. Dependency Vulnerability Scan

**Python:**
```bash
uv run pip-audit
```

**JavaScript/TypeScript:**
```bash
bun pm audit
# or check with npm for broader database
npm audit --omit=dev
```

**Go:**
```bash
govulncheck ./...
```

Review results against the severity rubric (shared with the
dependency-auditor agent):

- Critical: exploitable now or actively exploited (leaked live credential,
  known-exploited CVE in a reachable path). Must fix before release; blocks
  release-prep.
- High: known vulnerability with a plausible attack path. Fix before the next
  release.
- Medium: vulnerability with mitigating factors, or a major-version lag on a
  security-relevant package. Fix within the sprint.
- Low: outdated without known vulnerabilities; license concerns to review.
  Track in backlog.

### 3. Code Vulnerability Patterns

Scan for common vulnerability patterns:

**SQL Injection:**
```bash
# Look for string interpolation in SQL
grep -rn 'f".*SELECT\|f".*INSERT\|f".*UPDATE\|f".*DELETE' --include='*.py'
grep -rn "format.*SELECT\|format.*INSERT" --include='*.py'
```

**Command Injection:**
```bash
# Look for shell=True or unsanitized subprocess calls
grep -rn 'shell=True\|os\.system\|subprocess\.call.*shell' --include='*.py'
grep -rn 'exec(\|eval(' --include='*.py' --include='*.js' --include='*.ts'
```

**XSS (Cross-Site Scripting):**
```bash
# Look for dangerouslySetInnerHTML or unescaped output
grep -rn 'dangerouslySetInnerHTML\|innerHTML\s*=' --include='*.tsx' --include='*.jsx' --include='*.ts' --include='*.js'
```

**Path Traversal:**
```bash
grep -rn 'open(.*\+\|os\.path\.join.*input\|req\.\(params\|query\|body\)' --include='*.py' --include='*.js'
```

### 4. Authentication and Authorization

Review:
- [ ] Authentication endpoints use constant-time comparison for secrets
- [ ] Session tokens have appropriate expiration
- [ ] CORS configuration is restrictive (not `*` in production)
- [ ] Rate limiting on auth endpoints
- [ ] Password hashing uses bcrypt/argon2 (not MD5/SHA1)

### 5. Configuration Hardening

- [ ] Debug mode disabled in production configs
- [ ] HTTPS enforced (HSTS headers)
- [ ] Security headers present (CSP, X-Frame-Options, X-Content-Type-Options)
- [ ] Error messages do not leak stack traces in production
- [ ] Logging does not include sensitive data (passwords, tokens)

### 6. Docker Security (if applicable)

- [ ] Non-root user in Dockerfile
- [ ] Base image is pinned to specific version (not `latest`)
- [ ] No secrets in Docker build args or layers
- [ ] Health checks configured
- [ ] Read-only filesystem where possible

### 7. CI/CD Security

- [ ] Secrets stored in GitHub Secrets (not in workflow files)
- [ ] Third-party actions pinned to SHA (not tags)
- [ ] Minimal permissions in workflow `permissions:` block
- [ ] No `pull_request_target` with `actions/checkout` of PR head

## Output Format

Present findings as a prioritized list:

```
## Security Audit Results

### Critical (must fix)
1. [CRED] API key found in src/config.py:42 - move to environment variable
2. [DEP] lodash 4.17.20 has prototype pollution (CVE-2021-23337)

### High (fix before release)
3. [CODE] SQL injection risk in src/db.py:88 - use parameterized queries

### Medium (fix within sprint)
4. [CONFIG] CORS allows * origin in production config

### Low (backlog)
5. [STYLE] Error responses include stack traces in non-debug mode

### Passed
- [x] No .env files in git
- [x] Docker runs as non-root
- [x] Dependencies up to date
```

## Additional Resources

- Reference: [references/owasp-top-10.md](references/owasp-top-10.md) - OWASP Top 10 checklist with project-specific examples
- Reference: [references/secret-management.md](references/secret-management.md) - How to manage secrets across environments
Files in this package (3)
  • SKILL.md 5 KB
  • references/owasp-top-10.md 3 KB
  • references/secret-management.md 2 KB

Versions

RepositoryScoreLicence
This page · neuromechanist/research-skills100BSD-3-Clause
posthog/posthog100MIT
mono/SkiaSharp100MIT
iuliandita/skills100MIT
gtlpanda/PandaStack100MIT
ericrisco/rsc-harness100MIT
matthewliu/matt-agent-playbook100MIT
drvoss/everything-copilot-cli100MIT
stella/stella100Apache-2.0

Database snapshot: 13.11.2026 · package version 4d24333afcb8 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100audit-security
    Perform a security audit when the user asks to check for vulnerabilities, audit security, review OWASP compliance, scan for secrets, or assess application security posture
  • 90ds-security
    Use when checking dependencies for vulnerabilities, patching vulnerable dependencies, or when a security review or codebase audit is requested.
  • 84audit-dependencies
    Audit project dependencies for security vulnerabilities and outdated packages, then apply safe updates. Use when user says "audit my dependencies", "check for vulnerable packages", "run npm audit", "find security issues in my packages", "what packages are outdated", "update my…
  • 98security-review
    Scan a codebase for OWASP Top-10 vulnerabilities, hardcoded secrets, insecure dependencies, and unsafe code patterns. Produces a read-only markdown report ranked by severity (Critical / High / Medium / Low). Use when the user says "security review", "scan for vulnerabilities",…
  • 100audit-security
    Audit and fix app code against OWASP (injection, headers, dependencies). Use when "review security" or "check vulnerabilities". Auth gates → audit-auth-flows. Plan-only → plan-security-audit. RLS → plan-rls-audit. LLM → audit-llm-security.
  • 100security-scan
    Use when you want a quick security pass on code changes or dependencies — checks OWASP Top 10 patterns, runs dependency audits, and surfaces critical vulnerabilities with targeted fixes.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.