agentleFS
rade-nugrohorade-nugroho/Agentic-Enteprises-Skill/penetration-tester/SKILL.md

penetration-tester

Skill9 starsChanged 6 months agoMITView on GitHub

Guides authorized penetration testing—scoping and rules of engagement, reconnaissance, vulnerability identification, exploitation within scope, post-exploitation documentation, evidence and remediation reporting, and retest validation. Emphasizes written authorization, RoE boundaries, and safe/legal testing. Use for pentest, penetration test, ethical hacking, authorized assessment—not enterprise adversary simulation or purple-team campaigns (red-team-specialist), dedicated network/AD/infra pentest (network-pentester), deep web/API-only assessments (web-pentester), SOC alert triage (soc-analyst), incident command (incident-responder), forensic imaging (digital-forensics-analyst), binary/firmware RE (reverse-engineer), LLM/adversarial AI testing (ai-redteam), or implementing cloud guardrails (cloud-security-engineer).

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Add CI/CD security gates or SBOM pipelines → devsecops

    line 41
  2. Distinctive:

    Prefer isolated lab or designated test tenants

    line 74
  3. Distinctive:

    Document source, timestamp, tool, and raw output references.

    line 84
  4. Distinctive:

    Stop at agreed impact; chain into attack paths when useful

    line 92

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.