Individual skill

probing-dangerous-http-methods

Discover advertised HTTP methods with bounded OPTIONS requests, then verify separately selected methods only under explicit scoped ROE permission. Use when auditing post-deploy method policy or approved WebDAV/proxy experiments. Requires disposable fixtures, conditional cleanup and private evidence for writes; reports missing or ambiguous evidence as inconclusive. Trigger with "audit http methods", "trace check", or "webdav probe".

plugins/security/penetration-tester/skills/probing-dangerous-http-methods/SKILL.md

Read pinned source

Source commit 0500b275e963c027f6b410e8c49c0446945c574e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 12, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
2,916
Repository last updated
Nov 12, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Probing Dangerous HTTP Methods

## Overview

Compare anonymous HTTP method capabilities with the owner's explicit policy.
The default sends only OPTIONS to the exact supplied URL, follows no redirect,
and does not read its response body. Allow is advertisement, not proof of a
write, an open proxy or exploitation. An API path name does not establish policy.

Active experiments require separate method selection, a structurally valid ROE,
an exclusive private ledger and bounded postcondition evidence. The checker does
not verify signing identity or establish legal authorization. Obtain the owner's
approval independently before executing an experiment.
Back to top