[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6P6950HMB4MGEMQ4EET98EB":3,"skill-same:01M6P6950HMB4MGEMQ4EET98EB":82},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":30,"publishedAt":51,"linkOnly":52,"markdownContent":53,"markdownBody":54,"frontMatter":55,"refName":44,"commitSha":63,"skillDirectory":64,"forksCount":13,"repositoryHtmlUrl":65,"repositoryHomepageUrl":6,"ownerHtmlUrl":66,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":67,"install":68,"resources":81},"01M6P6950HMB4MGEMQ4EET98EB","hunt-spa-api",null,"Discover a single-page-app's hidden backend API from its public JS bundle, then test that API for broken access control \u002F missing authentication.","duc-duy-1612\u002FOnline-Delivery-Systems-Web","duc-duy-1612","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F192231384?v=4","01M6NSDKQQDKVTHZ8DZMZ1VYY6","01M6NSDKW8DDVTQHBT1HBDDJPT",0,"MIT","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fhunt-spa-api\u002FSKILL.md",[17,22,25],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":26,"categoryName":27,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50],"hunt spa api","api","hunt","spa","backend api","relevant","offensive","scripts","scope","app","commands","discover","testing","main","community","only","broken","access","authentication","security","2026-11-10 10:12:30",false,"---\nname: hunt-spa-api\ndescription: Discover a single-page-app's hidden backend API from its public JS bundle,\n  then test that API for broken access control \u002F missing authentication.\ncategory: security\nrisk: offensive\nsource: https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter\nsource_repo: elementalsouls\u002FClaude-BugHunter\nsource_type: community\ndate_added: '2026-09-20'\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter\u002Fblob\u002Fmain\u002FLICENSE\ncompatibility: Requires explicit written authorization for a target scope plus the\n  relevant testing tools for this technique. Docs-only; helper scripts and commands\n  not bundled.\nsources: authorized-engagement\nreport_count: 1\n---\n> **⚠️ AUTHORIZED USE ONLY**\n> This skill is for educational purposes or authorized security assessments only.\n> You must have explicit, written permission from the system owner before using this tool.\n> Misuse of this tool is illegal and strictly prohibited.\n\n> **Mandatory confirmation gate**\n> Before running any command that probes, exploits, changes, persists on, extracts data from, or attempts credential access against a target:\n> 1. Ask the user to state the exact target URL, IP, account, or resource.\n> 2. Ask the user to confirm written authorization and the permitted scope.\n> 3. Show the exact command(s) and explain their expected effect.\n> 4. Wait for explicit confirmation in the current conversation.\n>\n> Without that confirmation, remain read-only and provide defensive guidance only. Prefer a sandbox, disposable VM, or controlled lab.\n\n## When to use this skill\n\nTrigger when:\n- A target host returns a tiny HTML shell + big `\u002Fstatic\u002Fjs\u002F*.js` or `\u002F_next\u002Fstatic\u002F*` bundles (React\u002FVue\u002FAngular\u002FNext\u002FSvelte SPA)\n- You see a subdomain named `console`, `app`, `dashboard`, `portal`, `admin`, `panel`, `manage`, `internal`\n- Recon surfaces any `*api*`, `*-api*`, `api.*` host\n- A login page is OAuth\u002FSSO-gated (the *frontend* auth tells you nothing about whether the *API* enforces auth)\n\nThe core insight: **a SPA is a client to a backend API, and it ships the full map of that API — hosts, routes, sometimes keys — to anyone who views source.** The login page being protected says nothing about whether the API behind it checks tokens. Auth is frequently enforced on the *gateway\u002Flogin* and missing on a *route group* of the API.\n\nDO NOT skip this because \"the app needs login\" — that's exactly when this pays off.\n\n---\n\n## The play (5 steps)\n\n### 1. Pull the shell + enumerate the bundles\n```bash\ncurl -s https:\u002F\u002Fconsole.target.com\u002F -o index.html\n# React\u002FCRA:\ngrep -oE '\u002Fstatic\u002Fjs\u002F[^\"]+\\.js' index.html\n# Next.js:\ngrep -oE '\u002F_next\u002Fstatic\u002F[^\"]+\\.js' index.html\n# generic:\ngrep -oiE 'src=\"[^\"]+\\.js[^\"]*\"' index.html\n```\nDownload every bundle (they can be multi-MB — that's fine, it's all route data):\n```bash\nmkdir bundles\nfor j in $(grep -oE '\u002Fstatic\u002Fjs\u002F[^\"]+\\.js' index.html | sort -u); do\n  curl -s \"https:\u002F\u002Fconsole.target.com$j\" -o \"bundles\u002F$(echo \"$j\"|tr '\u002F' '_')\"\ndone\n```\n\n### 2. Harvest API hosts, routes, and secrets from the bundles\n```bash\nB=bundles\u002F*.js\n# Backend API hosts (incl. dev\u002Fbeta\u002Fstaging variants — often weaker auth)\ngrep -ohiE 'https:\u002F\u002F[a-z0-9.-]*(api|console|backend|service)[a-z0-9.-]*\\.target\\.com[a-z0-9\u002F_-]*' $B | sort -u\n# Versioned API base paths\ngrep -ohiE '\u002Fapi\u002Fv[0-9]+\u002F?' $B | sort -u\n# Route literals — minified bundles store routes as STRING segments, not full URLs.\n# Grep for quoted \"resource\u002Faction\" strings:\ngrep -ohiE '\"[a-z0-9_-]+\u002F[a-z0-9_\u002F-]+\"' $B | tr -d '\"' \\\n  | grep -iE '(login|user|account|order|billing|invoice|payment|deal|report|token|otp|password|reset|admin|profile|auth|upload|export|role|permission|dashboard|wallet|finance|sales)' | sort -u\n# Secrets (validate before trusting — most AIza keys are Maps\u002Fanalytics, not Auth)\ngrep -ohiE '(AIza[0-9A-Za-z_-]{35}|AKIA[0-9A-Z]{16}|sk_live_[0-9A-Za-z]+|eyJ[A-Za-z0-9_-]{10,}\\.[A-Za-z0-9_-]{10,}|apiKey[\"'\"'\"']?\\s*[:=]\\s*[\"'\"'\"'][^\"'\"'\"']+)' $B | sort -u\n```\n**Note:** minifiers store routes as concatenated string segments (e.g. `\"account\u002Fpayment\u002Flist\"`), NOT full `\u002Fapi\u002Fv2\u002F...` URLs — so a naive `\u002Fapi\u002Fv*` grep returns nothing. Grep for the **resource-word route strings** and prepend the base yourself.\n\n**Lazy-loaded (async) chunks — don't stop at HTML-referenced bundles.** CRA\u002Fwebpack SPAs reference only runtime+main+vendor in index.html; numbered async route chunks are named inside main.js's chunk map and loaded at runtime, so grepping only `\u002Fstatic\u002Fjs\u002F*.js` from the shell truncates route coverage to eager chunks.\n```bash\ngrep -oE '[0-9]+:\"[a-f0-9]+\"' bundles\u002F*main*.js        # {chunkId:\"hash\"} pairs\n# reconstruct \u002Fstatic\u002Fjs\u002F\u003Cid>.\u003Chash>.chunk.js, download each, re-run route\u002Fhost\u002Fsecret harvest\n# asset-manifest.json (if present) lists them all -> hunt-source-leak\n```\n\n### 3. Establish a CONTROL — find an endpoint that IS gated\nBefore declaring anything vulnerable, send an unauthenticated request to an endpoint you expect to be protected, and capture what *correct* rejection looks like:\n```bash\ncurl -s -X POST https:\u002F\u002Fapi.target.com\u002Fapi\u002Fusers -H 'Content-Type: application\u002Fjson' -d '{}'\n# secure → {\"error\":\"Missing or invalid authorization header\"} or HTTP 401\n```\nThis is your differential. A sibling API (e.g. a second API host, or a different route group on the same host) is the ideal control — same stack, so a different response = real authz gap, not a quirk.\n\n### 4. Test each route family UNAUTHENTICATED, both methods\nFor every discovered route, send it with **no `Authorization` header** and compare to the control:\n```bash\nfor r in \u003Croutes>; do\n  curl -s -o \u002Ftmp\u002Fr -w \"[%{http_code}] $r\\n\" -X POST -H 'Content-Type: application\u002Fjson' -d '{}' \"https:\u002F\u002Fapi.target.com\u002Fapi\u002Fv2\u002F$r\"\ndone\n```\nInterpret:\n- **`401`\u002F`\"Missing authorization\"`** → gated (correct). Move on.\n- **`200` with data** → unauthenticated data exposure. **Finding.**\n- **`400 \"field X is mandatory\"`** → the route processed your request and reached *business-logic validation* without an auth check → **auth bypass; supply the field minimally to confirm.**\n- **`200` + verbose DB\u002Fstack error** (e.g. `PROCEDURE db_x.sp_y does not exist`) → reached the data layer unauthenticated; also a SQLi-surface signal.\n- **Mandatory fields named like `is_admin` \u002F `is_internal` \u002F `requested_by` \u002F `role_id` \u002F `account_type`** → **authorization derived from client-supplied parameters** — set the privilege flag and you self-elevate. Critical-class.\n\n### 5. Pivot & prove (minimally)\n- IDs returned by one endpoint (`account_id`, `order_id`, `deal_id`) are the keys the *other* endpoints consume — they prove the whole router is reachable, not just one route.\n- Test `dev-`\u002F`beta-`\u002F`staging-` API variants — they frequently have weaker\u002Fdisabled auth.\n- Check the response headers: `Access-Control-Allow-Origin: *` compounds the issue (any web origin reads it from a victim's browser).\n- **STOP at minimum-necessary proof.** A handful of records (or a `totalCount`) confirms the missing check. Do NOT enumerate the table — see `redteam-mindset` data-minimization boundary. The finding is the absent auth, not the data volume.\n\n---\n\n## What \"the API behind the SSO login\" really means\n\nA common, dangerous architecture:\n- `console.target.com` (the SPA) → login is **Entra\u002FOkta\u002FGoogle OAuth** (looks airtight).\n- `api.target.com` (the backend) → some route groups enforce the bearer token, **some route groups forgot the middleware.**\n\nThe frontend login is theatre if the API doesn't independently validate the token on every route. Always test the API directly, bare, regardless of how locked-down the login UI is.\n\n---\n\n## Anti-patterns\n\n- **\"The app requires login, so the API must be protected.\"** No — test the API directly, unauthenticated. The whole point.\n- **\"Minified bundle, can't read it.\"** You don't need to read it — grep it for hosts\u002Froutes\u002Fsecrets. 5 minutes.\n- **\"`\u002Fapi\u002Fv1\u002Ffoo` returned 404, so no API here.\"** Wrong base or wrong method. Try `\u002Fapi\u002F`, `\u002Fapi\u002Fv2\u002F`, POST not GET, and the exact route strings from the bundle (Express's 404 echoes the path — use it to calibrate).\n- **\"AIza key found → critical secret.\"** Validate first — most are Maps\u002Fanalytics keys (`CONFIGURATION_NOT_FOUND` on identitytoolkit = not Auth-enabled). Don't over-claim.\n- **Dumping the whole dataset once you get a 200.** Stop at PoC. (`redteam-mindset`.)\n- **Account-creation \u002F write endpoints as \"proof\".** Read endpoints prove the auth gap without creating state. Never POST a `create`\u002F`signup`\u002F`upload` to \"demonstrate\" — that's a destructive write needing explicit per-action authorization.\n\n---\n\n## Related Skills & Chains\n\n- **`hunt-api-misconfig`** — once the API is mapped, run the broader misconfig matrix (method tampering, mass assignment, JWT alg confusion) per route.\n- **`hunt-idor`** — the `account_id`\u002F`order_id` pivots feed straight into IDOR testing across discovered routes.\n- **`hunt-source-leak`** — sourcemaps (`*.js.map`) reconstruct original source for deeper route\u002Fsecret extraction; same harvesting muscle.\n- **`hunt-nextjs`** — for Next.js targets, layer the middleware-bypass (`x-middleware-subrequest`) and `\u002F_next\u002Fdata` route tests on top of this.\n- **`redteam-mindset`** — the data-minimization boundary governs step 5: prove the missing check, don't exfiltrate the table.\n- **`recon-scope-triage`** — verify the API host actually belongs to the target before testing (don't pop a same-named third party's API).\n\n## Limitations\n\n- Authorized scope only: the confirmation gate above is mandatory before any probing, exploitation, or credential-access command.\n- Docs-only import: upstream helper scripts, commands, engine, and research assets are not bundled; reinstall tooling from the source repo when needed.\n- Validate every finding (see `triage-validation`) before reporting; report via `report-writing`. Prefer a sandbox, disposable VM, or controlled lab.\n\n### Example\n\n```bash\n# Read-only first step; confirm scope before anything active.\ncat scope.txt  # target list from the authorized engagement brief\n```\n\n> Adapted from [elementalsouls\u002FClaude-BugHunter](https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter) (MIT); frontmatter, When to Use\u002FLimitations, and safety boundaries added for upstream compliance. Docs-only import: executable helpers, commands, engine, and research assets not bundled.\n","> **⚠️ AUTHORIZED USE ONLY**\n> This skill is for educational purposes or authorized security assessments only.\n> You must have explicit, written permission from the system owner before using this tool.\n> Misuse of this tool is illegal and strictly prohibited.\n\n> **Mandatory confirmation gate**\n> Before running any command that probes, exploits, changes, persists on, extracts data from, or attempts credential access against a target:\n> 1. Ask the user to state the exact target URL, IP, account, or resource.\n> 2. Ask the user to confirm written authorization and the permitted scope.\n> 3. Show the exact command(s) and explain their expected effect.\n> 4. Wait for explicit confirmation in the current conversation.\n>\n> Without that confirmation, remain read-only and provide defensive guidance only. Prefer a sandbox, disposable VM, or controlled lab.\n\n## When to use this skill\n\nTrigger when:\n- A target host returns a tiny HTML shell + big `\u002Fstatic\u002Fjs\u002F*.js` or `\u002F_next\u002Fstatic\u002F*` bundles (React\u002FVue\u002FAngular\u002FNext\u002FSvelte SPA)\n- You see a subdomain named `console`, `app`, `dashboard`, `portal`, `admin`, `panel`, `manage`, `internal`\n- Recon surfaces any `*api*`, `*-api*`, `api.*` host\n- A login page is OAuth\u002FSSO-gated (the *frontend* auth tells you nothing about whether the *API* enforces auth)\n\nThe core insight: **a SPA is a client to a backend API, and it ships the full map of that API — hosts, routes, sometimes keys — to anyone who views source.** The login page being protected says nothing about whether the API behind it checks tokens. Auth is frequently enforced on the *gateway\u002Flogin* and missing on a *route group* of the API.\n\nDO NOT skip this because \"the app needs login\" — that's exactly when this pays off.\n\n---\n\n## The play (5 steps)\n\n### 1. Pull the shell + enumerate the bundles\n```bash\ncurl -s https:\u002F\u002Fconsole.target.com\u002F -o index.html\n# React\u002FCRA:\ngrep -oE '\u002Fstatic\u002Fjs\u002F[^\"]+\\.js' index.html\n# Next.js:\ngrep -oE '\u002F_next\u002Fstatic\u002F[^\"]+\\.js' index.html\n# generic:\ngrep -oiE 'src=\"[^\"]+\\.js[^\"]*\"' index.html\n```\nDownload every bundle (they can be multi-MB — that's fine, it's all route data):\n```bash\nmkdir bundles\nfor j in $(grep -oE '\u002Fstatic\u002Fjs\u002F[^\"]+\\.js' index.html | sort -u); do\n  curl -s \"https:\u002F\u002Fconsole.target.com$j\" -o \"bundles\u002F$(echo \"$j\"|tr '\u002F' '_')\"\ndone\n```\n\n### 2. Harvest API hosts, routes, and secrets from the bundles\n```bash\nB=bundles\u002F*.js\n# Backend API hosts (incl. dev\u002Fbeta\u002Fstaging variants — often weaker auth)\ngrep -ohiE 'https:\u002F\u002F[a-z0-9.-]*(api|console|backend|service)[a-z0-9.-]*\\.target\\.com[a-z0-9\u002F_-]*' $B | sort -u\n# Versioned API base paths\ngrep -ohiE '\u002Fapi\u002Fv[0-9]+\u002F?' $B | sort -u\n# Route literals — minified bundles store routes as STRING segments, not full URLs.\n# Grep for quoted \"resource\u002Faction\" strings:\ngrep -ohiE '\"[a-z0-9_-]+\u002F[a-z0-9_\u002F-]+\"' $B | tr -d '\"' \\\n  | grep -iE '(login|user|account|order|billing|invoice|payment|deal|report|token|otp|password|reset|admin|profile|auth|upload|export|role|permission|dashboard|wallet|finance|sales)' | sort -u\n# Secrets (validate before trusting — most AIza keys are Maps\u002Fanalytics, not Auth)\ngrep -ohiE '(AIza[0-9A-Za-z_-]{35}|AKIA[0-9A-Z]{16}|sk_live_[0-9A-Za-z]+|eyJ[A-Za-z0-9_-]{10,}\\.[A-Za-z0-9_-]{10,}|apiKey[\"'\"'\"']?\\s*[:=]\\s*[\"'\"'\"'][^\"'\"'\"']+)' $B | sort -u\n```\n**Note:** minifiers store routes as concatenated string segments (e.g. `\"account\u002Fpayment\u002Flist\"`), NOT full `\u002Fapi\u002Fv2\u002F...` URLs — so a naive `\u002Fapi\u002Fv*` grep returns nothing. Grep for the **resource-word route strings** and prepend the base yourself.\n\n**Lazy-loaded (async) chunks — don't stop at HTML-referenced bundles.** CRA\u002Fwebpack SPAs reference only runtime+main+vendor in index.html; numbered async route chunks are named inside main.js's chunk map and loaded at runtime, so grepping only `\u002Fstatic\u002Fjs\u002F*.js` from the shell truncates route coverage to eager chunks.\n```bash\ngrep -oE '[0-9]+:\"[a-f0-9]+\"' bundles\u002F*main*.js        # {chunkId:\"hash\"} pairs\n# reconstruct \u002Fstatic\u002Fjs\u002F\u003Cid>.\u003Chash>.chunk.js, download each, re-run route\u002Fhost\u002Fsecret harvest\n# asset-manifest.json (if present) lists them all -> hunt-source-leak\n```\n\n### 3. Establish a CONTROL — find an endpoint that IS gated\nBefore declaring anything vulnerable, send an unauthenticated request to an endpoint you expect to be protected, and capture what *correct* rejection looks like:\n```bash\ncurl -s -X POST https:\u002F\u002Fapi.target.com\u002Fapi\u002Fusers -H 'Content-Type: application\u002Fjson' -d '{}'\n# secure → {\"error\":\"Missing or invalid authorization header\"} or HTTP 401\n```\nThis is your differential. A sibling API (e.g. a second API host, or a different route group on the same host) is the ideal control — same stack, so a different response = real authz gap, not a quirk.\n\n### 4. Test each route family UNAUTHENTICATED, both methods\nFor every discovered route, send it with **no `Authorization` header** and compare to the control:\n```bash\nfor r in \u003Croutes>; do\n  curl -s -o \u002Ftmp\u002Fr -w \"[%{http_code}] $r\\n\" -X POST -H 'Content-Type: application\u002Fjson' -d '{}' \"https:\u002F\u002Fapi.target.com\u002Fapi\u002Fv2\u002F$r\"\ndone\n```\nInterpret:\n- **`401`\u002F`\"Missing authorization\"`** → gated (correct). Move on.\n- **`200` with data** → unauthenticated data exposure. **Finding.**\n- **`400 \"field X is mandatory\"`** → the route processed your request and reached *business-logic validation* without an auth check → **auth bypass; supply the field minimally to confirm.**\n- **`200` + verbose DB\u002Fstack error** (e.g. `PROCEDURE db_x.sp_y does not exist`) → reached the data layer unauthenticated; also a SQLi-surface signal.\n- **Mandatory fields named like `is_admin` \u002F `is_internal` \u002F `requested_by` \u002F `role_id` \u002F `account_type`** → **authorization derived from client-supplied parameters** — set the privilege flag and you self-elevate. Critical-class.\n\n### 5. Pivot & prove (minimally)\n- IDs returned by one endpoint (`account_id`, `order_id`, `deal_id`) are the keys the *other* endpoints consume — they prove the whole router is reachable, not just one route.\n- Test `dev-`\u002F`beta-`\u002F`staging-` API variants — they frequently have weaker\u002Fdisabled auth.\n- Check the response headers: `Access-Control-Allow-Origin: *` compounds the issue (any web origin reads it from a victim's browser).\n- **STOP at minimum-necessary proof.** A handful of records (or a `totalCount`) confirms the missing check. Do NOT enumerate the table — see `redteam-mindset` data-minimization boundary. The finding is the absent auth, not the data volume.\n\n---\n\n## What \"the API behind the SSO login\" really means\n\nA common, dangerous architecture:\n- `console.target.com` (the SPA) → login is **Entra\u002FOkta\u002FGoogle OAuth** (looks airtight).\n- `api.target.com` (the backend) → some route groups enforce the bearer token, **some route groups forgot the middleware.**\n\nThe frontend login is theatre if the API doesn't independently validate the token on every route. Always test the API directly, bare, regardless of how locked-down the login UI is.\n\n---\n\n## Anti-patterns\n\n- **\"The app requires login, so the API must be protected.\"** No — test the API directly, unauthenticated. The whole point.\n- **\"Minified bundle, can't read it.\"** You don't need to read it — grep it for hosts\u002Froutes\u002Fsecrets. 5 minutes.\n- **\"`\u002Fapi\u002Fv1\u002Ffoo` returned 404, so no API here.\"** Wrong base or wrong method. Try `\u002Fapi\u002F`, `\u002Fapi\u002Fv2\u002F`, POST not GET, and the exact route strings from the bundle (Express's 404 echoes the path — use it to calibrate).\n- **\"AIza key found → critical secret.\"** Validate first — most are Maps\u002Fanalytics keys (`CONFIGURATION_NOT_FOUND` on identitytoolkit = not Auth-enabled). Don't over-claim.\n- **Dumping the whole dataset once you get a 200.** Stop at PoC. (`redteam-mindset`.)\n- **Account-creation \u002F write endpoints as \"proof\".** Read endpoints prove the auth gap without creating state. Never POST a `create`\u002F`signup`\u002F`upload` to \"demonstrate\" — that's a destructive write needing explicit per-action authorization.\n\n---\n\n## Related Skills & Chains\n\n- **`hunt-api-misconfig`** — once the API is mapped, run the broader misconfig matrix (method tampering, mass assignment, JWT alg confusion) per route.\n- **`hunt-idor`** — the `account_id`\u002F`order_id` pivots feed straight into IDOR testing across discovered routes.\n- **`hunt-source-leak`** — sourcemaps (`*.js.map`) reconstruct original source for deeper route\u002Fsecret extraction; same harvesting muscle.\n- **`hunt-nextjs`** — for Next.js targets, layer the middleware-bypass (`x-middleware-subrequest`) and `\u002F_next\u002Fdata` route tests on top of this.\n- **`redteam-mindset`** — the data-minimization boundary governs step 5: prove the missing check, don't exfiltrate the table.\n- **`recon-scope-triage`** — verify the API host actually belongs to the target before testing (don't pop a same-named third party's API).\n\n## Limitations\n\n- Authorized scope only: the confirmation gate above is mandatory before any probing, exploitation, or credential-access command.\n- Docs-only import: upstream helper scripts, commands, engine, and research assets are not bundled; reinstall tooling from the source repo when needed.\n- Validate every finding (see `triage-validation`) before reporting; report via `report-writing`. Prefer a sandbox, disposable VM, or controlled lab.\n\n### Example\n\n```bash\n# Read-only first step; confirm scope before anything active.\ncat scope.txt  # target list from the authorized engagement brief\n```\n\n> Adapted from [elementalsouls\u002FClaude-BugHunter](https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter) (MIT); frontmatter, When to Use\u002FLimitations, and safety boundaries added for upstream compliance. Docs-only import: executable helpers, commands, engine, and research assets not bundled.\n",{"name":5,"risk":37,"source":56,"license":14,"sources":57,"category":50,"date_added":58,"description":7,"source_repo":59,"source_type":45,"report_count":60,"compatibility":61,"license_source":62},"https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter","authorized-engagement","2026-09-20","elementalsouls\u002FClaude-BugHunter",1,"Requires explicit written authorization for a target scope plus the relevant testing tools for this technique. Docs-only; helper scripts and commands not bundled.","https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter\u002Fblob\u002Fmain\u002FLICENSE","f3312ba749561b6159f477dbfc9313c875d40a56",".agents\u002Fskills_archive\u002Fhunt-spa-api","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612","2026-10-25 23:50:58",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill hunt-spa-api",{"tool":74,"command":75},"bunx","bunx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill hunt-spa-api",{"tool":77,"command":78},"pnpm","pnpm dlx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill hunt-spa-api","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fhunt-spa-api\u002FSKILL.md",true,[],[83,105,128,153,174,198],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":92,"publishedAt":51},"01M6Q0FA5FZ410Z33Z3TFQ4DBA","zero-trust","Implement zero-trust network architecture. Configure identity-based access, micro-segmentation, and continuous verification. Use when implementing modern security architectures.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fzero-trust\u002FSKILL.md",[89],{"categoryNo":90,"categoryName":91,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",[93,94,95,96,97,98,85,99,100,48,101,46,45,44,102,103,39,38,36,104],"ZeRO","trust","zero trust","architecture","assessment","verification","segmentation","devops-security","configure","active","critical","implementing",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":51},"01M6Q0F1YZJW3KX5FBKEVZ8CV4","zcode-delegate","Delegate coding tasks to the Z.AI ZCode CLI only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fzcode-delegate\u002FSKILL.md",[],[112,113,114,115,116,117,118,119,120,121,122,123,124,46,125,45,126,40,103,127],"delegate","zcode","zcode delegate","review","cli","orchestration","tasks","run","Bash","model","node","read","orchestrator","files","desktop app","agent-orchestration",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":51},"01M6Q0ETK41VGNMYEXW0T00AJN","youtube-transcript","Fetch YouTube transcripts through DeepAPI or local fallback tooling and save clean text output.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-transcript\u002FSKILL.md",[],[135,136,137,138,139,140,141,142,143,144,145,146,147,45,44,148,149,150,151,152],"transcript","youtube transcript","youtube","safe","github","codex","research","license","https","text","fetch","tooling","clean","local","output","deepapi","youtube transcripts","blob",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":164,"publishedAt":51},"01M6Q0EPPH2PVMDW40017F8WX0","youtube-transcript-skills","Fetch YouTube video transcripts, search videos\u002Fchannels, browse channels, and extract playlists via the getyoutubetranscript.com API - free tier, no card required.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-transcript-skills\u002FSKILL.md",[159,160,163],{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":161,"categoryName":162,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":26,"categoryName":27,"taxonomyType":28,"taxonomyTypeDesc":29},[135,136,137,165,138,166,139,140,142,167,32,168,169,145,170,45,44,171,172,173],"youtube transcript skills","gemini","search","Video","browse","api-integration","free","card","channels",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":184,"publishedAt":51},"01M6Q0EAB96PX83W5PTE8A0R8D","youtube-notetaker","Turn YouTube talks into local study notes with slides, transcripts, editable annotations, and a markdown-backed viewer.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-notetaker\u002FSKILL.md",[180,183],{"categoryNo":181,"categoryName":182,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":161,"categoryName":162,"taxonomyType":20,"taxonomyTypeDesc":21},[137,185,186,116,138,187,188,189,190,142,168,191,192,193,194,44,195,148,196,197],"youtube notetaker","notetaker","workflow","official","notes","code","markdown","slides","annotations","README","study","dair-academy","viewer",{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":202,"categories":203,"keywords":205,"publishedAt":51},"01M6Q0E55F0GW5MX48V8HXS8B5","youtube-full","Fetch YouTube transcripts, search videos, browse channels, and extract playlists via TranscriptAPI — no yt-dlp, no Google API key, works from any cloud server.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-full\u002FSKILL.md",[204],{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},[206,137,207,208,138,166,167,209,210,32,168,169,145,211,170,45,44,171,212,151],"youtube full","full","google","server","dlp","credits","automatic"]