Penetration Testing

Name: Penetration Testing
Author: bagelhole

bagelhole/devops-security-agent-skills

119 installs
44 repo stars
Updated May 22, 2026
bagelhole/devops-security-agent-skills

Penetration Testing is a Claude Code skill for running authorized, phased security assessments using reconnaissance, scanning, and exploitation techniques.

About

Penetration Testing validates security controls through authorized testing. A developer uses it to run a five-phase assessment covering reconnaissance, scanning, exploitation, post-exploitation, and reporting, with concrete tooling for DNS enumeration, port and vulnerability scanning, and web testing. It stresses written authorization, defined scope, and documenting findings.

Five-phase pentest methodology from recon to reporting
Concrete tooling: nmap, nikto, sqlmap, subfinder, Burp Suite
Rules of engagement and authorization best practices

Penetration Testing by the numbers

119 all-time installs (skills.sh)
Ranked #955 of 2,203 Security skills by installs in the Skillselion catalog
Data as of Jul 28, 2026 (Skillselion catalog sync)

At a glance

penetration-testing capabilities & compatibility

Capabilities: security audit
Use cases: security audit

From the docs

What penetration-testing says it does

Validate security controls through authorized testing.

SKILL.md

Always get written authorization

SKILL.md

Report critical findings immediately

SKILL.md

npx skills add https://github.com/bagelhole/devops-security-agent-skills --skill penetration-testing

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/skills/bagelhole/devops-security-agent-skills/penetration-testing.svg)](https://skillselion.com/skills/bagelhole/devops-security-agent-skills/penetration-testing)

Installs	119
repo stars	★ 44
Last updated	May 22, 2026
Repository	bagelhole/devops-security-agent-skills ↗

What it does

Run an authorized five-phase penetration test to validate security controls and document findings.

Who is it for?

Developers and security teams validating security controls through authorized, scoped penetration tests.

When should I use this skill?

When validating security controls or assessing system security.

What you get

A documented penetration test with findings, risk assessment, and remediation recommendations.

Documented findings
Risk assessment
Remediation recommendations

By the numbers

5-phase pentest methodology
Recon, scanning, exploitation, post-exploitation, reporting phases

Files

SKILL.mdMarkdownGitHub ↗

Penetration Testing

Validate security controls through authorized testing.

Phases

pentest_phases:
  1_reconnaissance:
    - Passive information gathering
    - DNS enumeration
    - Network mapping
    
  2_scanning:
    - Port scanning
    - Service identification
    - Vulnerability scanning
    
  3_exploitation:
    - Attempt exploitation
    - Verify vulnerabilities
    - Document findings
    
  4_post_exploitation:
    - Privilege escalation
    - Lateral movement
    - Data access
    
  5_reporting:
    - Document findings
    - Risk assessment
    - Remediation recommendations

Reconnaissance

# DNS enumeration
dig example.com ANY
host -l example.com

# Subdomain discovery
subfinder -d example.com

# WHOIS
whois example.com

Scanning

# Port scan
nmap -sV -sC -p- target.com

# Web scanning
nikto -h https://target.com
dirb https://target.com

# Vulnerability scan
nmap --script vuln target.com

Web Testing

# SQL injection test
sqlmap -u "http://target.com/page?id=1"

# XSS testing
# Use Burp Suite or manual testing

# Directory traversal
curl "http://target.com/file?path=../../../etc/passwd"

Rules of Engagement

scope:
  in_scope:
    - target.com
    - api.target.com
  out_of_scope:
    - production-db.target.com
    - third-party services
  
  testing_window: "Weekdays 2-6 AM UTC"
  emergency_contact: "security@target.com"