open-sesame

agent
Security Audit
Fail
Health Pass
  • License รขโ‚ฌโ€ License: NOASSERTION
  • Description รขโ‚ฌโ€ Repository has a description
  • Active repo รขโ‚ฌโ€ Last push 0 days ago
  • Community trust รขโ‚ฌโ€ 54 GitHub stars
Code Fail
  • rm -rf รขโ‚ฌโ€ Recursive force deletion command in .claude/skills/net-pentest/scripts/render-report.sh
  • rm -rf รขโ‚ฌโ€ Recursive force deletion command in .claude/skills/web-pentest/scripts/render-report.sh
Permissions Pass
  • Permissions รขโ‚ฌโ€ No dangerous permissions requested

No AI report is available for this listing yet.

SUMMARY

๐Ÿ”“ An AI web-pentest skill for Claude Code. Point it at a site you're authorized to test โ€” it maps the attack surface, works through the OWASP WSTG, validates findings, and writes dev + stakeholder reports (PDF).

README.md

open-sesame ๐Ÿ”“

AI penetration-testing skills for Claude โ€” web apps and networks.

Say the magic words, and the target opens up โ€” the authorized way.

License: MIT
PRs Welcome
Claude Skills
Methodology: OWASP WSTG + PTES


open-sesame is a suite of skills that turns Claude into a disciplined penetration
tester. Point it at a target you're authorized to assess and it runs the whole
engagement โ€” maps the attack surface, works methodically through an industry
methodology, validates findings with the lightest safe proof, and writes clean reports
for both engineers and leadership.

Skill For Methodology
web-pentest A single web application / API OWASP WSTG
net-pentest Networks & infrastructure, incl. Active Directory PTES / NIST SP 800-115

It's built as a set of Markdown instructions and small helper scripts โ€” no model
fine-tuning, no binaries. You can read every line of what it tells Claude to do.

[!WARNING]
Authorized testing only. This skill is for systems you own or have explicit
permission
to test (your own apps, a signed client engagement, an in-scope
bug-bounty target, or a CTF / practice lab). It is designed to refuse unauthorized
targets, treat the platform/host a target runs on as out of scope by default, and
prefer non-destructive proofs. Using it against systems you don't have permission to
test may be illegal. You are responsible for staying within scope and the law.

โœจ What it does

  • Authorization-first โ€” both skills confirm scope and rules of engagement before any
    active test, and treat third-party platform/cloud infrastructure as out of scope.
  • Web (web-pentest) โ€” full OWASP WSTG coverage: recon, configuration, auth, session,
    access control (incl. multi-tenant isolation), injection, crypto, business logic,
    client-side, and API tests; safe RCE validation and reverse shells.
  • Network (net-pentest) โ€” PTES-based external and internal testing: host discovery,
    port/service scanning, enumeration, vuln ID, exploitation, privilege escalation (Linux +
    Windows), pivoting, and Active Directory attacks (Kerberoasting, BloodHound, NTLM
    relay, the path to Domain Admin) โ€” plus hybrid/cloud identity (Entra ID, AWS),
    Wi-Fi, and container/Kubernetes testing.
  • Tooling playbooks โ€” concrete, safe-usage workflows for Burp, ffuf, nuclei, sqlmap,
    nmap, masscan, netexec, impacket, responder, BloodHound, and more.
  • Three reports, two audiences โ€” a technical findings report, a plain-language
    stakeholder summary, and a how-to-recreate guide, each rendered to PDF.

๐Ÿš€ Quick start

1. Install the skill

Clone into a location Claude discovers skills from:

