traffic-proxy
Skill4 starsChanged 8 months agoMITView on GitHub
Request/response interception playbook for logic bug hunting with mitmproxy and OWASP ZAP.
In this repository8 other files it gives its agents.
- bug-huntingSkill
- exploitationSkill
- pentest-toolsSkill
- planningSkill
- reconSkill
- reportingSkill
- research-notesSkill
- xray-suiteSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
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 8
Use this skill when automated scans find a suspicious workflow but proof needs manual request mutation.
- Distinctive: line 23
Run proxies only on authorized targets and in scoped windows.
- Distinctive: line 24
Start with read-only capture before mutation.
- Distinctive: line 25
Keep request rate low under WAF/rate-limit pressure.
- Distinctive: line 26
Prefer replaying one request class at a time with strict evidence notes.
- Distinctive: line 38
Use constrained scans first.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
traffic-proxy
Use this skill when automated scans find a suspicious workflow but proof needs manual request mutation.
Core tools
- mitmproxy / mitmdump: lightweight CLI interception and Python scripting.
- zaproxy / zap-cli: baseline active checks + scripting-friendly automation.
When to use
- Session/auth workflow inconsistencies (invite, verify-otp, role change, checkout flow).
- Business logic checks where endpoint order/state matters.
- Header trust-boundary testing (custom auth blobs, forwarded headers, rewrite headers).
Safe execution guidance
- Run proxies only on authorized targets and in scoped windows.
- Start with read-only capture before mutation.
- Keep request rate low under WAF/rate-limit pressure.
- Prefer replaying one request class at a time with strict evidence notes.
mitmproxy quick patterns
- Capture mode:
mitmdump --listen-host 127.0.0.1 --listen-port 8081 --set flow_detail=1 - Save flows:
mitmdump -w reports/output/<target>/mitm.flow - Replay selected flow IDs after controlled modifications.
ZAP quick patterns
- Quick baseline:
zaproxy -cmd -quickurl https://<target> -quickprogress - Scripted run:
zap-cli quick-scan --self-contained --spider https://<target> - Use constrained scans first; avoid broad active scans until recon confidence is high.
Evidence contract
For each proxy-assisted finding, capture:
- Original request and response
- Mutated request and response
- Boundary violated (auth, role, object ownership, state transition)
- Reproducible minimal steps
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.