claude-pentest
Reduces manual reconnaissance and vulnerability discovery cycles by automating pentesting workflows within Claude, enabling security teams to scale assessmen…
A Claude Code plugin that gives Claude structured, human-in-the-loop penetration testing capabilities. A single /pentest command coordinates the engagement — running reconnaissance, asking a planner agent for a deployment plan, then dispatching specialized executor agents across 63 attack categories, with operator approval required before any active exploitation. Every finding ships with a working proof-of-concept and captured HTTP/screenshot evidence. For authorized security testing only.
- Ask Claude to identify security vulnerabilities in your web application code
- Generate a penetration testing plan for your infrastructure before a security audit
- Find potential attack vectors in your system architecture and network configuration
Reduces manual reconnaissance and vulnerability discovery cycles by automating pentesting workflows within Claude, enabling security teams to scale assessment coverage without expanding headcount.
Security teams and penetration testers conducting authorized security assessments and vulnerability research.
https://github.com/Stickman230/claude-pentest
By Stickman230
How to Get It
/plugin marketplace add Stickman230/claude-pentest /plugin install pentest@claude-pentest
After installing, paste this into Claude:
Identify security vulnerabilities in my web application code
Trust Signals Auto-scanned
Community Pulse New
No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 48 GitHub stars; contributors unknown; last commit 0d ago; license MIT.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
- Single maintainer. Consider the risk if this person stops maintaining the project.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 48 GitHub stars; contributors unknown; last commit 0d ago; license MIT.