# Per project (available inside one repo) โ€” installs both skills
git clone https://github.com/hassan-algo/open-sesame.git
cp -r open-sesame/.claude/skills/* .claude/skills/

# Or personal (available in every project)
cp -r open-sesame/.claude/skills/* ~/.claude/skills/

2. Use it

In Claude Code, just describe the work โ€” the right skill triggers automatically:

Pentest my web app at https://staging.myapp.example โ€” I own it. Start with recon.
Scan my network 10.0.0.0/24 and enumerate Active Directory โ€” it's my lab.

web-pentest triggers on things like "find vulns in my web app", "test for IDOR/SQLi",
"validate this RCE"; net-pentest on "scan this subnet", "enumerate these hosts",
"Kerberoasting / BloodHound", "privilege escalation on this box". Or invoke explicitly
with /web-pentest or /net-pentest.

3. Get PDF reports

After a report is drafted in Markdown, render it to a styled PDF:

# each skill ships the same renderer
.claude/skills/web-pentest/scripts/render-report.sh report.md report.pdf

The script converts Markdown โ†’ HTML (pandoc, else npx marked) โ†’ PDF (headless
Chrome/Chromium, else weasyprint, else macOS cupsfilter). Install at least one tool
from each stage.

๐Ÿ—‚๏ธ How it's organized

.claude/skills/
โ”œโ”€โ”€ web-pentest/                 # single web application (OWASP WSTG)
โ”‚   โ”œโ”€โ”€ SKILL.md                 #   authorization, workflow, pointers
โ”‚   โ”œโ”€โ”€ references/              #   methodology, tooling, post-exploitation,
โ”‚   โ”‚                            #   reporting, lab-targets
โ”‚   โ”œโ”€โ”€ assets/report-template.md
โ”‚   โ”œโ”€โ”€ scripts/render-report.sh
โ”‚   โ””โ”€โ”€ evals/                   #   test cases + benchmarks
โ””โ”€โ”€ net-pentest/                 # networks & Active Directory (PTES / NIST)
    โ”œโ”€โ”€ SKILL.md
    โ”œโ”€โ”€ references/              #   methodology, active-directory, privesc,
    โ”‚                            #   pivoting, password-attacks, cloud-identity,
    โ”‚                            #   wireless, containers, tooling, reporting,
    โ”‚                            #   lab-targets
    โ”œโ”€โ”€ assets/report-template.md
    โ”œโ”€โ”€ scripts/render-report.sh
    โ””โ”€โ”€ evals/evals.json         #   trigger/behavior test cases

Supporting folders at the repo root:

  • index.html โ€” the project landing page.
  • reports/ โ€” generated engagement reports. Keep them local: reports/ is not yet in
    .gitignore, so add it before committing.

Each skill uses progressive disclosure: SKILL.md is always loaded; the references/
files are pulled in only when a phase needs them, keeping the context lean and the
workflow fast.

๐Ÿงช Validation

web-pentest was built and tuned with Anthropic's skill-creator and validated across
two eval iterations โ€” methodology, reporting, authorization-gating, RCE/reverse-shell
guidance, cross-tenant IDOR, and scope discipline. Summary results live in
.claude/skills/web-pentest/evals/benchmarks/.

Beyond the evals, see BENCHMARKS.md for timed, end-to-end
engagements, and CASE-STUDY.md for the story behind each one:

Target Skill Objective Active Total (incl. PDFs)
Metasploitable2 (Docker) web-pentest + net-pentest Root โ‰ˆ 3 min โ‰ˆ 6 min
Samba AD lab net-pentest Domain Admin โ‰ˆ 14 min โ‰ˆ 17 min
OWASP Juice Shop (Docker) web-pentest Admin + customer data โ‰ˆ 2.5 min โ‰ˆ 5 min

Dead ends and lab-injected findings are documented, not hidden.

๐Ÿค Contributing

Contributions are very welcome โ€” this gets better the more practitioners shape it. Good
first contributions:

  • Extend the methodology โ€” add or sharpen WSTG test cases in references/methodology.md.
  • Add tooling recipes โ€” real-world command workflows in references/tooling.md.
  • Improve reporting โ€” templates, severity guidance, or the render-report.sh backends.
  • Add eval cases โ€” new prompts in evals/ that catch gaps or regressions.

See CONTRIBUTING.md for how to propose changes. Please keep everything
aligned with the skill's core principle: authorized, non-destructive, methodical
testing
โ€” contributions that add offensive capability without that framing won't be
merged.

๐Ÿ“œ License

MIT โ€” free to use, modify, and share.

๐Ÿ™ Acknowledgements


Built for defenders and authorized testers. Hack responsibly. ๐Ÿ”“

Reviews (0)

No results found