mcpField
P
penetration-tester

penetration-tester

github.com/rade-nugrohoSecurity1239 installsUpdated 23w ago
Repository

About penetration-tester

A skill for planning and conducting authorized penetration tests across multiple domains. It covers scoping, validated vulnerability findings, in-scope exploitation, and remediation-focused reporting and retesting.

Key features

  1. 01Define authorization and rules of engagement
  2. 02Conduct reconnaissance and validate vulnerabilities
  3. 03Develop scoped proof-of-concept exploits
  4. 04Document attack paths and evidence
  5. 05Report remediation steps and retest findings

Use cases

  1. 01Scope an authorized cloud or wireless test
  2. 02Validate scanner findings before reporting
  3. 03Demonstrate an agreed attack path
  4. 04Retest critical or high-severity fixes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/rade-nugroho/agentic-enteprises-skill --skill penetration-tester

After installing, type/penetration-testerin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
exploitation_and_post_exploitation.md
penetration_tester_scope.md
recon_and_vulnerability_identification.md
reporting_and_remediation.md
retest_and_safe_practices.md
scoping_rules_of_engagement.md

Details

From the project README

Penetration Tester

When to Use

  • Plan or execute authorized penetration tests (cloud workload, wireless) spanning multiple domains under one ROE
  • Coordinate dedicated network/AD/infra assessments → network-pentester
  • Draft or validate rules of engagement, asset lists, and emergency stop procedures
  • Perform reconnaissance and vulnerability identification with manual validation
  • Develop proof-of-concept exploitation and document attack paths within agreed impact
  • Execute in-scope post-exploitation (credential proof, lateral movement, objective demo) with cleanup
  • Produce remediation-focused reports and retest critical/high findings

When NOT to Use

  • Deep web application or API-only assessments (OWASP, proxy methodology, GraphQL) → web-pentester
  • Dedicated internal/external network, AD, segmentation, wireless methodology → network-pentester
  • Triage SIEM/EDR alerts or run SOC playbooks → soc-analyst
  • Lead live incident command, war room, or stakeholder comms → incident-responder
  • Acquire and analyze forensic disk/memory images → digital-forensics-analyst
  • Disassembly, decompilation, patch diff, or malware RE lab work → reverse-engineer
  • Jailbreak LLMs, prompt injection, or agent tool abuse → ai-redteam
  • Campaign planning, purple team, detection validation at program level → red-team-specialist
  • Implement cloud IAM, CSPM, landing zone guardrails → cloud-security-engineer
  • Map audit controls or continuous compliance evidence → compliance-engineer
  • Add CI/CD security gates or SBOM pipelines → devsecops

Related skills

NeedSkill
Web/API-focused OWASP and proxy-based testingweb-pentester
Network, AD, lateral movement, segmentation, wirelessnetwork-pentester
Security program, pentest program governance, GRCcybersecurity
Implement fixes for findings (IAM, WAF, SIEM)information-security-engineer
Threat context for findings; IOC/TTP intel (not pentest execution)cti-analyst
Cloud control implementation and misconfig remediationcloud-security-engineer
LLM/agent adversarial testingai-redteam
Red team campaigns, purple team, ATT&CK emulationred-team-specialist
SOC alert triage and playbookssoc-analyst
Proactive threat hunts from pentest hypothesesthreat-hunter
Live IR command and containment cadenceincident-responder
Post-incident forensic artifactsdigital-forensics-analyst
Binary/protocol RE and patch analysisreverse-engineer
Audit evidence and control mappingcompliance-engineer
Pipeline/supply-chain testing in CIdevsecops
Offensive reporting for customerstech-writer-researcher

Core Workflows

1. Scope and authorization

Do not test without written authorization.

  1. Confirm signed SOW/ROE: assets, methods, windows, contacts
  2. Define out-of-scope (third parties, prod PII, physical access, DoS unless approved)
  3. Agree severity rubric and evidence handling
  4. Establish emergency stop and escalation path
  5. Prefer isolated lab or designated test tenants

See references/scoping_rules_of_engagement.md and references/penetration_tester_scope.md.

2. Reconnaissance and vulnerability identification
passive OSINT → asset inventory → service/version ID → auth surface mapping → validate findings

Document source, timestamp, tool, and raw output references. Validate scanner output manually.

See references/recon_and_vulnerability_identification.md.

3. Exploitation and post-exploitation (in scope only)
  • Minimal PoC steps; redacted evidence
  • Clear preconditions (role, network position, config)
  • Stop at agreed impact; chain into attack paths when useful
  • Post-exploitation only per ROE; remove persistence and test artifacts before closeout

See references/exploitation_and_post_exploitation.md.

4. Reporting, remediation, and retest

Per finding: title, severity, impact, reproduction, evidence, remediation, retest criteria. Deliver executive summary + technical appendix; schedule retest for critical/high.

See references/reporting_and_remediation.md and references/retest_and_safe_practices.md.

When to load references

TopicReference
Role boundariesreferences/penetration_tester_scope.md
Authorization and ROEreferences/scoping_rules_of_engagement.md
Recon and vuln IDreferences/recon_and_vulnerability_identification.md
Exploitation and post-exreferences/exploitation_and_post_exploitation.md
Reports and remediationreferences/reporting_and_remediation.md
Retest and safe practicesreferences/retest_and_safe_practices.md

Comments

Markdown supported