Security Code Audit
Use when you have application source code and want to find security vulnerabilities by reading it — covers OWASP Top 10 across frontend, backend API, and database. Produces a findings register with severity, file:line, and exploitability.
Install
/plugin marketplace add mn-youssef/security-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add mn-youssef/security-skills --skill security-code-auditgit clone --depth 1 https://github.com/mn-youssef/security-skills.git /tmp/security-skills
mkdir -p ~/.claude/skills
cp -r /tmp/security-skills/skills/security-code-audit ~/.claude/skills/security-code-auditPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Security Code Audit (FIND phase) ## Overview Read source code and find vulnerabilities by pattern. No running app required — works in any AI coding tool. Trace untrusted input from its **source** (where it enters) to its **sink** (where it's used dangerously). **Core principle:** A vulnerability is *untrusted data reaching a dangerous sink without adequate validation/encoding in between*. Find the source→sink paths. ## Method: source → sink tracing 1. From the threat model (or by scanning entry points), pick a **source** of untrusted input. 2. Follow the data through the code to where it's **used** (the sink). 3. Ask: is it validated, sanitized, parameterized, or encoded *for that sink*? If not → finding. 4. Record severity, `file:line`, the exact data path, and how to exploit it. ## OWASP Top 10 — what to grep for | Risk | Smell / sink to search | |------|------------------------| | Injection (SQL/NoSQL/cmd) | string-built queries, `exec`, `eval`, `system`, template interpolation in queries | | Broken access control (IDOR) | object lookups by user-supplied id with no ownership check | | Broken auth | custom crypto, weak session handling, missing MFA, token in URL | | Cryptographic failures | `md5`/`sha1` for passwords, hardcoded keys, `Math.random` for tokens, no TLS | | SSRF | server fetches a user-supplied URL (`requests.get(input)`, `fetch(input)`) | | Security misconfig | debug=true, default creds, permissive CORS `*`, verbose errors |
Details
- Skill name
security-code-audit- Repository
- mn-youssef/security-skills
- Path
skills/security-code-audit/SKILL.md- License
- MIT
- Repo updated
- 12 June 2026
FAQ
What does the Security Code Audit skill do?
Use when you have application source code and want to find security vulnerabilities by reading it — covers OWASP Top 10 across frontend, backend API, and database. Produces a findings register with severity, file:line, and exploitability.
How do I install the Security Code Audit skill?
Claude Code plugin: /plugin marketplace add mn-youssef/security-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Security Code Audit popular?
It lives in mn-youssef/security-skills, which has 49 GitHub stars and 7 forks.
Related skills
Access Control Testing
49mn-youssef/security-skills
Use when testing whether users can access data or actions they shouldn't — IDOR/BOLA, horizontal and vertical privilege escalation, multi-tenant isolation, forced browsing, function-level authorization (BFLA), and mass assignment. The #1 cause of real-world breaches.
Active Pentest
49mn-youssef/security-skills
Use when you need to actually run security tests against a running application you own or are authorized to test — the shared execution harness for lab/proxy/scanner setup, safe non-destructive execution, and standardized proof-of-concept capture that the find/exploit specialist skills rely on.
API Security Testing
49mn-youssef/security-skills
Use when testing REST, GraphQL, gRPC, or WebSocket APIs against the OWASP API Security Top 10 — object- and function-level authorization (BOLA/BFLA), excessive data exposure, mass assignment, unrestricted resource consumption, and GraphQL-specific abuse. For apps you own or are authorized to test.
Security Hardening
49mn-youssef/security-skills
Use when you have a security finding (from code audit or pentest) and need to fix it correctly with secure-coding patterns, then verify the fix actually closes it. Covers fixes for injection, access control, XSS, auth, secrets, and config across the stack.
Recon and Osint
49mn-youssef/security-skills
Use when starting an assessment and you need to discover an application's full attack surface — subdomains, hosts, endpoints, technologies, exposed services, leaked credentials and secrets — on assets you own or are authorized to test. Feeds the threat model with real, not assumed, targets.
Security Testing
49mn-youssef/security-skills
Use when you want to security-test, pentest, audit, or find vulnerabilities in an application you own or are authorized to test — entry point that confirms authorization and routes to the right phase (threat model, code audit, active test, or hardening).
Browse the most popular Claude skills, all security skills, or write your own with the skills generator.