CtrlK
BlogDocsLog inGet started
Tessl Logo

hunt-host-header

Hunt Host Header Injection — password reset poisoning → ATO, web cache poisoning via unkeyed Host/X-Forwarded-Host, routing-based SSRF (Host picks upstream → cloud metadata/internal services), path-override SSRF/ACL-bypass (X-Original-URL/X-Rewrite-URL), OAuth redirect_uri/issuer poisoning, and absolute-URL link poisoning in emails. High to Critical when it reaches ATO or mass cache poisoning. Built on public Host-header research (PortSwigger 'Practical web cache poisoning' + James Kettle, and the classic password-reset-poisoning class). Use on any forgot-password flow, CDN/reverse-proxy-fronted app, OAuth/OIDC endpoint, or absolute-URL-in-email feature.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable commands and a clearly sequenced, validation-heavy workflow, but it is a long monolithic file with prose that could be tightened and payload lists that could be externalized into reference files for better progressive disclosure.

Suggestions

Move the per-phase curl payload blocks into a references/ file (e.g. PAYLOADS.md) and link from each phase, leaving SKILL.md as the overview-plus-methodology; this would lift progressive_disclosure and reduce inline token weight.

Tighten the prose between command blocks (e.g. the Grounding/Provenance narrative and the Phase 2 'Mechanism' paragraph) to the minimum needed to disambiguate the commands, improving conciseness.

If externalizing payloads, keep one short canonical example per phase inline so actionability is preserved without the full payload list.

DimensionReasoningScore

Conciseness

The body is dense with executable commands that earn their place, but interleaved explanatory prose ('Mechanism: this is a reflection bug, not an OOB bug') and a lengthy provenance narrative make it tighten-able; not 3 due to length, not 1 because it avoids explaining basic concepts Claude already knows.

2 / 3

Actionability

Every phase provides fully executable, copy-paste-ready curl commands parameterized with $TARGET/$COLLAB, matching the executable-and-specific anchor.

3 / 3

Workflow Clarity

A clear Phase 1–5 sequence with explicit 'Confirm:' checkpoints, 'False-positive killers (mandatory)', and a 'Validation (house discipline)' feedback loop, matching the explicit-validation anchor.

3 / 3

Progressive Disclosure

A single 266-line monolithic file with no bundle files and long inline payload blocks that could be split into reference files; well-sectioned but content that should be separate is inline, matching the some-structure anchor rather than 3 (not a simple under-50-line skill) or 1 (well-organized, not a wall of text).

2 / 3

Total

10

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and distinctive: it lists concrete attack classes and gives explicit use-when triggers tied to natural features (forgot-password, CDN/proxy, OAuth, email links). It avoids first/second-person voice and over-claiming.

DimensionReasoningScore

Specificity

Enumerates multiple concrete attack actions — 'password reset poisoning → ATO', 'web cache poisoning via unkeyed Host/X-Forwarded-Host', 'routing-based SSRF', 'path-override SSRF/ACL-bypass', 'OAuth redirect_uri/issuer poisoning' — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers both what (the enumerated attack classes) and when ('Use on any forgot-password flow...'), directly matching the what-AND-when anchor.

3 / 3

Trigger Term Quality

The 'Use on any forgot-password flow, CDN/reverse-proxy-fronted app, OAuth/OIDC endpoint, or absolute-URL-in-email feature' clause covers natural trigger terms a tester would say; not 2 because common variations are all present rather than partially missing.

3 / 3

Distinctiveness Conflict Risk

'Host Header Injection' is a clearly bounded niche with distinct triggers, unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
elementalsouls/Claude-BugHunter
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.