SkillAgentSearch skills...

pentest-checklist

This skill should be used when the user asks to "plan a penetration test", "create a security assessment checklist", "prepare for penetration testing", "define pentest scope", "follow security testing best practices", or needs a structured methodology for penetration testing engagements.

Install / Use

npx skills add zebbern/claude-code-guide --skill pentest-checklist

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

94/100

Category

Security

Supported Platforms

Universal

Our assessment of pentest-checklist

pentest-checklist scores 94/100 on our quality scale, 323rd of 1,111 Security skills we index (top 30%).

Its SKILL.md is 10.0 KB long, well organised into 46 sections with 7 code examples: a thorough specification that gives an agent plenty to work with.

With 4,652 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
29/30
Structure
20/20
Description
15/15
Adoption
16/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 39 days ago, so pentest-checklist is actively maintained.
  • Our last check on 2026-11-16 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-29. Automated pattern scan on 2026-09-28. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

pentest-checklist compared with similar skills

All 4 of these similar skills score higher than pentest-checklist; compare them before choosing.

SkillScoreStarsUpdatedFormat
pentest-checklist (this skill)by zebbern944.7k39d agoSKILL.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md
designby nextlevelbuilder100149.0k6d agoSKILL.md

Frequently asked questions

How do I install pentest-checklist?
Run npx skills add zebbern/claude-code-guide --skill pentest-checklist. The install tabs above show the steps for each supported agent.
Which AI agents does pentest-checklist work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is pentest-checklist safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is pentest-checklist still maintained?
The repository was last updated 39 days ago, so pentest-checklist is actively maintained.

name: pentest-checklist description: This skill should be used when the user asks to "plan a penetration test", "create a security assessment checklist", "prepare for penetration testing", "define pentest scope", "follow security testing best practices", or needs a structured methodology for penetration testing engagements. metadata: author: zebbern version: "1.1"

Pentest Checklist

Purpose

Provide a comprehensive checklist for planning, executing, and following up on penetration tests. Ensure thorough preparation, proper scoping, and effective remediation of discovered vulnerabilities.

Inputs/Prerequisites

  • Clear business objectives for testing
  • Target environment information
  • Budget and timeline constraints
  • Stakeholder contacts and authorization
  • Legal agreements and scope documents

Outputs/Deliverables

  • Defined pentest scope and objectives
  • Prepared testing environment
  • Security monitoring data
  • Vulnerability findings report
  • Remediation plan and verification

Core Workflow

Phase 1: Scope Definition

Define Objectives

  • [ ] Clarify testing purpose - Determine goals (find vulnerabilities, compliance, customer assurance)
  • [ ] Validate pentest necessity - Ensure penetration test is the right solution
  • [ ] Align outcomes with objectives - Define success criteria

Reference Questions:

  • Why are you doing this pentest?
  • What specific outcomes do you expect?
  • What will you do with the findings?

Know Your Test Types

| Type | Purpose | Scope | |------|---------|-------| | External Pentest | Assess external attack surface | Public-facing systems | | Internal Pentest | Assess insider threat risk | Internal network | | Web Application | Find application vulnerabilities | Specific applications | | Social Engineering | Test human security | Employees, processes | | Red Team | Full adversary simulation | Entire organization |

Enumerate Likely Threats

  • [ ] Identify high-risk areas - Where could damage occur?
  • [ ] Assess data sensitivity - What data could be compromised?
  • [ ] Review legacy systems - Old systems often have vulnerabilities
  • [ ] Map critical assets - Prioritize testing targets

Define Scope

  • [ ] List in-scope systems - IPs, domains, applications
  • [ ] Define out-of-scope items - Systems to avoid
  • [ ] Set testing boundaries - What techniques are allowed?
  • [ ] Document exclusions - Third-party systems, production data

Budget Planning

| Factor | Consideration | |--------|---------------| | Asset Value | Higher value = higher investment | | Complexity | More systems = more time | | Depth Required | Thorough testing costs more | | Reputation Value | Brand-name firms cost more |

Budget Reality Check:

  • Cheap pentests often produce poor results
  • Align budget with asset criticality
  • Consider ongoing vs. one-time testing

Phase 2: Environment Preparation

Prepare Test Environment

  • [ ] Production vs. staging decision - Determine where to test
  • [ ] Set testing limits - No DoS on production
  • [ ] Schedule testing window - Minimize business impact
  • [ ] Create test accounts - Provide appropriate access levels

Environment Options:

Production  - Realistic but risky
Staging     - Safer but may differ from production
Clone       - Ideal but resource-intensive

Run Preliminary Scans

  • [ ] Execute vulnerability scanners - Find known issues first
  • [ ] Fix obvious vulnerabilities - Don't waste pentest time
  • [ ] Document existing issues - Share with testers

Common Pre-Scan Tools:

# Network vulnerability scan
nmap -sV --script vuln TARGET

# Web vulnerability scan
nikto -h http://TARGET

Review Security Policy

  • [ ] Verify compliance requirements - GDPR, PCI-DSS, HIPAA
  • [ ] Document data handling rules - Sensitive data procedures
  • [ ] Confirm legal authorization - Get written permission

Notify Hosting Provider

  • [ ] Check provider policies - What testing is allowed?
  • [ ] Submit authorization requests - AWS, Azure, GCP requirements
  • [ ] Document approvals - Keep records

Cloud Provider Policies:

  • AWS: https://aws.amazon.com/security/penetration-testing/
  • Azure: https://docs.microsoft.com/security/pentest
  • GCP: https://cloud.google.com/security/overview

