pentest-web
Skill8 starsChanged 3 months agoMITView on GitHub
Web application security testing methodology — OWASP Top 10, SSRF, IDOR, auth bypass, injection-class advisory. Burp/ZAP output analysis. Triggers on web pentest, OWASP, SQL injection, XSS, SSRF, IDOR, auth bypass, Burp output, ZAP, parameter pollution, request smuggling.
In this repository63 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ai-automationSkill
- consultingSkill
- contentSkill
- customer-successSkill
- data-analyticsSkill
- designSkill
- design-tokensSkill
- developmentSkill
- devopsSkill
- ecommerceSkill
- emailSkill
- expo-app-configSkill
- expo-config-pluginSkill
- expo-dev-clientSkill
- expo-eas-buildSkill
- expo-eas-submitSkill
- expo-eas-updateSkill
- expo-modulesSkill
- expo-notificationsSkill
- expo-orchestratorSkill
- expo-prebuildSkill
- expo-routerSkill
- expo-troubleshootingSkill
- financeSkill
- frontend-tasteSkill
- marketingSkill
- market-researchSkill
- mobileSkill
- pentest-adSkill
- pentest-apiSkill
- pentest-bizlogicSkill
- pentest-bugbountySkill
- pentest-cicdSkill
- pentest-cloudSkill
- pentest-credentialsSkill
- pentest-ctfSkill
- pentest-detectionSkill
- pentest-engagementSkill
- pentest-exploit-chainSkill
- pentest-forensicsSkill
- pentest-llmSkill
- pentest-malwareSkill
- pentest-mobileSkill
- pentest-opsec-evidenceSkill
- pentest-orchestratorSkill
- pentest-privescSkill
- pentest-reconSkill
- pentest-reportSkill
- pentest-socialSkill
- pentest-stigSkill
- pentest-threat-modelSkill
- pentest-wirelessSkill
- productivitySkill
- productSkill
- salesSkill
- security-checkSkill
- securitySkill
- seo-crawl-budgetSkill
- seoSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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
- Distinctive: line 46
If the user pastes a Burp Pro/CE or ZAP report:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
pentest-web
Web app attack-surface advisory + Burp/ZAP output analysis + OWASP Top 10 methodology. Live exploit composing requires a scope declaration; no automatic exploit execution.
Triggers
- "OWASP Top 10 test"
- "review the Burp output"
- "did we find a SQL injection"
- "let's run an XSS test"
- "can you look for SSRF / IDOR / auth bypass"
- "request smuggling"
OWASP Top 10 Checklist
| # | Category | Test Approach |
| A01 | Broken Access Control | Yatay/dikey IDOR, force browse, JWT manipulation |
| A02 | Cryptographic Failures | TLS config, password hash, sensitive data unencrypted |
| A03 | Injection | SQLi (in-band, blind, OOB), NoSQL, OS command, XPath |
| A04 | Insecure Design | Missing rate limit, business logic flaw |
| A05 | Security Misconfig | Default cred, verbose error, exposed admin panel |
| A06 | Vulnerable Components | Dependency CVE, framework version |
| A07 | Auth Failures | Brute force, password reset, session fix |
| A08 | Software/Data Integrity | Unsigned update, deserialization |
| A09 | Logging Failures | Bypass detection, audit gap |
| A10 | SSRF | Internal port reach, cloud metadata steal |
Burp/ZAP Output Analysis
If the user pastes a Burp Pro/CE or ZAP report:
## Burp Active Scan — analysis
### True Positive
- High: SQL Injection in /api/users?id= (Time-based, MySQL)
- Payload: `1' AND SLEEP(5)-- -`
- Impact: Full DB read + potential RCE (if FILE priv exists)
- Medium: Reflected XSS in /search?q= (no CSP)
### False Positive (filtered out)
- Info: Server header reveals nginx — not an info leak, low fix priority
- Low: Cookie missing HttpOnly — server-only cookie, no JS access
### Suggested Manual Test
- IDOR check /api/users/{id} — auth bypass attempt
- Race condition /api/purchase (5 parallel requests)
- JWT alg=none + RSA key swap via alg=HS256Common Methodology Flow
1. Recon: subfinder + httpx + wappalyzer
2. Crawl: ffuf / gobuster / katana (rate-limited)
3. Param discovery: paramspider / Arjun
4. Active probe: nuclei templates + manual Burp
5. Auth test: JWT decode + signature check + algorithm swap
6. Bizlogic: race, IDOR, price manipulation (hand off to pentest-bizlogic)
7. Report: OWASP severity + CVSS + remediationSuggested Commands (with scope)
# MODERATE — content discovery (rate limit)
ffuf -w wordlist.txt -u https://<target>/FUZZ -t 20 -p 0.1 -mc 200,301,403 -o ffuf_<target>_$(date +%Y%m%d_%H%M%S).json
# MODERATE — auto template scan
nuclei -u https://<target> -severity medium,high,critical -rate-limit 50 -o nuclei_<target>_$(date +%Y%m%d_%H%M%S).txt
# LOUD — SQLi targeted (single param + level 1 only)
# sqlmap use is suggested, but composing requires a scope declarationJWT Test Suggestion
# Manual decode (QUIET, sends no request to any target)
echo <token> | cut -d. -f2 | base64 -d | jq .
# Common bypass attempts
# alg: "none" -> skip the signature
# alg: HS256 + RSA pub -> HMAC with the public key
# kid: ../../etc/passwd -> path traversal
# exp manipulationCSP / Header Analysis
# QUIET — headers only
curl -sI https://<target> | grep -iE 'content-security-policy|x-frame-options|strict-transport|x-content-type'Out-of-Scope
- Live sqlmap orchestration (the user runs authorized
sqlmap) - Mass scan, parallel attacks on multiple targets
- Automated exploitation (PoC validation in pentest-exploit-chain)
- DoS attempt
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
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.

