Individual skill
webapp-probe
Probe a web app for what it exposes or leaks - passively from captured traffic and actively against the target. Use to assess a web app's exposure or review Burp/ZAP history.
skills/applicative-pentest/webapp-probe/SKILL.md
Source commit 0c1bc93fd5124e7a862d61c1b434f32ba8790e3a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 153
- Repository last updated
- Nov 7, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-security Repository topic
- ai-skills Repository topic
- security-skills Repository topic
- dynamic-workflow Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 25,149 bytesSKILL.mdcore · 25,149 bytesSKILL.mdcore · 25,149 bytesSKILL.mdcore · 25,149 bytesSKILL.mdcore · 25,149 bytesSKILL.mdcore · 25,149 bytesSKILL.mdcore · 25,149 bytesSKILL.mdcore · 25,149 bytesSKILL.mdcore · 25,149 bytesreferences/directory-signatures.mddoc · 4,138 bytesreferences/error-signatures.mddoc · 11,934 bytesreferences/secret-regexes.mddoc · 7,231 bytes
Read excerpt
## Contents
- Scope & authorization (blast-radius labels)
- Passive analysis of captured traffic:
1. Missing or weak security headers
2. Insecure session cookies
3. Hardcoded secrets & API tokens in bodies
4. Improper error handling (stack traces, DB errors, debug pages)
5. Outdated / dev-mode technology fingerprints
6. RCE-prone parameters in captured requests
- Active probing of the live target:
7. Disclosure-path brute (.git/config/logs, CVE paths)
8. Outdated / vulnerable software port probe
9. Wayback forgotten-endpoint mining + re-probe
10. Dependency confusion (sourcemaps -> npm)