Freeze Developments

  • [ ] Stop deployments during testing - Maintain consistent environment
  • [ ] Document current versions - Record system states
  • [ ] Avoid critical patches - Unless security emergency

Phase 3: Expertise Selection

Find Qualified Pentesters

  • [ ] Seek recommendations - Ask trusted sources
  • [ ] Verify credentials - OSCP, GPEN, CEH, CREST
  • [ ] Check references - Talk to previous clients
  • [ ] Match expertise to scope - Web, network, mobile specialists

Evaluation Criteria:

| Factor | Questions to Ask | |--------|------------------| | Experience | Years in field, similar projects | | Methodology | OWASP, PTES, custom approach | | Reporting | Sample reports, detail level | | Communication | Availability, update frequency |

Define Methodology

  • [ ] Select testing standard - PTES, OWASP, NIST
  • [ ] Determine access level - Black box, gray box, white box
  • [ ] Agree on techniques - Manual vs. automated testing
  • [ ] Set communication schedule - Updates and escalation

Testing Approaches:

| Type | Access Level | Simulates | |------|-------------|-----------| | Black Box | No information | External attacker | | Gray Box | Partial access | Insider with limited access | | White Box | Full access | Insider/detailed audit |

Define Report Format

  • [ ] Review sample reports - Ensure quality meets needs
  • [ ] Specify required sections - Executive summary, technical details
  • [ ] Request machine-readable output - CSV, XML for tracking
  • [ ] Agree on risk ratings - CVSS, custom scale

Report Should Include:

  • Executive summary for management
  • Technical findings with evidence
  • Risk ratings and prioritization
  • Remediation recommendations
  • Retesting guidance

Phase 4: Monitoring

Implement Security Monitoring

  • [ ] Deploy IDS/IPS - Intrusion detection systems
  • [ ] Enable logging - Comprehensive audit trails
  • [ ] Configure SIEM - Centralized log analysis
  • [ ] Set up alerting - Real-time notifications

Monitoring Tools:

# Check security logs
tail -f /var/log/auth.log
tail -f /var/log/apache2/access.log

# Monitor network
tcpdump -i eth0 -w capture.pcap

Configure Logging

  • [ ] Centralize logs - Aggregate from all systems
  • [ ] Set retention periods - Keep logs for analysis
  • [ ] Enable detailed logging - Application and system level
  • [ ] Test log collection - Verify all sources working

Key Logs to Monitor:

  • Authentication events
  • Application errors
  • Network connections
  • File access
  • System changes

Monitor Exception Tools

  • [ ] Track error rates - Unusual spikes indicate testing
  • [ ] Brief operations team - Distinguish testing from attacks
  • [ ] Document baseline - Normal vs. pentest activity

Watch Security Tools

  • [ ] Review IDS alerts - Separate pentest from real attacks
  • [ ] Monitor WAF logs - Track blocked attempts
  • [ ] Check endpoint protection - Antivirus detections

Phase 5: Remediation

Ensure Backups

  • [ ] Verify backup integrity - Test restoration
  • [ ] Document recovery procedures - Know how to restore
  • [ ] Separate backup access - Protect from testing

Reserve Remediation Time

  • [ ] Allocate team availability - Post-pentest analysis
  • [ ] Schedule fix implementation - Address findings
  • [ ] Plan verification testing - Confirm fixes work

Patch During Testing Policy

  • [ ] Generally avoid patching - Maintain consistent environment
  • [ ] Exception for critical issues - Security emergencies only
  • [ ] Communicate changes - Inform pentesters of any changes

Cleanup Procedure

  • [ ] Remove test artifacts - Backdoors, scripts, files
  • [ ] Delete test accounts - Remove pentester access
  • [ ] Restore configurations - Return to original state
  • [ ] Verify cleanup complete - Audit all changes

Schedule Next Pentest

  • [ ] Determine frequency - Annual, quarterly, after changes
  • [ ] Consider continuous testing - Bug bounty, ongoing assessments
  • [ ] Budget for future tests - Plan ahead

Testing Frequency Factors:

  • Release frequency
  • Regulatory requirements
  • Risk tolerance
  • Past findings severity

Quick Reference

Pre-Pentest Checklist

□ Scope defined and documented
□ Authorization obtained
□ Environment prepared
□ Hosting provider notified
□ Team briefed
□ Monitoring enabled
□ Backups verified

Post-Pentest Checklist

□ Report received and reviewed
□ Findings prioritized
□ Remediation assigned
□ Fixes implemented
□ Verification testing scheduled
□ Environment cleaned up
□ Next test scheduled

Constraints

  • Production testing carries inherent risks
  • Budget limitations affect thoroughness
  • Time constraints may limit coverage
  • Tester expertise varies significantly
  • Findings become stale quickly

Examples

Example 1: Quick Scope Definition

**Target:** Corporate web application (app.company.com)
**Type:** Gray box web application pentest
**Duration:** 5 business days
**Excluded:** DoS testing, production database access
**Access:** Standard user account provided

Example 2: Monitoring Setup

# Enable comprehensive logging
sudo systemctl restart rsyslog
sudo systemctl restart auditd

# Start packet capture
tcpdump -i eth0 -w /tmp/pentest_capture.pcap &

Troubleshooting

| Issue | Solution | |-------|----------| | Scope creep | Document and require change approval | | Testing impacts production | Schedule off-hours, use staging | | Findings disputed | Provide detailed evidence, retest | | Remediation delayed | Prioritize by risk, set deadlines | | Budget exceeded | Define clear scope, fixed-price contracts |

Related Skills

View on GitHub
GitHub Stars4.7k
CategorySecurity
Updated1mo ago
Forks468

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions