skills/headers/SKILL.md
Route security testing for HTTP header trust, origin validation, proxy context, route overrides, host routing, method overrides, content negotiation, and auth-header precedence.
npx skillsauth add ghostonbutterbread/bug-bounty-harness headersInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use when the security question depends on how the server interprets request headers.
This is a RAG-style mechanism skill. Classify the header lane first, load one focused reference pack, then test only the smallest safe mutation set.
$HARNESS_ROOT; default is /home/ryushe/projects/bug_bounty_harness.$HARNESS_ROOT/prompts/headers-context-pack.md.Origin or Referer behavior -> $HARNESS_ROOT/skills/headers/references/technique-packs/origin.md$HARNESS_ROOT/skills/headers/references/technique-packs/proxy-trust.md$HARNESS_ROOT/skills/headers/references/technique-packs/route-override.md$HARNESS_ROOT/skills/headers/references/technique-packs/method-override.md$HARNESS_ROOT/skills/headers/references/technique-packs/host-routing.mdAccept, Content-Type, charset, compression, or API version behavior -> $HARNESS_ROOT/skills/headers/references/technique-packs/content-negotiation.md$HARNESS_ROOT/skills/headers/references/technique-packs/auth-context.md$HARNESS_ROOT/prompts/headers-playbook.md for deep review, stuck analysis, or report writing.403 endpoint -> /403/bypass/csrf or future /cors/access-control or /idor/single-request-grabberPromote only when header behavior changes authorization, routing, origin trust, object/account boundary, parser behavior, or security policy in a reproducible way.
Do not promote cosmetic error changes, cache artifacts, same-content redirects, public data, or caller-owned access.
Stop before touching real-user data, bypassing explicit target policy, escalating outside approved accounts, performing destructive state changes, or continuing after rate-limit/WAF enforcement. Route those cases to /waf, /403, /access-control, or Ryushe for approval.
Write notes under $HARNESS_SHARED_BASE/{program}/ghost/headers/ or the owning finding lane.
Record full URLs, baseline headers, mutated headers, auth state, owned account/resource used, response delta, loaded reference pack, proof/no-proof result, and next safe test.
testing
Systematic live request mutation: flip booleans, field ops, headers, content-type, parser differentials, replay vs intercept, null/empty testing. Inherits live-testing-policy scope/rate/ownership rules.
development
Test password reset, forgot-password, reset-token, email reset, and account recovery flows for account takeover risks.
tools
Targeted param/field discovery using tech stack clues, naming conventions, and controlled-rate ffuf — then feeds findings into request-exploration for mutation. Not brute-force; informed and scoped.
testing
Ghost-only workflow for creating approved bug bounty test accounts and saving credential references.