agentleFS
Sign inStart free
leonardoaraujosantosleonardoaraujosantos/my_ai_skills/pentest/SKILL.md

pentest

Skill1 starsChanged 4 months agoLicence not identifiedView on GitHub

Authorized defensive security testing for web apps, APIs, cloud, and CI/CD. A scope-gated orchestrator over 41 vulnerability/recon playbooks (IDOR, SQLi, XSS, SSRF, JWT, OAuth, BOLA/BFLA, SSTI, XXE, command injection, deserialization, CORS, CSRF, GraphQL, mass-assignment, rate-limit, AWS IAM / S3, containers, GitLab CI/CD, secrets-in-code, subdomain takeover, and recon). Optionally drives Shannon, an autonomous AI pentester that proves exploits with working PoCs. Supports black-box (only a backend or web URL, no source or creds), gray-box, and white-box engagements. Use when the user asks to security-test / pentest / audit / find vulnerabilities in an application, API, or cloud account THEY OWN OR ARE EXPLICITLY AUTHORIZED TO TEST. Every run requires a populated security-scope.yaml; refuses to emit test traffic without one. Defensive, No-Exploit-No-Report standard — findings include CWE, OWASP, CVSS, PoC, and remediation.

  • Reads credentials

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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.

Check your setup, free