[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6P62AZJ3D9J09XTZW2TC3A9":3,"skill-same:01M6P62AZJ3D9J09XTZW2TC3A9":76},{"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":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":32,"commitSha":57,"skillDirectory":58,"forksCount":13,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":61,"install":62,"resources":75},"01M6P62AZJ3D9J09XTZW2TC3A9","hunt-mfa-bypass",null,"Hunt MFA \u002F 2FA bypass","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-mfa-bypass\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"hunt mfa bypass","mfa","hunt","only","for","relevant","helper","scripts","scope","main","community","testing","NIST","cve","https","license","database","testing tools","research","github","2026-11-10 10:12:30",false,"---\nname: hunt-mfa-bypass\ndescription: Hunt MFA \u002F 2FA bypass\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: hackerone_public, cve_database, nist_800_63b, public_research\nreport_count: 5\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## Autonomous Testing Priority\n\n**Try workflow bypasses before brute force — they're faster and more likely to succeed.**\n\n**Pattern 1 — Skip the MFA step entirely (most automatable):**\n1. Login with valid credentials → receive a \"pre-MFA\" session state\n2. Without completing MFA, directly access a protected resource (`\u002Fdashboard`, `\u002Fapi\u002Fme`, `\u002Faccount\u002Fprofile`)\n3. If the response returns user data → MFA is enforced only in the UI, not server-side = Critical\n\n**Pattern 2 — OTP replay (reuse a consumed code):**\n1. Complete a valid MFA flow to get a working OTP\n2. Log out, log in again with the same credentials\n3. Submit the same OTP again\n4. If accepted → OTP is not invalidated after use\n\n**Pattern 3 — Submit obviously wrong OTP, observe response:**\nTry submitting `000000` or `123456`. If the response is 200 or returns a session token, OTP validation is broken or client-side only.\n\n**Pattern 4 — Partial \u002F incremental validation (prefix oracle):**\nIf a guessed full code is rejected, test whether the server validates the OTP **prefix-by-prefix** instead of all-or-nothing. Submit a short partial code and compare responses:\n1. Submit a 1–3 digit value (e.g. `otp=1`, then `otp=12`, …) — for a POST verify endpoint the code goes in the **request body**, not the URL query string, or the server reads an empty value.\n2. If a *correct* prefix gives a DIFFERENT response than a wrong one (a success\u002Fflag, a distinct message, or a different length\u002Ftiming), the validator leaks correctness one chunk at a time.\n3. Walk the code digit-by-digit: keep the prefix that \"responds correct,\" append 0–9, repeat. This collapses 10^6 brute force to ~10×N guesses (≤60 for a 6-digit code) — very feasible in a bounded test.\nThis is the go-to when there is no leaked code and no skip\u002Freplay path. Some apps award success on *any* correct prefix outright (so a single correct first digit can win — sweep `otp=0,1,…,9` before giving up).\n**CRITICAL — stay in ONE session:** re-authenticating (POST \u002F…\u002Flogin again) regenerates the OTP, throwing away your prefix progress. Do the entire sweep against a single established MFA session; never re-login between guesses.\n\n**On full brute force:** brute-forcing all 10^6 codes is infeasible in a bounded test — but the prefix oracle above (Pattern 4) usually makes it unnecessary. Only attempt full brute force with evidence of no rate limit AND a small key space.\n\n**Proof:** A session token or protected resource data in the response without completing MFA confirms the bypass.\n\n---\n\n## 19. MFA \u002F 2FA BYPASS\n> Growing bug class — 7 distinct patterns. Pays High\u002FCritical when it enables ATO without prior session.\n\n### Pattern 1: No Rate Limit on OTP\n```bash\n# Test with ffuf — all 1M 6-digit codes\nffuf -u \"https:\u002F\u002Ftarget.com\u002Fapi\u002Fverify-otp\" \\\n  -X POST -H \"Content-Type: application\u002Fjson\" \\\n  -H \"Cookie: session=YOUR_SESSION\" \\\n  -d '{\"otp\":\"FUZZ\"}' \\\n  -w \u003C(seq -w 000000 999999) \\\n  -fc 400,429 -t 5\n# -t 5 (slow down) — aggressive rates get 429 or ban\n```\n\n### Pattern 2: OTP Not Invalidated After Use\n```\n1. Login → receive OTP \"123456\" → enter it → success\n2. Logout → login again with same credentials\n3. Try OTP \"123456\" again\n4. If accepted → OTP never invalidated = ATO (attacker sniffs OTP once, reuses forever)\n```\n\n### Pattern 3: Response Manipulation\n```\n1. Enter wrong OTP → capture response in Burp\n2. Change {\"success\":false} → {\"success\":true} (or 401 → 200)\n3. Forward → if app proceeds → client-side only MFA check\n```\n\n### Pattern 4: Skip MFA Step (Workflow Bypass)\n```bash\n# After entering password, app sets a \"pre-mfa\" cookie → redirects to \u002Fmfa\n# Test: skip \u002Fmfa entirely, access \u002Fdashboard directly with pre-mfa cookie\n# If app grants access without MFA = auth flow bypass = Critical\ncurl -s -b \"session=PRE_MFA_SESSION\" https:\u002F\u002Ftarget.com\u002Fdashboard\n```\n\n### Pattern 5: Race on MFA Verification\n```python\nimport asyncio, aiohttp\n\nasync def verify(session, otp):\n    async with session.post(\"https:\u002F\u002Ftarget.com\u002Fapi\u002Fmfa\u002Fverify\",\n                            json={\"otp\": otp}) as r:\n        return r.status, await r.text()\n\nasync def race():\n    cookies = {\"session\": \"YOUR_SESSION\"}\n    async with aiohttp.ClientSession(cookies=cookies) as s:\n        # Fire ~30 concurrent submissions of the SAME OTP to hit the TOCTOU\n        # window before the server marks it used. Two requests are NOT enough —\n        # they almost always resolve sequentially as \"already-used\" (false negative).\n        # Best done as a single-packet \u002F 20+ HTTP-2-stream attack (Turbo Intruder).\n        results = await asyncio.gather(*[verify(s, \"123456\") for _ in range(30)])\n        # Race confirmed if >1 success (or 1 success among many \"already-used\").\n        for status, body in results:\n            print(status, body)\nasyncio.run(race())\n```\n\n### Pattern 6: Backup Code Brute Force\n```\nBackup codes: typically 8 alphanumeric = 36^8 = ~2.8T (too large)\nBUT: check if backup codes are only 6-8 digits = 1-10M range = feasible with no rate limit\nAlso test: can backup codes be reused after exhaustion? Some apps regenerate predictably.\n```\n\n### Pattern 7: \"Remember This Device\" Trust Escalation\n```\n1. Complete MFA once on Device A (attacker's browser)\n2. Capture the \"remember device\" cookie\n3. Present that cookie from a new IP\u002Fbrowser\n4. If MFA skipped = device trust not bound to IP\u002FUA = ATO from any location\n```\n\n### MFA Chain Escalation\n```\nRate limit bypass + no lockout = ATO (Critical)\nResponse manipulation = client-side only check = Critical\nSkip MFA step = auth flow bypass = Critical\nOTP reuse = persistent session hijack = High\n```\n\n---\n\n## Related Skills & Chains\n\n- **`hunt-ato`** — MFA bypass is a primitive; ATO is the destination. Chain primitive: cookie theft (via XSS or session-fixation) + password oracle (login response timing\u002Flength diff reveals valid passwords without lockout) + no MFA step-up on password-change endpoint = persistent ATO without ever facing the OTP challenge → password rotated, attacker locks victim out.\n- **`hunt-race-condition`** — Pattern 5 (OTP race) lives in race-condition territory; load both skills together. Chain primitive: same 6-digit OTP submitted via 20 parallel HTTP\u002F2 streams (single-packet Turbo Intruder attack) before the server marks it used → 1 success + 19 \"already-used\" → race window confirmed → attacker doesn't need to brute, just guesses once and parallelizes → ATO.\n- **`hunt-auth-bypass`** — MFA-step-skip is auth-flow bypass at the workflow layer. Chain primitive: pre-MFA cookie issued after password step + direct navigation to `\u002Fdashboard` skipping `\u002Fmfa` route + server only middleware-gates `\u002Fmfa` not `\u002Fdashboard` = full post-auth access from password-only state → MFA never enforced because the route gate was misplaced.\n- **`hunt-misc`** — Recovery-code dump via `\u002Fapi\u002Fme` is a misc-class info disclosure that becomes Critical when chained. Chain primitive: `\u002Fapi\u002Fme` returns full user object including `backup_codes` array (plaintext, never rotated) → attacker with any read-IDOR or XSS exfils backup codes → uses one backup code → MFA satisfied → ATO without OTP knowledge.\n- **`security-arsenal`** — Pull the OTP-brute-force payload section (000000-999999 wordlist generator, ffuf rate-limit-evasion patterns with `-t 5 -p 0.5-2`, distributed-IP rotation via proxychains) and the JWT-token-replay table when \"MFA satisfied\" claim lives in a JWT claim that can be forged.\n- **`triage-validation`** — Run the Pre-Severity Gate before claiming Critical on an MFA bypass that only works when the attacker already has the password. Standalone MFA bypass is High; chained-with-password-oracle is Critical; chained-with-cookie-theft-only is Critical. The chain question separates the two.\n\n## When to Use\n\n- You have explicit, written authorization to assess the target in scope, and the task matches this skill's vulnerability class or technique within a bug-bounty or penetration-test engagement.\n- You need the recon, exploitation, or validation workflow described below — executed strictly inside the approved scope.\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## Autonomous Testing Priority\n\n**Try workflow bypasses before brute force — they're faster and more likely to succeed.**\n\n**Pattern 1 — Skip the MFA step entirely (most automatable):**\n1. Login with valid credentials → receive a \"pre-MFA\" session state\n2. Without completing MFA, directly access a protected resource (`\u002Fdashboard`, `\u002Fapi\u002Fme`, `\u002Faccount\u002Fprofile`)\n3. If the response returns user data → MFA is enforced only in the UI, not server-side = Critical\n\n**Pattern 2 — OTP replay (reuse a consumed code):**\n1. Complete a valid MFA flow to get a working OTP\n2. Log out, log in again with the same credentials\n3. Submit the same OTP again\n4. If accepted → OTP is not invalidated after use\n\n**Pattern 3 — Submit obviously wrong OTP, observe response:**\nTry submitting `000000` or `123456`. If the response is 200 or returns a session token, OTP validation is broken or client-side only.\n\n**Pattern 4 — Partial \u002F incremental validation (prefix oracle):**\nIf a guessed full code is rejected, test whether the server validates the OTP **prefix-by-prefix** instead of all-or-nothing. Submit a short partial code and compare responses:\n1. Submit a 1–3 digit value (e.g. `otp=1`, then `otp=12`, …) — for a POST verify endpoint the code goes in the **request body**, not the URL query string, or the server reads an empty value.\n2. If a *correct* prefix gives a DIFFERENT response than a wrong one (a success\u002Fflag, a distinct message, or a different length\u002Ftiming), the validator leaks correctness one chunk at a time.\n3. Walk the code digit-by-digit: keep the prefix that \"responds correct,\" append 0–9, repeat. This collapses 10^6 brute force to ~10×N guesses (≤60 for a 6-digit code) — very feasible in a bounded test.\nThis is the go-to when there is no leaked code and no skip\u002Freplay path. Some apps award success on *any* correct prefix outright (so a single correct first digit can win — sweep `otp=0,1,…,9` before giving up).\n**CRITICAL — stay in ONE session:** re-authenticating (POST \u002F…\u002Flogin again) regenerates the OTP, throwing away your prefix progress. Do the entire sweep against a single established MFA session; never re-login between guesses.\n\n**On full brute force:** brute-forcing all 10^6 codes is infeasible in a bounded test — but the prefix oracle above (Pattern 4) usually makes it unnecessary. Only attempt full brute force with evidence of no rate limit AND a small key space.\n\n**Proof:** A session token or protected resource data in the response without completing MFA confirms the bypass.\n\n---\n\n## 19. MFA \u002F 2FA BYPASS\n> Growing bug class — 7 distinct patterns. Pays High\u002FCritical when it enables ATO without prior session.\n\n### Pattern 1: No Rate Limit on OTP\n```bash\n# Test with ffuf — all 1M 6-digit codes\nffuf -u \"https:\u002F\u002Ftarget.com\u002Fapi\u002Fverify-otp\" \\\n  -X POST -H \"Content-Type: application\u002Fjson\" \\\n  -H \"Cookie: session=YOUR_SESSION\" \\\n  -d '{\"otp\":\"FUZZ\"}' \\\n  -w \u003C(seq -w 000000 999999) \\\n  -fc 400,429 -t 5\n# -t 5 (slow down) — aggressive rates get 429 or ban\n```\n\n### Pattern 2: OTP Not Invalidated After Use\n```\n1. Login → receive OTP \"123456\" → enter it → success\n2. Logout → login again with same credentials\n3. Try OTP \"123456\" again\n4. If accepted → OTP never invalidated = ATO (attacker sniffs OTP once, reuses forever)\n```\n\n### Pattern 3: Response Manipulation\n```\n1. Enter wrong OTP → capture response in Burp\n2. Change {\"success\":false} → {\"success\":true} (or 401 → 200)\n3. Forward → if app proceeds → client-side only MFA check\n```\n\n### Pattern 4: Skip MFA Step (Workflow Bypass)\n```bash\n# After entering password, app sets a \"pre-mfa\" cookie → redirects to \u002Fmfa\n# Test: skip \u002Fmfa entirely, access \u002Fdashboard directly with pre-mfa cookie\n# If app grants access without MFA = auth flow bypass = Critical\ncurl -s -b \"session=PRE_MFA_SESSION\" https:\u002F\u002Ftarget.com\u002Fdashboard\n```\n\n### Pattern 5: Race on MFA Verification\n```python\nimport asyncio, aiohttp\n\nasync def verify(session, otp):\n    async with session.post(\"https:\u002F\u002Ftarget.com\u002Fapi\u002Fmfa\u002Fverify\",\n                            json={\"otp\": otp}) as r:\n        return r.status, await r.text()\n\nasync def race():\n    cookies = {\"session\": \"YOUR_SESSION\"}\n    async with aiohttp.ClientSession(cookies=cookies) as s:\n        # Fire ~30 concurrent submissions of the SAME OTP to hit the TOCTOU\n        # window before the server marks it used. Two requests are NOT enough —\n        # they almost always resolve sequentially as \"already-used\" (false negative).\n        # Best done as a single-packet \u002F 20+ HTTP-2-stream attack (Turbo Intruder).\n        results = await asyncio.gather(*[verify(s, \"123456\") for _ in range(30)])\n        # Race confirmed if >1 success (or 1 success among many \"already-used\").\n        for status, body in results:\n            print(status, body)\nasyncio.run(race())\n```\n\n### Pattern 6: Backup Code Brute Force\n```\nBackup codes: typically 8 alphanumeric = 36^8 = ~2.8T (too large)\nBUT: check if backup codes are only 6-8 digits = 1-10M range = feasible with no rate limit\nAlso test: can backup codes be reused after exhaustion? Some apps regenerate predictably.\n```\n\n### Pattern 7: \"Remember This Device\" Trust Escalation\n```\n1. Complete MFA once on Device A (attacker's browser)\n2. Capture the \"remember device\" cookie\n3. Present that cookie from a new IP\u002Fbrowser\n4. If MFA skipped = device trust not bound to IP\u002FUA = ATO from any location\n```\n\n### MFA Chain Escalation\n```\nRate limit bypass + no lockout = ATO (Critical)\nResponse manipulation = client-side only check = Critical\nSkip MFA step = auth flow bypass = Critical\nOTP reuse = persistent session hijack = High\n```\n\n---\n\n## Related Skills & Chains\n\n- **`hunt-ato`** — MFA bypass is a primitive; ATO is the destination. Chain primitive: cookie theft (via XSS or session-fixation) + password oracle (login response timing\u002Flength diff reveals valid passwords without lockout) + no MFA step-up on password-change endpoint = persistent ATO without ever facing the OTP challenge → password rotated, attacker locks victim out.\n- **`hunt-race-condition`** — Pattern 5 (OTP race) lives in race-condition territory; load both skills together. Chain primitive: same 6-digit OTP submitted via 20 parallel HTTP\u002F2 streams (single-packet Turbo Intruder attack) before the server marks it used → 1 success + 19 \"already-used\" → race window confirmed → attacker doesn't need to brute, just guesses once and parallelizes → ATO.\n- **`hunt-auth-bypass`** — MFA-step-skip is auth-flow bypass at the workflow layer. Chain primitive: pre-MFA cookie issued after password step + direct navigation to `\u002Fdashboard` skipping `\u002Fmfa` route + server only middleware-gates `\u002Fmfa` not `\u002Fdashboard` = full post-auth access from password-only state → MFA never enforced because the route gate was misplaced.\n- **`hunt-misc`** — Recovery-code dump via `\u002Fapi\u002Fme` is a misc-class info disclosure that becomes Critical when chained. Chain primitive: `\u002Fapi\u002Fme` returns full user object including `backup_codes` array (plaintext, never rotated) → attacker with any read-IDOR or XSS exfils backup codes → uses one backup code → MFA satisfied → ATO without OTP knowledge.\n- **`security-arsenal`** — Pull the OTP-brute-force payload section (000000-999999 wordlist generator, ffuf rate-limit-evasion patterns with `-t 5 -p 0.5-2`, distributed-IP rotation via proxychains) and the JWT-token-replay table when \"MFA satisfied\" claim lives in a JWT claim that can be forged.\n- **`triage-validation`** — Run the Pre-Severity Gate before claiming Critical on an MFA bypass that only works when the attacker already has the password. Standalone MFA bypass is High; chained-with-password-oracle is Critical; chained-with-cookie-theft-only is Critical. The chain question separates the two.\n\n## When to Use\n\n- You have explicit, written authorization to assess the target in scope, and the task matches this skill's vulnerability class or technique within a bug-bounty or penetration-test engagement.\n- You need the recon, exploitation, or validation workflow described below — executed strictly inside the approved scope.\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":48,"source":49,"license":14,"sources":50,"category":51,"date_added":52,"description":7,"source_repo":53,"source_type":33,"report_count":54,"compatibility":55,"license_source":56},"offensive","https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter","hackerone_public, cve_database, nist_800_63b, public_research","security","2026-09-20","elementalsouls\u002FClaude-BugHunter",5,"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-mfa-bypass","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":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill hunt-mfa-bypass",{"tool":68,"command":69},"bunx","bunx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill hunt-mfa-bypass",{"tool":71,"command":72},"pnpm","pnpm dlx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill hunt-mfa-bypass","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fhunt-mfa-bypass\u002FSKILL.md",true,[],[77,100,124,145,173,197],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":86,"publishedAt":43},"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",[83],{"categoryNo":84,"categoryName":85,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",[87,88,89,90,91,92,79,93,94,95,96,26,33,32,97,98,31,30,28,99],"ZeRO","trust","zero trust","architecture","assessment","verification","segmentation","devops-security","access","configure","active","critical","implementing",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":43},"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",[],[107,108,109,110,111,112,113,114,115,116,117,118,119,26,120,33,121,122,98,123],"delegate","zcode","zcode delegate","review","cli","orchestration","tasks","run","Bash","model","node","read","orchestrator","files","desktop app","app","agent-orchestration",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":43},"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",[],[131,132,133,134,42,135,41,38,37,136,137,138,139,33,32,140,141,142,143,144],"transcript","youtube transcript","youtube","safe","codex","text","fetch","tooling","clean","local","output","deepapi","youtube transcripts","blob",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":162,"publishedAt":43},"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",[151,154,157],{"categoryNo":152,"categoryName":153,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":155,"categoryName":156,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":158,"categoryName":159,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[131,132,133,163,134,164,42,135,38,165,166,167,168,137,169,33,32,170,171,172],"youtube transcript skills","gemini","search","api","Video","browse","api-integration","free","card","channels",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":183,"publishedAt":43},"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",[179,182],{"categoryNo":180,"categoryName":181,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":155,"categoryName":156,"taxonomyType":20,"taxonomyTypeDesc":21},[133,184,185,111,134,186,187,188,189,38,167,190,191,192,193,32,194,140,195,196],"youtube notetaker","notetaker","workflow","official","notes","code","markdown","slides","annotations","README","study","dair-academy","viewer",{"skillNo":198,"name":199,"nameZh":6,"description":200,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":201,"categories":202,"keywords":204,"publishedAt":43},"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",[203],{"categoryNo":152,"categoryName":153,"taxonomyType":20,"taxonomyTypeDesc":21},[205,133,206,207,134,164,165,208,209,166,167,168,137,210,169,33,32,170,211,143],"youtube full","full","google","server","dlp","credits","automatic"]