/awesome-web-security
Curated lookup over qazbnm456/awesome-web-security.
Always fetches the latest index from raw.githubusercontent.com — no stale snapshot.
When to use
A user asks for resources, references, learning paths, or tools related to web
security topics: XSS, SQLi, CSRF, SSRF, XXE, OAuth/JWT, prototype pollution,
deserialization, SAML, file upload, web cache poisoning, WAF / CSP evasion,
browser exploitation, recon (subdomain enumeration, OSINT), DNS rebinding,
CTF write-ups, bug bounty methodology, defensive tooling, payload lists,
cheatsheets, or related blogs.
When NOT to use
- The user wants to attack a target they do not own and have not been
authorized to test. Decline and ask for scope: own system, CTF,
authorized pentest, academic research, or defensive analysis.
- The user is asking for malware authoring, mass scanning of unowned
infrastructure, or detection-evasion guidance for offensive purposes.
- The question has no security framing — it's general programming or
framework usage. Hand off to a non-security skill.
How
- Fetch the index with WebFetch:
https://raw.githubusercontent.com/qazbnm456/awesome-web-security/master/data/index.json
- Parse the JSON. Schema:
{
"schema_version": "1",
"categories": [{"key": "xss", "title": "...", "h_level": 3, "parent": "intro", "anchor": "xss"}],
"entries": [{
"id": "xss-google-app-security",
"url": "...",
"title": "...",
"author": {"name": "...", "url": "..."},
"category": "xss",
"type": "article|tool|cheatsheet|video|book|community|payload-list",
"languages": ["en", "zh", "jp"],
"difficulty": "intro|intermediate|advanced",
"date_added": "YYYY-MM-DD",
"archive_url": "...|null",
"last_checked": "YYYY-MM-DD|null",
"status": "active|dead|archived-only|quarantined"
}]
}
- Filter by:
category matching the user's topic (a topic may map to several
categories — for "XSS" check xss, tools-xss, tricks-xss,
practices-xss, evasions-csp as relevant).
languages: default to the user's language; fall back to en.
difficulty: include all unless the user asked for "intro" or "deep".
type: filter by what the user wants — articles, tools, cheatsheets,
payload lists, etc.
- Rank by:
- "Latest" requests →
date_added DESC.
- "Deep dive" requests → prefer
difficulty: advanced, then by depth
signals (long titles, payload-list type, presence of author URL).
- "Tools" requests →
type: tool only.
- Return 5–7 entries; for each include title, URL, archive_url fallback if
status != active, and a one-line value statement explaining what this
entry teaches.
Safety guardrails
- Refuse to assist with unauthorized targeting. Ask for scope.
- Frame all results defensively / educationally.
- For
payload-list entries, append: "Test payloads only against systems
you own or have written authorization to test."
- Do not chain entries into an attack playbook against a named real target.
Output format
For each result:
Title — author • difficulty • type
One line on what this teaches and why it matters.
(Archive fallback: archive_url) — included only when status != active.
End with:
Cited from qazbnm456/awesome-web-security. Full list and categories at the README.
Failure handling
- JSON fetch fails (network, 404, parse error) → respond:
"The awesome-web-security index is temporarily unreachable. Try again
shortly, or visit https://github.com/qazbnm456/awesome-web-security
directly." Do NOT fabricate entries.
- No matches in the requested category → say so explicitly. Offer adjacent
categories from
categories[].parent chain.
Examples
User: "I'm learning XSS, give me intermediate-level resources in English."
→ Filter category matching xss, tools-xss, tricks-xss, evasions-csp;
languages contains en; difficulty in intermediate or advanced;
rank by date_added DESC; return top 5–7.
User: "我想找最新的 SSRF 文章。"
→ Filter category matching ssrf, tricks-ssrf, tools-ssrf;
languages contains zh; rank by date_added DESC; return in Chinese.
User: "What's a good XSS payload list?"
→ Filter category: xss AND type: payload-list; rank by depth signals.
Append the unauthorized-testing reminder.
1---2name: awesome-web-security3description: "Looks up curated web security learning resources (XSS, SQLi, CSRF, SSRF, OAuth/JWT, deserialization, SAML, recon, evasion, defensive tooling, CTF). Filters by topic, difficulty, language, and resource type. Returns top references with archive fallbacks. Defensive and educational use only."4when_to_use: "XSS, SQL injection, CSRF, SSRF, XXE, OAuth, JWT, prototype pollution, deserialization, SAML, file upload, web cache poisoning, WAF evasion, CSP bypass, browser exploitation, subdomain enumeration, OSINT, web security, penetration testing references, bug bounty resources, CTF web challenges, payload list, security cheatsheet, awesome list, 资安, 渗透, 学习资源, 安全, 漏洞, セキュリティ, ペンテスト, 脆弱性"5metadata:6 source: https://skillmd.com/skills/qazbnm456/awesome-web-security7 version: "1.0.0"8---910# /awesome-web-security1112Curated lookup over [qazbnm456/awesome-web-security](https://github.com/qazbnm456/awesome-web-security).13Always fetches the latest index from `raw.githubusercontent.com` — no stale snapshot.1415## When to use1617A user asks for resources, references, learning paths, or tools related to web18security topics: XSS, SQLi, CSRF, SSRF, XXE, OAuth/JWT, prototype pollution,19deserialization, SAML, file upload, web cache poisoning, WAF / CSP evasion,20browser exploitation, recon (subdomain enumeration, OSINT), DNS rebinding,21CTF write-ups, bug bounty methodology, defensive tooling, payload lists,22cheatsheets, or related blogs.2324## When NOT to use2526- The user wants to attack a target they do not own and have not been27 authorized to test. Decline and ask for scope: own system, CTF,28 authorized pentest, academic research, or defensive analysis.29- The user is asking for malware authoring, mass scanning of unowned30 infrastructure, or detection-evasion guidance for offensive purposes.31- The question has no security framing — it's general programming or32 framework usage. Hand off to a non-security skill.3334## How35361. Fetch the index with WebFetch:37 `https://raw.githubusercontent.com/qazbnm456/awesome-web-security/master/data/index.json`382. Parse the JSON. Schema:39 ```40 {41 "schema_version": "1",42 "categories": [{"key": "xss", "title": "...", "h_level": 3, "parent": "intro", "anchor": "xss"}],43 "entries": [{44 "id": "xss-google-app-security",45 "url": "...",46 "title": "...",47 "author": {"name": "...", "url": "..."},48 "category": "xss",49 "type": "article|tool|cheatsheet|video|book|community|payload-list",50 "languages": ["en", "zh", "jp"],51 "difficulty": "intro|intermediate|advanced",52 "date_added": "YYYY-MM-DD",53 "archive_url": "...|null",54 "last_checked": "YYYY-MM-DD|null",55 "status": "active|dead|archived-only|quarantined"56 }]57 }58 ```593. Filter by:60 - `category` matching the user's topic (a topic may map to several61 categories — for "XSS" check `xss`, `tools-xss`, `tricks-xss`,62 `practices-xss`, `evasions-csp` as relevant).63 - `languages`: default to the user's language; fall back to `en`.64 - `difficulty`: include all unless the user asked for "intro" or "deep".65 - `type`: filter by what the user wants — articles, tools, cheatsheets,66 payload lists, etc.674. Rank by:68 - "Latest" requests → `date_added` DESC.69 - "Deep dive" requests → prefer `difficulty: advanced`, then by depth70 signals (long titles, payload-list type, presence of author URL).71 - "Tools" requests → `type: tool` only.725. Return 5–7 entries; for each include title, URL, archive_url fallback if73 `status != active`, and a one-line value statement explaining what this74 entry teaches.7576## Safety guardrails7778- Refuse to assist with unauthorized targeting. Ask for scope.79- Frame all results defensively / educationally.80- For `payload-list` entries, append: "Test payloads only against systems81 you own or have written authorization to test."82- Do not chain entries into an attack playbook against a named real target.8384## Output format8586For each result:8788> **[Title](url)** — *author* • *difficulty* • *type*89> One line on what this teaches and why it matters.90> *(Archive fallback: archive_url)* — included only when `status != active`.9192End with:9394> Cited from [qazbnm456/awesome-web-security](https://github.com/qazbnm456/awesome-web-security). Full list and categories at the README.9596## Failure handling9798- JSON fetch fails (network, 404, parse error) → respond:99 "The awesome-web-security index is temporarily unreachable. Try again100 shortly, or visit https://github.com/qazbnm456/awesome-web-security101 directly." Do NOT fabricate entries.102- No matches in the requested category → say so explicitly. Offer adjacent103 categories from `categories[].parent` chain.104105## Examples106107User: "I'm learning XSS, give me intermediate-level resources in English."108→ Filter `category` matching `xss`, `tools-xss`, `tricks-xss`, `evasions-csp`;109 `languages` contains `en`; `difficulty` in `intermediate` or `advanced`;110 rank by `date_added` DESC; return top 5–7.111112User: "我想找最新的 SSRF 文章。"113→ Filter `category` matching `ssrf`, `tricks-ssrf`, `tools-ssrf`;114 `languages` contains `zh`; rank by `date_added` DESC; return in Chinese.115116User: "What's a good XSS payload list?"117→ Filter `category: xss` AND `type: payload-list`; rank by depth signals.118 Append the unauthorized-testing reminder.