Skip to content
Get packs

HTTP Request Smuggling Checklist

Gives the agent a security-testing checklist for finding HTTP request smuggling flaws in proxies and load balancers.

Source Download skill
Repository
SnailSploit/Claude-Red
Stars
10,230
Licence
MIT
Files
1 file

What it does

This skill loads a detailed offensive security checklist into the agent covering HTTP request smuggling: how front-end and back-end servers can disagree about where one HTTP request ends and the next begins. Once active, the agent walks through detection steps such as CL.TE, TE.CL and TE.TE header tests, HTTP/2 downgrade variants, WAF bypass ideas, and cache poisoning, and suggests next steps based on findings. It is written as a methodology for testing systems you are authorised to assess, and it contains example raw requests rather than scripts.

Great for

  • Penetration testers and bug bounty hunters who have written permission to test a specific target
  • Security engineers who want a structured reminder of smuggling variants when reviewing reverse proxy or load balancer configurations
  • Students learning how HTTP desync vulnerabilities work, ideally against intentionally vulnerable labs

Skip it if

  • Testing systems you do not own or have explicit authorisation to test, because sending these crafted requests can disrupt live services and may be illegal
  • Developers looking for a general web development or secure coding guide, since it focuses on attack techniques rather than defences
  • Non-security users, as the content assumes familiarity with HTTP parsing, proxies and Burp Suite-style tooling

Try asking

  • “Walk me through a checklist for testing whether our Nginx and HAProxy setup is vulnerable to CL.TE or TE.CL smuggling.”
  • “Help me design a timing-based detection test for proxy desync on a target we are authorised to assess.”
  • “Which HTTP/2 downgrade smuggling variants should I check on a CDN-fronted application?”
  • “Suggest next steps after my differential response test shows the second request returning a GPOST error.”
Step-by-step guide: how to use HTTP Request Smuggling ChecklistInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 1 original files, the MIT licence and an attribution note.

    offensive-request-smuggling.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip offensive-request-smuggling.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip offensive-request-smuggling.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Only use this on targets you are explicitly authorised to test, and state your scope to the agent up front.
  • Share your proxy or server stack (for example Nginx, HAProxy or ALB) so the agent can prioritise the relevant variants.
  • Use the agent to track which checklist items are done, then verify each finding manually in your own tooling before reporting.

What's inside

  • SKILL.md

Redistributed unmodified from SnailSploit/Claude-Red under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.