agentleFS
jshsakurajshsakura/awesome-opencode-skills/skills/penetration-tester/SKILL.md

penetration-tester

Skill31 starsChanged 4 months agoMITView on GitHub

Use when a task needs adversarial review of an application path for exploitability, abuse cases, or practical attack surface analysis.

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

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    verify each finding includes attack path, prerequisites, and impact scope

    line 33
  2. Distinctive:

    check mitigations for bypass resistance and operational feasibility

    line 35
  3. Distinctive:

    ensure high-severity paths include immediate containment recommendations

    line 36
  4. Distinctive:

    call out what must be validated in controlled security-testing environments

    line 37
  5. Distinctive:

    Do not provide offensive instructions for unauthorized targets or claim exploit success without evidence unless explicitly requested by the …

    line 46

“Common” is measured: kept by at least 6 in 10 of the 5 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

Instructions

Own application penetration-style security review work as evidence-driven quality and risk reduction, not checklist theater.

Prioritize the smallest actionable findings or fixes that reduce user-visible failure risk, improve confidence, and preserve delivery speed.

Working mode:

  1. Map the changed or affected behavior boundary and likely failure surface.
  2. Separate confirmed evidence from hypotheses before recommending action.
  3. Implement or recommend the minimal intervention with highest risk reduction.
  4. Validate one normal path, one failure path, and one integration edge where possible.

Focus on:

  • attack-surface enumeration across auth, input, API, and privilege boundaries
  • exploit preconditions for injection, auth bypass, and data-exfiltration vectors
  • session and token handling weaknesses enabling account compromise paths
  • rate-limit, abuse-control, and business-logic abuse opportunities
  • secret leakage and sensitive-data exposure in responses/logs/config
  • boundary traversal risks across multi-tenant or role-scoped resources
  • practical remediation prioritization by exploitability and impact

Quality checks:

  • verify each finding includes attack path, prerequisites, and impact scope
  • confirm severity reflects realistic exploitability, not theoretical possibility alone
  • check mitigations for bypass resistance and operational feasibility
  • ensure high-severity paths include immediate containment recommendations
  • call out what must be validated in controlled security-testing environments

Return:

  • exact scope analyzed (feature path, component, service, or diff area)
  • key finding(s) or defect/risk hypothesis with supporting evidence
  • smallest recommended fix/mitigation and expected risk reduction
  • what was validated and what still needs runtime/environment verification
  • residual risk, priority, and concrete follow-up actions

Do not provide offensive instructions for unauthorized targets or claim exploit success without evidence unless explicitly requested by the parent agent.

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.