http-protocol
Skill1 starsChanged 3 months agoMITView on GitHub
This is a thin human-facing router. Use skill.yaml as the source of truth for exact commands, inputs, outputs, and workflow chaining.
In this repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- agent-safetySkill
- ai-llmSkill
- apiSkill
- asset-graphSkill
- authSkill
- auto-researchSkill
- binary-analysisSkill
- business-logicSkill
- campaignSkill
- cicd-securitySkill
- cloudSkill
- cors-csrfSkill
- coverageSkill
- cross-accountSkill
- domain-modelSkill
- enrichmentSkill
- evaluation-harnessSkill
- file-uploadSkill
- graphql-auditSkill
- identity-domainSkill
- impact-verifierSkill
- meme-coin-auditSkill
- mobileSkill
- modern-browserSkill
- nuclei-scannerSkill
- oob-infraSkill
- osintSkill
- personaSkill
- plannerSkill
- privescSkill
- program-memorySkill
- race-conditionSkill
- rceSkill
- reconSkill
- reportingSkill
- sastSkill
- scope-managerSkill
- skill-scientistSkill
- sqliSkill
- ssrfSkill
- standard-catalogSkill
- technique-kbSkill
- traffic-corpusSkill
- triage-validationSkill
- vuln-intelSkill
- web3-auditSkill
- xssSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Start with http1-smuggling unless prior evidence points to a more specific workflow.
- Very specific: line 17
Follow each workflow next mapping in skill.yaml after reviewing generated findings.
- Distinctive: line 18
If a workflow has no script reference, treat it as a manual or tool-native workflow and use the closest phase runbook when available.
≈ “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
Http Protocol
Overview
HTTP protocol-layer attacks — request smuggling (HTTP/1+2), cache poisoning, cache deception, URL parser differentials, email parser bypasses, TLS 0-RTT replay
This is a thin human-facing router. Use skill.yaml as the source of truth for exact commands, inputs, outputs, and workflow chaining.
Quick Reference
- Skill:
http-protocol - Severity range:
info,low,medium,high,critical - Required tools:
curl,python3,nc,openssl,jq - Expected input files:
live_urls.txt,tech_fingerprint.json - Scope check: confirm authorization before running intrusive or authenticated testing.
Workflow Selection
- Start with
http1-smugglingunless prior evidence points to a more specific workflow. - Follow each workflow
nextmapping inskill.yamlafter reviewing generated findings. - If a workflow has no script reference, treat it as a manual or tool-native workflow and use the closest phase runbook when available.
- Runbooks: use
runbooks/and select the closest phase runbook when workflow names do not map 1:1.
Available Workflows
| Workflow | Purpose | Script paths | Primary outputs | Evidence |
http1-smuggling | Test CL.TE, TE.CL, and TE.TE HTTP/1.1 request smuggling using Python socket-based probes with obfuscated Transfer-Encoding variants | .claude/skills/http-protocol/scripts/http_smuggling_probe.py | $OUTDIR/http-protocol/smuggling/http1_findings.jsonl | $OUTDIR/http-protocol/smuggling/evidence/ |
http2-smuggling | Test H2.CL and H2.TE downgrade smuggling where HTTP/2 frontend connects to HTTP/1.1 backend via Content-Length or Transfer-Encoding injection | .claude/skills/http-protocol/scripts/http_smuggling_probe.py | $OUTDIR/http-protocol/smuggling/http2_findings.jsonl | $OUTDIR/http-protocol/smuggling/evidence/ |
cache-poisoning | Test web cache poisoning via unkeyed header injection (X-Forwarded-Host, X-Forwarded-Scheme, X-Original-URL), fat GET body poisoning, and parameter cloaking | .claude/skills/http-protocol/scripts/cache_poison_probe.py | $OUTDIR/http-protocol/cache/poison_findings.jsonl | $OUTDIR/http-protocol/cache/evidence/ |
cache-deception | Test web cache deception attacks where sensitive pages get cached as static files via path confusion (account.css, profile.js, .css/.js extensions on dynamic paths) | .claude/skills/http-protocol/scripts/cache_deception_probe.py | $OUTDIR/http-protocol/cache/deception_findings.jsonl | $OUTDIR/http-protocol/cache/evidence/ |
url-parser-differential | Test URL parser differentials — backslash vs forward slash normalization, URL encoding confusion, double encoding, Unicode UTF-8 overlong bypasses, null-byte truncation, path parameter separation | .claude/skills/http-protocol/scripts/url_parser_differential.py | $OUTDIR/http-protocol/url-parser/differential_findings.jsonl | $OUTDIR/http-protocol/url-parser/evidence/ |
email-parser-bypass | Test email parser bypasses — encoded @ signs, quoted local-parts, comments in emails, multiple @ signs, backslash escapes, Unicode confusables, display name injection, based on PortSwigger "Splitting the email atom" research | .claude/skills/http-protocol/scripts/email_parser_bypass.py | $OUTDIR/http-protocol/email-parser/bypass_findings.jsonl | $OUTDIR/http-protocol/email-parser/evidence/ |
early-data-probe | TLS 1.3 0-RTT early data replay testing — checks if server accepts early data, replays POST requests creating duplicate side effects, detects Early-Data header for GET replay feasibility | .claude/skills/http-protocol/scripts/early_data_probe.py | $OUTDIR/http-protocol/tls/early_data_findings.jsonl | $OUTDIR/http-protocol/tls/evidence/ |
verify | Verify protocol findings with raw socket captures and secondary confirmation probes | No script reference in skill.yaml command. | $OUTDIR/http-protocol/verified/manifest.txt | $OUTDIR/http-protocol/verified/ |
Evidence Required
- Save raw request and response data for each confirmed finding.
- Include timestamps, affected target, exact workflow name, tool versions, and reproduction steps.
- Store screenshots or terminal captures in the workflow evidence directory when the workflow defines one.
- Evidence templates from
skill.yaml: smuggling_curl: curl -v raw smuggling request/response paircache_header_dump: curl -sD headers.txt showing cache hit with poisoned valuedeception_body: Full response body showing PII/CSRF tokens in cached static fileurl_diff_response: Side-by-side curl of normal vs encoded path responsesemail_injection_log: curl log showing crafted email accepted at registrationearly_data_capture: openssl s_client early-data send + replay confirmation
References
- Source of truth:
skill.yaml - Runbooks:
runbooks/ - OWASP WSTG:
WSTG-CONF-01,WSTG-ATHZ-01 - OWASP API Top 10:
API7:2019,API8:2019
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.

