Pentest Methodology Agent Skill
Ethical security testing methodology - 5-phase pipeline, OWASP checklist, proof levels, structured findings
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/vibeeval/vibecosystem --skill pentest-methodologyThe instruction itself
12 sections, as written by the authorPentest Methodology
Etik guvenlik testi metodolojisi. Shannon framework'unden adapte.
ONEMLI: Bu skill sadece YETKILI guvenlik testleri icin kullanilir. Bug bounty, pentest anlasmasi, veya kendi sisteminiz olmali.
5-Faz Pipeline
Phase 1: Recon ──▶ Phase 2: Vuln Analysis ──▶ Phase 3: Exploitation
│
Phase 5: Report ◀── Phase 4: Verification ◀────────────┘
Phase 1: Reconnaissance (Kesfetme)
| Adim | Arac/Yontem | Cikti |
|------|-------------|-------|
| Subdomain enum | DNS brute, certificate transparency | Subdomain listesi |
| Port scan | nmap, masscan | Acik portlar |
| Tech stack | Wappalyzer, HTTP headers | Teknoloji listesi |
| Directory enum | ffuf, gobuster | Endpoint listesi |
| API discovery | Swagger/OpenAPI, sitemap | API endpoint'leri |
| Source review | JS dosyalari, comments | Hardcoded info |
Phase 2: Vulnerability Analysis
OWASP Top 10 kontrol matrisi:
| # | Vuln | Test Yontemi |
|---|------|-------------|
| A01 | Broken Access Control | IDOR, privilege escalation, path traversal |
| A02 | Cryptographic Failures | SSL config, weak ciphers, plaintext storage |
| A03 | Injection | SQLi, XSS, command injection, template injection |
| A04 | Insecure Design | Business logic flaws, race conditions |
| A05 | Security Misconfiguration | Default creds, verbose errors, CORS |
| A06 | Vulnerable Components | CVE scan, outdated dependencies |
| A07 | Auth Failures | Brute force, session fixation, JWT attacks |
| A08 | Data Integrity | Deserialization, CI/CD pipeline attacks |
| A09 | Logging Failures | Log injection, insufficient audit trail |
| A10 | SSRF | Internal service access, cloud metadata |
Phase 3: Exploitation (Dogrulama)
Her bulgu icin:
- Reproduce: Tekrarlanabilir adimlar yaz
- Proof: Etkiyi goster (ekran goruntusu, response)
- Impact: Gercek etki ne? (Data leak, RCE, account takeover)
- Scope: Etki alani ne kadar genis?
Phase 4: Verification
Bulgunun gercek oldugunu dogrula:
- False positive degil mi? Farkli kosullarda tekrarla
- Scope dogru mu? Sadece bir endpoint mi, yoksa sistemik mi?
- Severity dogru mu? Etkiyi abartma, kucumseme
Phase 5: Report
Yapilandirilmis bulgu formati (asagida)
Proof Levels
| Level | Tanim | Ornek |
|-------|-------|-------|
| L1 - Theoretical | Potansiyel risk, exploit edilmemis | "Bu endpoint input validate etmiyor" |
| L2 - Demonstrated | Bypass/leak gosterildi | "SQL injection ile hata mesaji leak etti" |
| L3 - Exploited | Tam exploit, veri erisimi | "Admin panel'e yetkisiz erisim saglandi" |
| L4 - Chained | Birden fazla vuln zincirlendi | "XSS + CSRF = Account takeover" |
Structured Finding Format
## [SEVERITY] Finding Title
**ID**: FINDING-001
**Severity**: Critical / High / Medium / Low / Informational
**Proof Level**: L1 / L2 / L3 / L4
**CVSS**: X.X (hesapla: cvss.org)
**CWE**: CWE-XXX
### Description
Ne bulundu, tek paragraf.
### Impact
Exploit edilirse ne olur?
### Steps to Reproduce
1. [Adim 1]
2. [Adim 2]
3. [Adim 3]
### Proof
[Screenshot, HTTP request/response, veya kod]
### Remediation
Nasil duzeltilir?
### References
- [OWASP link]
- [CWE link]
Source-to-Sink Taint Tracing
Kullanici input'unun tehlikeli bir fonksiyona ulasip ulasamadigini kontrol et:
Source (Input) ──▶ Transform/Sanitize? ──▶ Sink (Tehlikeli fonksiyon)
req.body.username ──▶ Validation var mi? ──▶ db.query(...)
req.query.redirect ──▶ URL whitelist var mi? ──▶ res.redirect(...)
req.headers.host ──▶ Sanitize var mi? ──▶ fetch(...)
Source'lar: req.body, req.query, req.params, req.headers, cookies, file uploads
Sink'ler: SQL query, eval(), exec(), redirect(), innerHTML, dangerouslySetInnerHTML
Agent Entegrasyonu
- security-analyst: Bu pipeline'i kullanarak tam guvenlik auditi yapar
- security-reviewer: Code review sirasinda vuln pattern'lerini kontrol eder
- code-reviewer: Security-relevant code degisikliklerinde flag kaldirir
Kurallar
- Yetki olmadan test YAPMA
- Rate limiting'e uy, sistemi cokertme
- Buldugun seyi raporla, exploit etme (beyond PoC)
- Hassas verileri rapordan cikar (maskeleme)
- Remediation onerisi ZORUNLU
Other skills for the same job
different authors, same section of the catalogue
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
This skill should be used when the user asks to "perform cloud penetration testing", "assess Azure or AWS or GCP security", "enumerate cloud resources", "exploit cloud misconfigurations", "test O365 security", "extract secrets from cloud environments", or "audit cloud infrastructure". It provides comprehensive techniques for security assessment across major cloud platforms.
You are a dependency security expert specializing in vulnerability scanning, license compliance, and supply chain security. Analyze project dependencies for known vulnerabilities, licensing issues, outdated packages, and provide actionable remediation strategies.
Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges
This skill should be used when the user asks to "escalate privileges on Linux", "find privesc vectors on Linux systems", "exploit sudo misconfigurations", "abuse SUID binaries", "exploit cron jobs for root access", "enumerate Linux systems for privilege escalation", or "gain root access from low-privilege shell". It provides comprehensive techniques for identifying and exploiting privilege escalation paths on Linux systems.
Expert malware analyst specializing in defensive malware research, threat intelligence, and incident response. Masters sandbox analysis, behavioral analysis, and malware family identification. Handles static/dynamic analysis, unpacking, and IOC extraction. Use PROACTIVELY for malware triage, threat hunting, incident response, or security research.
This skill should be used when the user asks to "use Metasploit for penetration testing", "exploit vulnerabilities with msfconsole", "create payloads with msfvenom", "perform post-exploitation", "use auxiliary modules for scanning", or "develop custom exploits". It provides comprehensive guidance for leveraging the Metasploit Framework in security assessments.
Expert in secure mobile coding practices specializing in input validation, WebView security, and mobile-specific security patterns. Use PROACTIVELY for mobile security implementations or mobile security code reviews.
How to use it
Take vibeeval/pentest-methodology from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.