← ClaudeAtlas

security-auditlisted

Run a full security, bug, and data-protection audit on any codebase (especially vibe-coded apps built with Lovable, Bolt, Replit, Cursor, v0, Claude Code, or similar AI builders). Use whenever the user asks to "audit", "check for vulnerabilities", "find security issues", "review for bugs", "pentest", "rate/score my app's security", "is this safe to launch/deploy", or similar, or before any deployment/launch discussion. Runs 100+ checks across OWASP Top 10 2025, OWASP LLM Top 10, supply-chain, secrets, data protection, auth, and business logic, cross-references live threat intelligence via web search, and produces a scored report (0-100 per category + overall letter grade) with concrete fixes.
hemant-datascientist/security-audit-skill · ★ 0 · AI & Automation · score 70
Install: claude install-skill hemant-datascientist/security-audit-skill
# Security, Bug & Data Protection Audit A single comprehensive audit skill that replaces ad-hoc prompt lists. It combines static checklist review (100+ items, mapped to current industry standards) with a live threat-intel step, so findings reflect *this week's* attack patterns, not a stale training-data snapshot. This skill is defensive/blue-team only: it finds and helps fix weaknesses in code the user owns or is authorized to audit. It never generates exploit code, malware, or attack tooling — only detection guidance and fixes. ## When NOT to over-trigger Don't run the full audit for a one-line code question, a single function review, or when the user is mid-feature-development and just wants that feature reviewed. In those cases, do a targeted check against the relevant category file only (see references/). Reserve the full 100+ item run for explicit audit requests or pre-launch checks. ## Workflow Run these five phases in order. Don't skip phases 1 and 5 — they're what makes this audit better than a static checklist someone could paste from a PDF. ### Phase 1 — Recon (before opening the checklist) Figure out what you're actually auditing before picking checks: - Stack: language(s), framework(s), package manager(s), DB, auth provider, hosting. - App type: has payments? has auth/accounts? multi-tenant? handles PII? has an LLM/agent component? public API? mobile app? Note this because it determines which checklist categories matter most (e.g., skip Category 11, LL