Individual skill

attack-patterns-reference

0upvotes

Use when classifying a verified web or WordPress behavior and selecting a related validation skill.

meta/attack-patterns-reference/SKILL.md

Read pinned source

Source commit 1260244136edc6ae698d76d3d526f503e322778d

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Instructions only
Last checked: Nov 9, 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): 1,366
Repository last updated: Nov 7, 2026
License: MIT

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

bug-bounty Repository topic
cloud-security Repository topic
firebase-hacking Repository topic
hermes-agent Repository topic
jwt-attacks Repository topic
offensive-security Repository topic
penetration-testing Repository topic
reconnaissance Repository topic
red-team Repository topic
security-automation Repository topic
meta Declared skill tag
reference Declared skill tag
patterns Declared skill tag
validation Declared skill tag
engineering Derived category

Files and excerpt

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

Browse files

SKILL.mdcore · 5,737 bytes
references/p-patterns.mddoc · 3,335 bytes

Read excerpt


# Attack Patterns Reference

This catalog maps observed web and WordPress behavior to the skill that owns
its validation. Pattern IDs are navigation labels. They do not establish
exploitability, severity, prevalence, or a confirmed attack path.

## When to Use

- A recon result needs to be classified before focused testing.
- Several verified behaviors may form a candidate attack path.
- A WordPress, CORS, XML-RPC, source-leak, or exposed-service signal needs an
  owning validation procedure.

Do not use the catalog as a scanner finding list or a substitute for the