[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A9MXAMK4TFT1RDK5VT9C7T":3,"skill-same:01M7A9MXAMK4TFT1RDK5VT9C7T":102},{"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":47,"commitSha":48,"skillDirectory":49,"forksCount":14,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M7A9MXAMK4TFT1RDK5VT9C7T","performing-authenticated-vulnerability-scan",null,"Plan and run authenticated (credentialed) vulnerability scans with scanners such as Nessus, Qualys, OpenVAS, or Rapid7 InsightVM, using SSH, SMB, WinRM, or SNMPv3 credentials to inspect installed software, patches, and configurations on Linux, Windows, and network devices. Use when a scan must catch vulnerabilities unauthenticated scanning misses, or when choosing and managing credential types for a credentialed scan.","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-authenticated-vulnerability-scan\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-authenticated-vulnerability-scan\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: performing-authenticated-vulnerability-scan\ndescription: Plan and run authenticated (credentialed) vulnerability scans with scanners such as\n  Nessus, Qualys, OpenVAS, or Rapid7 InsightVM, using SSH, SMB, WinRM, or SNMPv3 credentials\n  to inspect installed software, patches, and configurations on Linux, Windows, and network\n  devices. Use when a scan must catch vulnerabilities unauthenticated scanning misses, or when\n  choosing and managing credential types for a credentialed scan.\ndomain: cybersecurity\nsubdomain: vulnerability-management\ntags:\n- vulnerability-management\n- cve\n- authenticated-scanning\n- credentials\n- nessus\n- qualys\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- T1003\n- T1110\n---\n# Performing Authenticated Vulnerability Scan\n\n## Overview\nAuthenticated (credentialed) vulnerability scanning uses valid system credentials to log into target hosts and perform deep inspection of installed software, patches, configurations, and security settings. Compared to unauthenticated scanning, credentialed scans detect 45-60% more vulnerabilities with significantly fewer false positives because they can directly query installed packages, registry keys, and file system contents.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing authenticated vulnerability scan\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- Vulnerability scanner (Nessus, Qualys, OpenVAS, Rapid7 InsightVM)\n- Service accounts with appropriate privileges on target systems\n- Secure credential storage (vault integration preferred)\n- Network access from scanner to target management ports\n- Written authorization from system owners\n\n## Core Concepts\n\n### Why Authenticated Scanning\nUnauthenticated scanning can only assess externally visible services and banners, often leading to:\n- Missed vulnerabilities in locally installed software\n- Inaccurate version detection from banner changes\n- Inability to check patch levels, configurations, or local policies\n- Higher false positive rates due to inference-based detection\n\nAuthenticated scanning resolves these by directly querying the target OS.\n\n### Credential Types by Platform\n\n#### Linux\u002FUnix Systems\n- **SSH Key Authentication**: RSA\u002FEd25519 key pairs (recommended)\n- **SSH Username\u002FPassword**: Fallback for systems without key-based auth\n- **Sudo\u002FSu Elevation**: Non-root user with sudo privileges\n- **Certificate-based SSH**: X.509 certificates for enterprise environments\n\n#### Windows Systems\n- **SMB (Windows)**: Domain or local admin credentials\n- **WMI**: Windows Management Instrumentation queries\n- **WinRM**: Windows Remote Management (HTTPS preferred)\n- **Kerberos**: Domain authentication with service tickets\n\n#### Network Devices\n- **SNMP v3**: USM with authentication and privacy (AES-256)\n- **SSH**: For Cisco IOS, Juniper JunOS, Palo Alto PAN-OS\n- **API Tokens**: REST API for modern network platforms\n\n#### Databases\n- **Oracle**: SYS\u002FSYSDBA credentials or TNS connection\n- **Microsoft SQL Server**: Windows auth or SQL auth\n- **PostgreSQL**: Role-based authentication\n- **MySQL**: User\u002Fpassword with SELECT privileges\n\n## Workflow\n\n### Step 1: Create Dedicated Service Accounts\n\n```bash\n# Linux: Create scan service account\nsudo useradd -m -s \u002Fbin\u002Fbash -c \"Vulnerability Scanner Service Account\" nessus_svc\nsudo usermod -aG sudo nessus_svc\n\n# Configure sudo for passwordless specific commands\necho 'nessus_svc ALL=(ALL) NOPASSWD: \u002Fusr\u002Fbin\u002Fdpkg -l, \u002Fusr\u002Fbin\u002Frpm -qa, \\\n\u002Fbin\u002Fcat \u002Fetc\u002Fshadow, \u002Fusr\u002Fsbin\u002Fdmidecode, \u002Fusr\u002Fbin\u002Ffind' | sudo tee \u002Fetc\u002Fsudoers.d\u002Fnessus_svc\n\n# Generate SSH key pair\nsudo -u nessus_svc ssh-keygen -t ed25519 -f \u002Fhome\u002Fnessus_svc\u002F.ssh\u002Fid_ed25519 -N \"\"\n\n# Distribute public key to targets\nfor host in $(cat target_hosts.txt); do\n    ssh-copy-id -i \u002Fhome\u002Fnessus_svc\u002F.ssh\u002Fid_ed25519.pub nessus_svc@$host\ndone\n```\n\n```powershell\n# Windows: Create scan service account via PowerShell\nNew-ADUser -Name \"SVC_VulnScan\" `\n    -SamAccountName \"SVC_VulnScan\" `\n    -UserPrincipalName \"SVC_VulnScan@domain.local\" `\n    -Description \"Vulnerability Scanner Service Account\" `\n    -PasswordNeverExpires $true `\n    -CannotChangePassword $true `\n    -Enabled $true `\n    -AccountPassword (Read-Host -AsSecureString \"Enter Password\")\n\n# Add to local Administrators group on targets via GPO or:\nAdd-ADGroupMember -Identity \"Domain Admins\" -Members \"SVC_VulnScan\"\n# For least privilege, use a dedicated GPO for local admin rights instead\n\n# Enable WinRM on targets\nEnable-PSRemoting -Force\nSet-Item WSMan:\\localhost\\Service\\AllowRemote -Value $true\nwinrm set winrm\u002Fconfig\u002Fservice '@{AllowUnencrypted=\"false\"}'\n```\n\n### Step 2: Configure Scanner Credentials\n\n#### Nessus Configuration\n```json\n{\n  \"credentials\": {\n    \"add\": {\n      \"Host\": {\n        \"SSH\": [{\n          \"auth_method\": \"public key\",\n          \"username\": \"nessus_svc\",\n          \"private_key\": \"\u002Fpath\u002Fto\u002Fid_ed25519\",\n          \"elevate_privileges_with\": \"sudo\",\n          \"escalation_account\": \"root\"\n        }],\n        \"Windows\": [{\n          \"auth_method\": \"Password\",\n          \"username\": \"DOMAIN\\\\SVC_VulnScan\",\n          \"password\": \"stored_in_vault\",\n          \"domain\": \"domain.local\"\n        }],\n        \"SNMPv3\": [{\n          \"username\": \"nessus_snmpv3\",\n          \"security_level\": \"authPriv\",\n          \"auth_algorithm\": \"SHA-256\",\n          \"auth_password\": \"stored_in_vault\",\n          \"priv_algorithm\": \"AES-256\",\n          \"priv_password\": \"stored_in_vault\"\n        }]\n      }\n    }\n  }\n}\n```\n\n### Step 3: Validate Credential Access\n\n```bash\n# Test SSH connectivity\nssh -i \u002Fpath\u002Fto\u002Fkey -o ConnectTimeout=10 nessus_svc@target_host \"uname -a && sudo dpkg -l | head -5\"\n\n# Test WinRM connectivity\npython3 -c \"\nimport winrm\ns = winrm.Session('target_host', auth=('DOMAIN\\\\\\\\SVC_VulnScan', 'password'), transport='ntlm')\nr = s.run_cmd('systeminfo')\nprint(r.std_out.decode())\n\"\n\n# Test SNMP v3 connectivity\nsnmpwalk -v3 -u nessus_snmpv3 -l authPriv -a SHA-256 -A authpass -x AES-256 -X privpass target_host sysDescr.0\n```\n\n### Step 4: Run Authenticated Scan\n\nConfigure and launch the scan using the Nessus API:\n```bash\n# Create scan with credentials\ncurl -k -X POST https:\u002F\u002Fnessus:8834\u002Fscans \\\n  -H \"X-Cookie: token=$TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"uuid\": \"'$TEMPLATE_UUID'\",\n    \"settings\": {\n      \"name\": \"Authenticated Scan - Production\",\n      \"text_targets\": \"192.168.1.0\u002F24\",\n      \"launch\": \"ON_DEMAND\"\n    },\n    \"credentials\": {\n      \"add\": {\n        \"Host\": {\n          \"SSH\": [{\"auth_method\": \"public key\", \"username\": \"nessus_svc\", \"private_key\": \"\u002Fkeys\u002Fid_ed25519\"}],\n          \"Windows\": [{\"auth_method\": \"Password\", \"username\": \"DOMAIN\\\\SVC_VulnScan\", \"password\": \"vault_ref\"}]\n        }\n      }\n    }\n  }'\n```\n\n### Step 5: Verify Credential Success\n\nAfter scan completion, check credential verification results:\n- **Plugin 19506** (Nessus Scan Information): Shows credential status\n- **Plugin 21745** (OS Security Patch Assessment): Confirms local checks\n- **Plugin 117887** (Local Security Checks): Credential verification\n- **Plugin 110385** (Nessus Credentialed Check): Target-level auth status\n\n## Credential Security Best Practices\n\n1. **Use a secrets vault** (HashiCorp Vault, CyberArk, AWS Secrets Manager) for credential storage\n2. **Rotate credentials** every 90 days or after personnel changes\n3. **Principle of least privilege** - only grant minimum required access\n4. **Audit credential usage** - monitor service account login events\n5. **Encrypt in transit** - use SSH keys over passwords, WinRM over HTTPS\n6. **Separate accounts** per scanner - never share credentials across tools\n7. **Disable interactive login** for scan service accounts where possible\n8. **Log all authentication** events for scan accounts in SIEM\n\n## Common Pitfalls\n- Using domain admin accounts instead of least-privilege service accounts\n- Storing credentials in plaintext scan configurations\n- Not testing credentials before scan launch (leads to wasted scan windows)\n- Forgetting to configure sudo\u002Felevation for Linux targets\n- Windows UAC blocking remote credentialed checks\n- Firewall rules blocking WMI\u002FWinRM\u002FSSH between scanner and targets\n- Credential lockout from multiple failed authentication attempts\n\n## Related Skills\n- scanning-infrastructure-with-nessus\n- performing-network-vulnerability-assessment\n- implementing-continuous-vulnerability-monitoring\n","# Performing Authenticated Vulnerability Scan\n\n## Overview\nAuthenticated (credentialed) vulnerability scanning uses valid system credentials to log into target hosts and perform deep inspection of installed software, patches, configurations, and security settings. Compared to unauthenticated scanning, credentialed scans detect 45-60% more vulnerabilities with significantly fewer false positives because they can directly query installed packages, registry keys, and file system contents.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing authenticated vulnerability scan\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- Vulnerability scanner (Nessus, Qualys, OpenVAS, Rapid7 InsightVM)\n- Service accounts with appropriate privileges on target systems\n- Secure credential storage (vault integration preferred)\n- Network access from scanner to target management ports\n- Written authorization from system owners\n\n## Core Concepts\n\n### Why Authenticated Scanning\nUnauthenticated scanning can only assess externally visible services and banners, often leading to:\n- Missed vulnerabilities in locally installed software\n- Inaccurate version detection from banner changes\n- Inability to check patch levels, configurations, or local policies\n- Higher false positive rates due to inference-based detection\n\nAuthenticated scanning resolves these by directly querying the target OS.\n\n### Credential Types by Platform\n\n#### Linux\u002FUnix Systems\n- **SSH Key Authentication**: RSA\u002FEd25519 key pairs (recommended)\n- **SSH Username\u002FPassword**: Fallback for systems without key-based auth\n- **Sudo\u002FSu Elevation**: Non-root user with sudo privileges\n- **Certificate-based SSH**: X.509 certificates for enterprise environments\n\n#### Windows Systems\n- **SMB (Windows)**: Domain or local admin credentials\n- **WMI**: Windows Management Instrumentation queries\n- **WinRM**: Windows Remote Management (HTTPS preferred)\n- **Kerberos**: Domain authentication with service tickets\n\n#### Network Devices\n- **SNMP v3**: USM with authentication and privacy (AES-256)\n- **SSH**: For Cisco IOS, Juniper JunOS, Palo Alto PAN-OS\n- **API Tokens**: REST API for modern network platforms\n\n#### Databases\n- **Oracle**: SYS\u002FSYSDBA credentials or TNS connection\n- **Microsoft SQL Server**: Windows auth or SQL auth\n- **PostgreSQL**: Role-based authentication\n- **MySQL**: User\u002Fpassword with SELECT privileges\n\n## Workflow\n\n### Step 1: Create Dedicated Service Accounts\n\n```bash\n# Linux: Create scan service account\nsudo useradd -m -s \u002Fbin\u002Fbash -c \"Vulnerability Scanner Service Account\" nessus_svc\nsudo usermod -aG sudo nessus_svc\n\n# Configure sudo for passwordless specific commands\necho 'nessus_svc ALL=(ALL) NOPASSWD: \u002Fusr\u002Fbin\u002Fdpkg -l, \u002Fusr\u002Fbin\u002Frpm -qa, \\\n\u002Fbin\u002Fcat \u002Fetc\u002Fshadow, \u002Fusr\u002Fsbin\u002Fdmidecode, \u002Fusr\u002Fbin\u002Ffind' | sudo tee \u002Fetc\u002Fsudoers.d\u002Fnessus_svc\n\n# Generate SSH key pair\nsudo -u nessus_svc ssh-keygen -t ed25519 -f \u002Fhome\u002Fnessus_svc\u002F.ssh\u002Fid_ed25519 -N \"\"\n\n# Distribute public key to targets\nfor host in $(cat target_hosts.txt); do\n    ssh-copy-id -i \u002Fhome\u002Fnessus_svc\u002F.ssh\u002Fid_ed25519.pub nessus_svc@$host\ndone\n```\n\n```powershell\n# Windows: Create scan service account via PowerShell\nNew-ADUser -Name \"SVC_VulnScan\" `\n    -SamAccountName \"SVC_VulnScan\" `\n    -UserPrincipalName \"SVC_VulnScan@domain.local\" `\n    -Description \"Vulnerability Scanner Service Account\" `\n    -PasswordNeverExpires $true `\n    -CannotChangePassword $true `\n    -Enabled $true `\n    -AccountPassword (Read-Host -AsSecureString \"Enter Password\")\n\n# Add to local Administrators group on targets via GPO or:\nAdd-ADGroupMember -Identity \"Domain Admins\" -Members \"SVC_VulnScan\"\n# For least privilege, use a dedicated GPO for local admin rights instead\n\n# Enable WinRM on targets\nEnable-PSRemoting -Force\nSet-Item WSMan:\\localhost\\Service\\AllowRemote -Value $true\nwinrm set winrm\u002Fconfig\u002Fservice '@{AllowUnencrypted=\"false\"}'\n```\n\n### Step 2: Configure Scanner Credentials\n\n#### Nessus Configuration\n```json\n{\n  \"credentials\": {\n    \"add\": {\n      \"Host\": {\n        \"SSH\": [{\n          \"auth_method\": \"public key\",\n          \"username\": \"nessus_svc\",\n          \"private_key\": \"\u002Fpath\u002Fto\u002Fid_ed25519\",\n          \"elevate_privileges_with\": \"sudo\",\n          \"escalation_account\": \"root\"\n        }],\n        \"Windows\": [{\n          \"auth_method\": \"Password\",\n          \"username\": \"DOMAIN\\\\SVC_VulnScan\",\n          \"password\": \"stored_in_vault\",\n          \"domain\": \"domain.local\"\n        }],\n        \"SNMPv3\": [{\n          \"username\": \"nessus_snmpv3\",\n          \"security_level\": \"authPriv\",\n          \"auth_algorithm\": \"SHA-256\",\n          \"auth_password\": \"stored_in_vault\",\n          \"priv_algorithm\": \"AES-256\",\n          \"priv_password\": \"stored_in_vault\"\n        }]\n      }\n    }\n  }\n}\n```\n\n### Step 3: Validate Credential Access\n\n```bash\n# Test SSH connectivity\nssh -i \u002Fpath\u002Fto\u002Fkey -o ConnectTimeout=10 nessus_svc@target_host \"uname -a && sudo dpkg -l | head -5\"\n\n# Test WinRM connectivity\npython3 -c \"\nimport winrm\ns = winrm.Session('target_host', auth=('DOMAIN\\\\\\\\SVC_VulnScan', 'password'), transport='ntlm')\nr = s.run_cmd('systeminfo')\nprint(r.std_out.decode())\n\"\n\n# Test SNMP v3 connectivity\nsnmpwalk -v3 -u nessus_snmpv3 -l authPriv -a SHA-256 -A authpass -x AES-256 -X privpass target_host sysDescr.0\n```\n\n### Step 4: Run Authenticated Scan\n\nConfigure and launch the scan using the Nessus API:\n```bash\n# Create scan with credentials\ncurl -k -X POST https:\u002F\u002Fnessus:8834\u002Fscans \\\n  -H \"X-Cookie: token=$TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"uuid\": \"'$TEMPLATE_UUID'\",\n    \"settings\": {\n      \"name\": \"Authenticated Scan - Production\",\n      \"text_targets\": \"192.168.1.0\u002F24\",\n      \"launch\": \"ON_DEMAND\"\n    },\n    \"credentials\": {\n      \"add\": {\n        \"Host\": {\n          \"SSH\": [{\"auth_method\": \"public key\", \"username\": \"nessus_svc\", \"private_key\": \"\u002Fkeys\u002Fid_ed25519\"}],\n          \"Windows\": [{\"auth_method\": \"Password\", \"username\": \"DOMAIN\\\\SVC_VulnScan\", \"password\": \"vault_ref\"}]\n        }\n      }\n    }\n  }'\n```\n\n### Step 5: Verify Credential Success\n\nAfter scan completion, check credential verification results:\n- **Plugin 19506** (Nessus Scan Information): Shows credential status\n- **Plugin 21745** (OS Security Patch Assessment): Confirms local checks\n- **Plugin 117887** (Local Security Checks): Credential verification\n- **Plugin 110385** (Nessus Credentialed Check): Target-level auth status\n\n## Credential Security Best Practices\n\n1. **Use a secrets vault** (HashiCorp Vault, CyberArk, AWS Secrets Manager) for credential storage\n2. **Rotate credentials** every 90 days or after personnel changes\n3. **Principle of least privilege** - only grant minimum required access\n4. **Audit credential usage** - monitor service account login events\n5. **Encrypt in transit** - use SSH keys over passwords, WinRM over HTTPS\n6. **Separate accounts** per scanner - never share credentials across tools\n7. **Disable interactive login** for scan service accounts where possible\n8. **Log all authentication** events for scan accounts in SIEM\n\n## Common Pitfalls\n- Using domain admin accounts instead of least-privilege service accounts\n- Storing credentials in plaintext scan configurations\n- Not testing credentials before scan launch (leads to wasted scan windows)\n- Forgetting to configure sudo\u002Felevation for Linux targets\n- Windows UAC blocking remote credentialed checks\n- Firewall rules blocking WMI\u002FWinRM\u002FSSH between scanner and targets\n- Credential lockout from multiple failed authentication attempts\n\n## Related Skills\n- scanning-infrastructure-with-nessus\n- performing-network-vulnerability-assessment\n- implementing-continuous-vulnerability-monitoring\n",{"name":5,"tags":25,"author":33,"domain":34,"license":15,"version":35,"nist_csf":36,"subdomain":26,"description":7,"mitre_attack":41},[26,27,28,29,30,31,32],"vulnerability-management","cve","authenticated-scanning","credentials","nessus","qualys","risk","mahipal","cybersecurity","1.0",[37,38,39,40],"ID.RA-01","ID.RA-02","ID.IM-02","ID.RA-06",[42,43,44,45,46],"T1190","T1203","T1068","T1003","T1110","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Fperforming-authenticated-vulnerability-scan","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":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add NeelakshSaxena\u002FVayu --skill performing-authenticated-vulnerability-scan",{"tool":60,"command":61},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill performing-authenticated-vulnerability-scan",{"tool":63,"command":64},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill performing-authenticated-vulnerability-scan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-authenticated-vulnerability-scan\u002FSKILL.md",true,[68,74,78,84,88,92,98],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"assets\u002Ftemplate.md","ASSET","资产文件",1320,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-authenticated-vulnerability-scan\u002Fassets\u002Ftemplate.md",{"path":75,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fapi-reference.md","REFERENCE","参考文档",2088,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-authenticated-vulnerability-scan\u002Freferences\u002Fapi-reference.md",{"path":85,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fstandards.md",2292,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-authenticated-vulnerability-scan\u002Freferences\u002Fstandards.md",{"path":89,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fworkflows.md",3362,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-authenticated-vulnerability-scan\u002Freferences\u002Fworkflows.md",{"path":93,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"scripts\u002Fagent.py","SCRIPT","脚本",6960,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-authenticated-vulnerability-scan\u002Fscripts\u002Fagent.py",{"path":99,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":100,"sourceHtmlUrl":101},"scripts\u002Fprocess.py",14567,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-authenticated-vulnerability-scan\u002Fscripts\u002Fprocess.py",[103,110,117,124,131,138],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"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":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"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":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"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":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"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":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"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":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"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",[],[]]