Security Testing
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).
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-testinggit 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-testing ~/.claude/skills/security-testingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Security Testing (Orchestrator) ## Overview Front door for defensive security work. It enforces an authorization gate, then routes you through the lifecycle: **PLAN → FIND → EXPLOIT → FIX**. Use attacker thinking to find your own weaknesses, then close them. **Core principle:** Attackers think in *paths*, defenders think in *lists*. A defender must be right everywhere; an attacker needs one weak link. Hunt the path. ## How to run this orchestrator (MANDATORY — read first) This skill is a **router, not a substitute** for the skills it names. The tables below tell you *which* skill to open at each phase — you MUST actually open it with the `Skill` tool. **The rule:** before doing the work of a phase, invoke that phase's skill and follow its checklist. Reading a one-line description in a routing table is NOT running the skill and does NOT count as coverage. Doing the work "from your own expertise" instead of invoking the skill is the failure this section exists to stop. - RECON → `recon-and-osint` · PLAN → `threat-modeling` - FIND/EXPLOIT → invoke **each applicable** specialist (`access-control-testing`, `authentication-testing`, `injection-testing`, `file-upload-and-ssrf`, `api-security-testing`, `client-side-exploitation`, `business-logic-testing`, `secrets-management-audit`) **before** testing that area — plus `security-code-audit` (static) and `active-pentest` (dynamic).
Details
- Skill name
security-testing- Repository
- mn-youssef/security-skills
- Path
skills/security-testing/SKILL.md- License
- MIT
- Repo updated
- 12 June 2026
FAQ
What does the Security Testing skill do?
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).
How do I install the Security Testing 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 Testing 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.
Securitycards
21Reware-Labs/securitycards
Apply version-specific secure coding guidance to AI-generated or human-written code that uses supported open source libraries. Use when starting a software project, implementing a security-sensitive feature, or reviewing code for secure defaults, authentication, authorization, input handling, injection, cryptography, file handling, network boundaries, secrets, sessions, and other library-specific security concerns.
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.
Threat Modeling
49mn-youssef/security-skills
Use when starting a security assessment and you need to map an application's attack surface, enumerate trust boundaries, and rank what to test first — before auditing code or running tools. Produces a prioritized target list.
Browse the most popular Claude skills, all security skills, or write your own with the skills generator.