hunting-http-parameter-pollution SKILL.md skillA
hunting-http-parameter-pollution from unboundcompute/security-agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add unboundcompute/security-agent-skills/hunting-http-parameter-pollution@git:20260903.6dac719Pins git:20260903.6dac719 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- unboundcompute/security-agent-skills
- Path
skills/hunting-http-parameter-pollution/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260903.6dac719, committed Sep 3, 2026
- Size
- 10,062 bytes
- Repository stars
- 26
- License
- MIT
Hunt HTTP parameter pollution, where the same parameter name appears more than once, or a parameter is shaped as an array, and two components in the request path disagree on how to resolve it. A validator, a gateway, or a filter reads one occurrence while the backend sink reads another, so a value that passes a check is not the value that is used, and a control is bypassed, an authorization decision is confused, or a payload is smuggled past a filter. First-versus-last-wins differentials…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Hunting HTTP parameter pollution: when two parsers disagree An HTTP request can carry the same parameter name twice, or shape a parameter as a list, and nothing in the protocol says which value wins. Each component decides on its own: one framework takes the first occurrence, another the last, a third concatenates them, a fourth exposes an array. Parameter pollution is the bug that appears when two components on the path make different choices about the same duplicated input. A gateway or a validator inspects one occurrence and approves the request; the backend that acts on the request reads a different occurrence. The value that was checked is not the value that is used. That gap bypasses a security filter, confuses an authorization or routing decision, or slips a payload past a web application firewall that examined the harmless copy. The vulnerability is entirely relational: a single parser is never wrong with itself, so the work is to find two parsers that differ and a check on one side of the difference. ## When to use - A request crosses more than one component that parses parameters (gateway, framework, backend, service). …
Read the whole file at its exact version.
How to install
mdr add unboundcompute/security-agent-skills/hunting-http-parameter-pollution@sha256:d84866f696a0edd4The line at the top of this page pins the label git:20260903.6dac719, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_37fj6pwb67hz347j)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 3, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10062 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
unboundcompute/security-agent-skills · 26 stars · license MIT · pushed 2026-09-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_37fj6pwb67hz347j GET https://markdownregistry.com/api/v1/resolve?ref=unboundcompute/security-agent-skills/hunting-http-parameter-pollution GET https://markdownregistry.com/api/v1/blob/d84866f696a0edd45a63f43666d8f12cfea84639cd374a6ab05675b5bf9c72a7
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.