[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AAGPEW4SYAQDX9E3FAYF6Z":3,"skill-same:01M7AAGPEW4SYAQDX9E3FAYF6Z":99},{"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":44,"commitSha":45,"skillDirectory":46,"forksCount":14,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M7AAGPEW4SYAQDX9E3FAYF6Z","performing-web-application-scanning-with-nikto",null,"Runs Nikto, an open-source web server and web application scanner, to test over 7,000 potentially dangerous files\u002Fprograms, check for outdated versions across 1,250+ servers, and identify XSS, SQL injection, misconfigurations, default credentials, and vulnerable CGI scripts. Use when performing web application vulnerability scanning, security assessments, scheduled security testing, or validating web server security controls.","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\u002Fperforming-web-application-scanning-with-nikto\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-web-application-scanning-with-nikto\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: performing-web-application-scanning-with-nikto\ndescription: Runs Nikto, an open-source web server and web application scanner,\n  to test over 7,000 potentially dangerous files\u002Fprograms, check for outdated versions\n  across 1,250+ servers, and identify XSS, SQL injection, misconfigurations, default\n  credentials, and vulnerable CGI scripts. Use when performing web application vulnerability\n  scanning, security assessments, scheduled security testing, or validating web\n  server security controls.\ndomain: cybersecurity\nsubdomain: vulnerability-management\ntags:\n- vulnerability-management\n- cve\n- nikto\n- web-scanning\n- owasp\n- risk\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- ID.RA-01\n- ID.RA-02\n- ID.IM-02\n- ID.RA-06\nmitre_attack:\n- T1190\n- T1203\n- T1068\n---\n# Performing Web Application Scanning with Nikto\n\n## Overview\nNikto is an open-source web server and web application scanner that tests against over 7,000 potentially dangerous files\u002Fprograms, checks for outdated versions of over 1,250 servers, and identifies version-specific problems on over 270 servers. It performs comprehensive tests including XSS, SQL injection, server misconfigurations, default credentials, and known vulnerable CGI scripts.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing web application scanning with nikto\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n- Nikto installed (Perl-based, included in Kali Linux)\n- Written authorization to scan target web servers\n- Network access to target web applications\n- Understanding of HTTP\u002FHTTPS protocols\n\n## Core Concepts\n\n### What Nikto Detects\n- Server misconfigurations and dangerous default files\n- Outdated server software versions with known CVEs\n- Common CGI vulnerabilities and dangerous scripts\n- Default credentials and admin pages\n- HTTP methods that should be disabled (PUT, DELETE, TRACE)\n- SSL\u002FTLS misconfigurations and weak ciphers\n- Missing security headers (X-Frame-Options, CSP, HSTS)\n- Information disclosure through headers and error pages\n\n### Nikto vs Other Web Scanners\n| Feature | Nikto | OWASP ZAP | Burp Suite | Nuclei |\n|---------|-------|-----------|------------|--------|\n| License | Open Source | Open Source | Commercial | Open Source |\n| Focus | Server\u002FConfig | App Logic | Full Pentest | Template-Based |\n| Speed | Fast | Medium | Slow | Very Fast |\n| False Positives | Moderate | Low | Low | Low |\n| Authentication | Basic | Full | Full | Template |\n| Active Community | Yes | Yes | Yes | Yes |\n\n## Workflow\n\n### Step 1: Basic Scanning\n```bash\n# Basic scan against a target\nnikto -h https:\u002F\u002Ftarget.example.com\n\n# Scan specific port\nnikto -h target.example.com -p 8443\n\n# Scan multiple ports\nnikto -h target.example.com -p 80,443,8080,8443\n\n# Scan with SSL enforcement\nnikto -h target.example.com -ssl\n\n# Scan from a host list file\nnikto -h targets.txt\n```\n\n### Step 2: Advanced Scanning Options\n```bash\n# Comprehensive scan with all tuning options\nnikto -h https:\u002F\u002Ftarget.example.com \\\n  -Tuning 123456789abcde \\\n  -timeout 10 \\\n  -Pause 2 \\\n  -Display V \\\n  -output report.html \\\n  -Format htm\n\n# Tuning options control test types:\n# 0 - File Upload\n# 1 - Interesting File \u002F Seen in logs\n# 2 - Misconfiguration \u002F Default File\n# 3 - Information Disclosure\n# 4 - Injection (XSS\u002FScript\u002FHTML)\n# 5 - Remote File Retrieval - Inside Web Root\n# 6 - Denial of Service\n# 7 - Remote File Retrieval - Server Wide\n# 8 - Command Execution \u002F Remote Shell\n# 9 - SQL Injection\n# a - Authentication Bypass\n# b - Software Identification\n# c - Remote Source Inclusion\n# d - WebService\n# e - Administrative Console\n\n# Scan with specific tuning (XSS + SQL injection + auth bypass)\nnikto -h https:\u002F\u002Ftarget.example.com -Tuning 49a\n\n# Scan with authentication\nnikto -h https:\u002F\u002Ftarget.example.com -id admin:password\n\n# Scan through a proxy\nnikto -h https:\u002F\u002Ftarget.example.com -useproxy http:\u002F\u002Fproxy:8080\n\n# Scan with custom User-Agent\nnikto -h https:\u002F\u002Ftarget.example.com -useragent \"Mozilla\u002F5.0 (Security Scan)\"\n\n# Scan specific CGI directories\nnikto -h https:\u002F\u002Ftarget.example.com -Cgidirs \u002Fcgi-bin\u002F,\u002Fscripts\u002F\n\n# Evasion techniques (IDS avoidance for authorized testing)\n# 1-Random URI encoding, 2-Directory self-reference\n# 3-Premature URL ending, 4-Prepend long random string\nnikto -h https:\u002F\u002Ftarget.example.com -evasion 1234\n```\n\n### Step 3: Output and Reporting\n```bash\n# Generate multiple output formats\nnikto -h https:\u002F\u002Ftarget.example.com -output scan.csv -Format csv\nnikto -h https:\u002F\u002Ftarget.example.com -output scan.xml -Format xml\nnikto -h https:\u002F\u002Ftarget.example.com -output scan.html -Format htm\nnikto -h https:\u002F\u002Ftarget.example.com -output scan.txt -Format txt\n\n# JSON output (newer versions)\nnikto -h https:\u002F\u002Ftarget.example.com -output scan.json -Format json\n\n# Save to multiple formats simultaneously\nnikto -h https:\u002F\u002Ftarget.example.com \\\n  -output scan_report \\\n  -Format htm\n```\n\n### Step 4: Scan Multiple Targets\n```bash\n# Create targets file (one per line)\ncat > targets.txt \u003C\u003C 'EOF'\nhttps:\u002F\u002Fapp1.example.com\nhttps:\u002F\u002Fapp2.example.com:8443\nhttp:\u002F\u002Finternal-app.corp.local\n192.168.1.100:8080\nEOF\n\n# Scan all targets\nnikto -h targets.txt -output multi_scan.html -Format htm\n\n# Parallel scanning with GNU parallel\ncat targets.txt | parallel -j 5 \"nikto -h {} -output {\u002F}_report.html -Format htm\"\n```\n\n### Step 5: SSL\u002FTLS Assessment\n```bash\n# Comprehensive SSL scan\nnikto -h https:\u002F\u002Ftarget.example.com -ssl \\\n  -Tuning b \\\n  -Display V\n\n# Check for specific SSL vulnerabilities\n# Nikto checks for:\n# - Expired certificates\n# - Self-signed certificates\n# - Weak cipher suites\n# - SSLv2\u002FSSLv3 enabled\n# - BEAST, POODLE, Heartbleed indicators\n# - Missing HSTS header\n```\n\n### Step 6: Integration with Other Tools\n```bash\n# Pipe Nmap results into Nikto\nnmap -p 80,443,8080 --open -oG - 192.168.1.0\u002F24 | \\\n  awk '\u002Fopen\u002F{print $2}' | \\\n  while read host; do nikto -h \"$host\" -output \"${host}_nikto.html\" -Format htm; done\n\n# Export to Metasploit-compatible format\nnikto -h target.example.com -output msf_import.xml -Format xml\n\n# Parse Nikto XML output with Python for custom reporting\npython3 -c \"\nimport xml.etree.ElementTree as ET\ntree = ET.parse('scan.xml')\nfor item in tree.findall('.\u002F\u002Fitem'):\n    print(f\\\"[{item.get('id')}] {item.findtext('description', '')[:100]}\\\")\n\"\n```\n\n## Interpreting Results\n\n### Severity Classification\n- **OSVDB\u002FCVE References**: Cross-reference with NVD for CVSS scores\n- **Server Information Disclosure**: Version banners, technology stack\n- **Dangerous HTTP Methods**: PUT, DELETE, TRACE enabled\n- **Default\u002FBackup Files**: .bak, .old, .swp, web.config.bak\n- **Admin Interfaces**: \u002Fadmin, \u002Fmanager, \u002Fconsole exposed\n- **Missing Security Headers**: CSP, X-Frame-Options, HSTS\n\n### Common False Positives\n- Generic checks triggered by custom 404 pages\n- Anti-CSRF tokens flagged as form vulnerabilities\n- CDN\u002FWAF responses misidentified as vulnerable\n- Load balancer health check pages\n\n## Best Practices\n1. Always obtain written authorization before scanning\n2. Run Nikto in conjunction with application-level scanners (ZAP, Burp)\n3. Use -Pause flag to reduce load on production servers\n4. Validate findings manually before reporting\n5. Combine with SSL testing tools (testssl.sh, sslyze) for comprehensive coverage\n6. Schedule regular scans as part of continuous vulnerability management\n7. Keep Nikto database updated for latest vulnerability checks\n8. Use appropriate evasion settings only for authorized IDS testing\n\n## Common Pitfalls\n- Running Nikto without authorization (legal liability)\n- Treating Nikto as a complete web application scanner (it focuses on server\u002Fconfig issues)\n- Not validating results leading to false positive reports\n- Scanning too aggressively against production systems\n- Ignoring SSL\u002FTLS findings as \"informational\"\n\n## Related Skills\n- scanning-infrastructure-with-nessus\n- scanning-apis-for-security-vulnerabilities\n- performing-network-vulnerability-assessment\n","# Performing Web Application Scanning with Nikto\n\n## Overview\nNikto is an open-source web server and web application scanner that tests against over 7,000 potentially dangerous files\u002Fprograms, checks for outdated versions of over 1,250 servers, and identifies version-specific problems on over 270 servers. It performs comprehensive tests including XSS, SQL injection, server misconfigurations, default credentials, and known vulnerable CGI scripts.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing web application scanning with nikto\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n- Nikto installed (Perl-based, included in Kali Linux)\n- Written authorization to scan target web servers\n- Network access to target web applications\n- Understanding of HTTP\u002FHTTPS protocols\n\n## Core Concepts\n\n### What Nikto Detects\n- Server misconfigurations and dangerous default files\n- Outdated server software versions with known CVEs\n- Common CGI vulnerabilities and dangerous scripts\n- Default credentials and admin pages\n- HTTP methods that should be disabled (PUT, DELETE, TRACE)\n- SSL\u002FTLS misconfigurations and weak ciphers\n- Missing security headers (X-Frame-Options, CSP, HSTS)\n- Information disclosure through headers and error pages\n\n### Nikto vs Other Web Scanners\n| Feature | Nikto | OWASP ZAP | Burp Suite | Nuclei |\n|---------|-------|-----------|------------|--------|\n| License | Open Source | Open Source | Commercial | Open Source |\n| Focus | Server\u002FConfig | App Logic | Full Pentest | Template-Based |\n| Speed | Fast | Medium | Slow | Very Fast |\n| False Positives | Moderate | Low | Low | Low |\n| Authentication | Basic | Full | Full | Template |\n| Active Community | Yes | Yes | Yes | Yes |\n\n## Workflow\n\n### Step 1: Basic Scanning\n```bash\n# Basic scan against a target\nnikto -h https:\u002F\u002Ftarget.example.com\n\n# Scan specific port\nnikto -h target.example.com -p 8443\n\n# Scan multiple ports\nnikto -h target.example.com -p 80,443,8080,8443\n\n# Scan with SSL enforcement\nnikto -h target.example.com -ssl\n\n# Scan from a host list file\nnikto -h targets.txt\n```\n\n### Step 2: Advanced Scanning Options\n```bash\n# Comprehensive scan with all tuning options\nnikto -h https:\u002F\u002Ftarget.example.com \\\n  -Tuning 123456789abcde \\\n  -timeout 10 \\\n  -Pause 2 \\\n  -Display V \\\n  -output report.html \\\n  -Format htm\n\n# Tuning options control test types:\n# 0 - File Upload\n# 1 - Interesting File \u002F Seen in logs\n# 2 - Misconfiguration \u002F Default File\n# 3 - Information Disclosure\n# 4 - Injection (XSS\u002FScript\u002FHTML)\n# 5 - Remote File Retrieval - Inside Web Root\n# 6 - Denial of Service\n# 7 - Remote File Retrieval - Server Wide\n# 8 - Command Execution \u002F Remote Shell\n# 9 - SQL Injection\n# a - Authentication Bypass\n# b - Software Identification\n# c - Remote Source Inclusion\n# d - WebService\n# e - Administrative Console\n\n# Scan with specific tuning (XSS + SQL injection + auth bypass)\nnikto -h https:\u002F\u002Ftarget.example.com -Tuning 49a\n\n# Scan with authentication\nnikto -h https:\u002F\u002Ftarget.example.com -id admin:password\n\n# Scan through a proxy\nnikto -h https:\u002F\u002Ftarget.example.com -useproxy http:\u002F\u002Fproxy:8080\n\n# Scan with custom User-Agent\nnikto -h https:\u002F\u002Ftarget.example.com -useragent \"Mozilla\u002F5.0 (Security Scan)\"\n\n# Scan specific CGI directories\nnikto -h https:\u002F\u002Ftarget.example.com -Cgidirs \u002Fcgi-bin\u002F,\u002Fscripts\u002F\n\n# Evasion techniques (IDS avoidance for authorized testing)\n# 1-Random URI encoding, 2-Directory self-reference\n# 3-Premature URL ending, 4-Prepend long random string\nnikto -h https:\u002F\u002Ftarget.example.com -evasion 1234\n```\n\n### Step 3: Output and Reporting\n```bash\n# Generate multiple output formats\nnikto -h https:\u002F\u002Ftarget.example.com -output scan.csv -Format csv\nnikto -h https:\u002F\u002Ftarget.example.com -output scan.xml -Format xml\nnikto -h https:\u002F\u002Ftarget.example.com -output scan.html -Format htm\nnikto -h https:\u002F\u002Ftarget.example.com -output scan.txt -Format txt\n\n# JSON output (newer versions)\nnikto -h https:\u002F\u002Ftarget.example.com -output scan.json -Format json\n\n# Save to multiple formats simultaneously\nnikto -h https:\u002F\u002Ftarget.example.com \\\n  -output scan_report \\\n  -Format htm\n```\n\n### Step 4: Scan Multiple Targets\n```bash\n# Create targets file (one per line)\ncat > targets.txt \u003C\u003C 'EOF'\nhttps:\u002F\u002Fapp1.example.com\nhttps:\u002F\u002Fapp2.example.com:8443\nhttp:\u002F\u002Finternal-app.corp.local\n192.168.1.100:8080\nEOF\n\n# Scan all targets\nnikto -h targets.txt -output multi_scan.html -Format htm\n\n# Parallel scanning with GNU parallel\ncat targets.txt | parallel -j 5 \"nikto -h {} -output {\u002F}_report.html -Format htm\"\n```\n\n### Step 5: SSL\u002FTLS Assessment\n```bash\n# Comprehensive SSL scan\nnikto -h https:\u002F\u002Ftarget.example.com -ssl \\\n  -Tuning b \\\n  -Display V\n\n# Check for specific SSL vulnerabilities\n# Nikto checks for:\n# - Expired certificates\n# - Self-signed certificates\n# - Weak cipher suites\n# - SSLv2\u002FSSLv3 enabled\n# - BEAST, POODLE, Heartbleed indicators\n# - Missing HSTS header\n```\n\n### Step 6: Integration with Other Tools\n```bash\n# Pipe Nmap results into Nikto\nnmap -p 80,443,8080 --open -oG - 192.168.1.0\u002F24 | \\\n  awk '\u002Fopen\u002F{print $2}' | \\\n  while read host; do nikto -h \"$host\" -output \"${host}_nikto.html\" -Format htm; done\n\n# Export to Metasploit-compatible format\nnikto -h target.example.com -output msf_import.xml -Format xml\n\n# Parse Nikto XML output with Python for custom reporting\npython3 -c \"\nimport xml.etree.ElementTree as ET\ntree = ET.parse('scan.xml')\nfor item in tree.findall('.\u002F\u002Fitem'):\n    print(f\\\"[{item.get('id')}] {item.findtext('description', '')[:100]}\\\")\n\"\n```\n\n## Interpreting Results\n\n### Severity Classification\n- **OSVDB\u002FCVE References**: Cross-reference with NVD for CVSS scores\n- **Server Information Disclosure**: Version banners, technology stack\n- **Dangerous HTTP Methods**: PUT, DELETE, TRACE enabled\n- **Default\u002FBackup Files**: .bak, .old, .swp, web.config.bak\n- **Admin Interfaces**: \u002Fadmin, \u002Fmanager, \u002Fconsole exposed\n- **Missing Security Headers**: CSP, X-Frame-Options, HSTS\n\n### Common False Positives\n- Generic checks triggered by custom 404 pages\n- Anti-CSRF tokens flagged as form vulnerabilities\n- CDN\u002FWAF responses misidentified as vulnerable\n- Load balancer health check pages\n\n## Best Practices\n1. Always obtain written authorization before scanning\n2. Run Nikto in conjunction with application-level scanners (ZAP, Burp)\n3. Use -Pause flag to reduce load on production servers\n4. Validate findings manually before reporting\n5. Combine with SSL testing tools (testssl.sh, sslyze) for comprehensive coverage\n6. Schedule regular scans as part of continuous vulnerability management\n7. Keep Nikto database updated for latest vulnerability checks\n8. Use appropriate evasion settings only for authorized IDS testing\n\n## Common Pitfalls\n- Running Nikto without authorization (legal liability)\n- Treating Nikto as a complete web application scanner (it focuses on server\u002Fconfig issues)\n- Not validating results leading to false positive reports\n- Scanning too aggressively against production systems\n- Ignoring SSL\u002FTLS findings as \"informational\"\n\n## Related Skills\n- scanning-infrastructure-with-nessus\n- scanning-apis-for-security-vulnerabilities\n- performing-network-vulnerability-assessment\n",{"name":5,"tags":25,"author":32,"domain":33,"license":15,"version":34,"nist_csf":35,"subdomain":26,"description":7,"mitre_attack":40},[26,27,28,29,30,31],"vulnerability-management","cve","nikto","web-scanning","owasp","risk","mahipal","cybersecurity","1.0",[36,37,38,39],"ID.RA-01","ID.RA-02","ID.IM-02","ID.RA-06",[41,42,43],"T1190","T1203","T1068","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Fperforming-web-application-scanning-with-nikto","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":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add NeelakshSaxena\u002FVayu --skill performing-web-application-scanning-with-nikto",{"tool":57,"command":58},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill performing-web-application-scanning-with-nikto",{"tool":60,"command":61},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill performing-web-application-scanning-with-nikto","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-web-application-scanning-with-nikto\u002FSKILL.md",true,[65,71,75,81,85,89,95],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"assets\u002Ftemplate.md","ASSET","资产文件",1033,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-web-application-scanning-with-nikto\u002Fassets\u002Ftemplate.md",{"path":72,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fapi-reference.md","REFERENCE","参考文档",1772,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-web-application-scanning-with-nikto\u002Freferences\u002Fapi-reference.md",{"path":82,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fstandards.md",2166,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-web-application-scanning-with-nikto\u002Freferences\u002Fstandards.md",{"path":86,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fworkflows.md",2128,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-web-application-scanning-with-nikto\u002Freferences\u002Fworkflows.md",{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"scripts\u002Fagent.py","SCRIPT","脚本",5394,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-web-application-scanning-with-nikto\u002Fscripts\u002Fagent.py",{"path":96,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":97,"sourceHtmlUrl":98},"scripts\u002Fprocess.py",12297,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-web-application-scanning-with-nikto\u002Fscripts\u002Fprocess.py",[100,107,114,121,128,135],{"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},"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":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},"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":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},"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":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},"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":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"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":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"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",[],[]]