Active Pentest
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.
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 active-pentestgit clone --depth 1 https://github.com/mn-youssef/security-skills.git /tmp/security-skills
mkdir -p ~/.claude/skills
cp -r /tmp/security-skills/skills/active-pentest ~/.claude/skills/active-pentestPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Active Pentest (EXPLOIT harness) ## Overview This is the shared **execution harness** for the FIND/EXPLOIT specialists. They decide *what* to test — `access-control-testing`, `authentication-testing`, `business-logic-testing`, `api-security-testing` (and Tier-2 classes like injection / client-side / file-upload). This skill is *how* you run their tests safely against a live app: set up the lab/proxy/scanners, drive the tools, and capture proof in a consistent format. **Core principle:** A finding isn't real until you've reproduced it. A PoC ends the debate. The specialists own the attack recipes; this skill owns safe execution and evidence. ## ⚠️ Authorization Gate — STOP if not all true Do not proceed unless **all** hold: - [ ] You own the target, or have **written authorization** to test it. - [ ] Target is a **lab / staging / local** instance — not third-party production. - [ ] You will **not** run destructive or DoS techniques, and won't touch real user data. If any box is unchecked → stop and stay in `security-code-audit` on code you control. ## Scope discipline (non-destructive by default) - **Allowed:** read-only recon, fingerprinting, single-request PoCs, reading your own test data, proving an IDOR with two test accounts you created. - **Avoid:** load/stress/DoS, mass scanning, automated exploitation that writes/deletes real data, techniques whose only purpose is evasion of monitoring. Throttle scanners; use test accounts.
Details
- Skill name
active-pentest- Repository
- mn-youssef/security-skills
- Path
skills/active-pentest/SKILL.md- License
- MIT
- Repo updated
- 12 June 2026
FAQ
What does the Active Pentest skill do?
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.
How do I install the Active Pentest 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 Active Pentest 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.
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.
Authentication Testing
49mn-youssef/security-skills
Use when testing login, sessions, password reset, OAuth/OIDC/SAML/SSO, MFA, and JWTs for weaknesses that lead to account takeover — credential attacks, session fixation, reset-token poisoning, MFA bypass, and token forgery. On apps you own or are authorized to test.
Syncable Vulnerabilities
43syncable-dev/syncable-cli
Use when the user asks to check for CVEs, scan dependencies for vulnerabilities, find known security issues in packages, or audit npm/pip/cargo/go/java dependency security
Client Side Exploitation
49mn-youssef/security-skills
Use when testing advanced browser-side and HTTP-layer attacks beyond basic XSS/CSRF — DOM XSS, CSP bypass, CORS misconfiguration exploitation, postMessage abuse, prototype pollution, DOM clobbering, clickjacking, web cache poisoning, and HTTP request smuggling. On apps you own or are authorized to test.
Syncable Security Audit
43syncable-dev/syncable-cli
Use when the user asks for a security audit, pre-deployment security review, compliance check, thorough security assessment before shipping, or deep security scan for production readiness
Browse the most popular Claude skills, all security skills, or write your own with the skills generator.