[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A7R85JTP5SHYQCK75DT4BY":3,"skill-same:01M7A7R85JTP5SHYQCK75DT4BY":101},{"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":46,"commitSha":47,"skillDirectory":48,"forksCount":14,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M7A7R85JTP5SHYQCK75DT4BY","implementing-attack-path-analysis-with-xm-cyber",null,"Deploys XM Cyber's continuous exposure management platform to build attack graphs that chain vulnerabilities, misconfigurations, identity risks, and credential weaknesses toward critical assets, identifying the small fraction of exposures sitting on converging \"choke points\". Use when mapping attack paths across an environment or prioritizing remediation within a continuous threat exposure management (CTEM) program.","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\u002Fimplementing-attack-path-analysis-with-xm-cyber\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-attack-path-analysis-with-xm-cyber\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: implementing-attack-path-analysis-with-xm-cyber\ndescription: Deploys XM Cyber's continuous exposure management platform to build\n  attack graphs that chain vulnerabilities, misconfigurations, identity risks, and\n  credential weaknesses toward critical assets, identifying the small fraction of\n  exposures sitting on converging \"choke points\". Use when mapping attack paths\n  across an environment or prioritizing remediation within a continuous threat exposure\n  management (CTEM) program.\ndomain: cybersecurity\nsubdomain: vulnerability-management\ntags:\n- xm-cyber\n- attack-path-analysis\n- exposure-management\n- ctem\n- choke-points\n- breach-simulation\n- attack-surface\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# Implementing Attack Path Analysis with XM Cyber\n\n## Overview\nXM Cyber is a continuous exposure management platform that uses attack graph analysis to identify how adversaries can chain together exposures -- vulnerabilities, misconfigurations, identity risks, and credential weaknesses -- to reach critical business assets. According to XM Cyber's 2024 research analyzing over 40 million exposures across 11.5 million entities, organizations typically have around 15,000 exploitable exposures, but traditional CVEs account for less than 1% of total exposures. The platform identifies that only 2% of exposures reside on \"choke points\" of converging attack paths, enabling security teams to focus on fixes that eliminate the most risk with the least effort.\n\n\n## When to Use\n\n- When deploying or configuring implementing attack path analysis with xm cyber capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n- XM Cyber platform license and tenant access\n- Network connectivity to monitored environments (on-premises, cloud, hybrid)\n- Administrative access for agent deployment or agentless integration\n- Cloud provider API access (AWS, Azure, GCP) for cloud attack path analysis\n- Active Directory read access for identity-based attack path modeling\n- CMDB or asset inventory defining critical business assets\n\n## Core Concepts\n\n### Attack Graph Analysis\nUnlike point-in-time vulnerability scanning, XM Cyber continuously models all possible attack paths across the entire environment:\n\n| Traditional Scanning | XM Cyber Attack Path Analysis |\n|---------------------|-------------------------------|\n| Lists individual vulnerabilities | Maps chained attack paths |\n| Scores by CVSS severity | Scores by reachability to critical assets |\n| Point-in-time assessment | Continuous real-time modeling |\n| No context of lateral movement | Models full lateral movement chains |\n| Treats each vuln independently | Shows how vulns chain together |\n\n### Key Metrics from XM Cyber Research (2024)\n\n| Finding | Statistic |\n|---------|-----------|\n| Average exposures per organization | ~15,000 |\n| CVE-based exposures | \u003C 1% of total |\n| Misconfiguration-based exposures | ~80% of total |\n| Exposures on critical choke points | 2% |\n| Orgs where attackers can pivot on-prem to cloud | 70% |\n| Cloud critical assets compromisable in 2 hops | 93% |\n| Critical asset exposures in cloud platforms | 56% |\n\n### Choke Point Concept\nA choke point is a single entity (host, identity, credential, misconfiguration) that sits at the intersection of multiple attack paths leading to critical assets. Fixing a choke point eliminates many attack paths simultaneously, providing maximum risk reduction per remediation effort.\n\n```\nAttack Path 1:  Web Server -> SQL Injection -> DB Admin Creds\n                                                    \\\nAttack Path 2:  VPN -> Stolen Creds -> File Server   -> Domain Controller\n                                                    \u002F     (Critical Asset)\nAttack Path 3:  Workstation -> Mimikatz -> Cached Creds\n                                    ^\n                              CHOKE POINT\n                     (Cached Domain Admin credential)\n```\n\n### Exposure Categories\n\n| Category | % of Exposures | Examples |\n|----------|---------------|----------|\n| Identity & Credentials | 40% | Cached credentials, over-privileged accounts, Kerberoastable SPNs |\n| Misconfigurations | 38% | Open shares, weak permissions, missing hardening |\n| Network Exposures | 12% | Open ports, flat networks, missing segmentation |\n| Software Vulnerabilities | 8% | Unpatched CVEs, outdated software |\n| Cloud Exposures | 2% | IAM misconfig, public storage, overly permissive roles |\n\n## Workflow\n\n### Step 1: Define Critical Assets (Business Context)\n\n```\nCritical Asset Definition:\n    Tier 1 - Crown Jewels:\n        - Domain Controllers (Active Directory)\n        - Database servers with PII\u002Ffinancial data\n        - ERP systems (SAP, Oracle)\n        - Certificate Authority servers\n        - Backup infrastructure (Veeam, Commvault)\n\n    Tier 2 - High Value:\n        - Email servers (Exchange)\n        - File servers with IP\u002Ftrade secrets\n        - CI\u002FCD pipeline servers\n        - Jump servers \u002F PAM vaults\n\n    Tier 3 - Supporting Infrastructure:\n        - DNS\u002FDHCP servers\n        - Monitoring systems\n        - Logging infrastructure\n```\n\n### Step 2: Deploy XM Cyber Sensors\n\n```\nDeployment Architecture:\n    On-Premises:\n        - Install XM Cyber sensor on management server\n        - Configure AD integration (read-only service account)\n        - Enable network discovery protocols\n        - Set scanning scope (IP ranges, AD OUs)\n\n    Cloud (AWS):\n        - Deploy XM Cyber CloudConnect via CloudFormation\n        - Configure IAM role with read-only permissions\n        - Enable cross-account scanning for multi-account orgs\n\n    Cloud (Azure):\n        - Deploy via Azure Marketplace\n        - Configure Entra ID (Azure AD) integration\n        - Grant Reader role on subscriptions\n\n    Hybrid:\n        - Configure cross-environment path analysis\n        - Map on-premises to cloud trust relationships\n        - Enable identity correlation across environments\n```\n\n### Step 3: Configure Attack Scenarios\n\n```\nScenario 1: External Attacker to Domain Admin\n    Starting Point:  Internet-facing assets\n    Target:          Domain Admin privileges\n    Attack Techniques: Exploit public CVEs, credential theft,\n                      lateral movement, privilege escalation\n\nScenario 2: Insider Threat to Financial Data\n    Starting Point:  Any corporate workstation\n    Target:          Financial database servers\n    Attack Techniques: Credential harvesting, share enumeration,\n                      privilege escalation, data access\n\nScenario 3: Cloud Account Takeover\n    Starting Point:  Compromised cloud IAM user\n    Target:          Production cloud infrastructure\n    Attack Techniques: IAM privilege escalation, cross-account\n                      pivot, storage access, compute compromise\n\nScenario 4: Ransomware Propagation\n    Starting Point:  Phished workstation\n    Target:          Maximum host compromise (lateral spread)\n    Attack Techniques: Credential reuse, SMB exploitation,\n                      PsExec\u002FWMI lateral movement\n```\n\n### Step 4: Analyze Attack Path Results\n\n```python\n# Interpreting XM Cyber attack path analysis results\ndef analyze_choke_points(attack_graph_results):\n    \"\"\"Analyze attack graph results for priority remediation.\"\"\"\n\n    choke_points = []\n    for entity in attack_graph_results.get(\"entities\", []):\n        if entity.get(\"is_choke_point\"):\n            choke_points.append({\n                \"entity_name\": entity[\"name\"],\n                \"entity_type\": entity[\"type\"],\n                \"attack_paths_blocked\": entity[\"paths_through\"],\n                \"critical_assets_protected\": entity[\"protects_assets\"],\n                \"remediation_complexity\": entity[\"fix_complexity\"],\n                \"exposure_type\": entity[\"exposure_category\"],\n            })\n\n    # Sort by impact (paths blocked * assets protected)\n    choke_points.sort(\n        key=lambda x: x[\"attack_paths_blocked\"] * len(x[\"critical_assets_protected\"]),\n        reverse=True\n    )\n\n    print(f\"Total choke points identified: {len(choke_points)}\")\n    print(f\"\\nTop 10 choke points for maximum risk reduction:\")\n    for i, cp in enumerate(choke_points[:10], 1):\n        print(f\"  {i}. {cp['entity_name']} ({cp['entity_type']})\")\n        print(f\"     Paths blocked: {cp['attack_paths_blocked']}\")\n        print(f\"     Assets protected: {len(cp['critical_assets_protected'])}\")\n        print(f\"     Exposure type: {cp['exposure_type']}\")\n        print(f\"     Fix complexity: {cp['remediation_complexity']}\")\n\n    return choke_points\n```\n\n### Step 5: Prioritize Remediation by Impact\n\n```\nRemediation Priority Matrix:\n\nPriority 1 (Immediate - 48h):\n    - Choke points on paths to Tier 1 assets\n    - Identity exposures (cached Domain Admin creds)\n    - Internet-facing vulnerabilities with attack paths\n\nPriority 2 (Urgent - 7 days):\n    - Choke points on paths to Tier 2 assets\n    - Cloud IAM misconfigurations with privilege escalation\n    - Network segmentation gaps enabling lateral movement\n\nPriority 3 (Important - 30 days):\n    - Remaining choke points\n    - Misconfigurations reducing defense depth\n    - Non-critical software vulnerabilities on attack paths\n\nPriority 4 (Standard - 90 days):\n    - Exposures NOT on any attack path to critical assets\n    - Informational findings\n    - Hardening recommendations\n```\n\n## Best Practices\n1. Define critical assets before deploying the platform; attack paths without target context are meaningless\n2. Focus remediation on choke points first; fixing 2% of exposures can eliminate the majority of risk\n3. Use attack path context to justify remediation urgency to IT teams (show the chain, not just the vuln)\n4. Re-run attack path analysis after each remediation to verify paths are truly eliminated\n5. Include cloud environments in analysis; 56% of critical asset exposures exist in cloud platforms\n6. Monitor for new attack paths created by infrastructure changes (new servers, permission changes)\n7. Integrate findings with ticketing systems for automated remediation tracking\n\n## Common Pitfalls\n- Focusing solely on CVEs when 80% of exposures come from misconfigurations\n- Not defining critical assets, leading to unfocused attack path analysis\n- Treating all exposures equally instead of focusing on choke points\n- Ignoring identity-based attack paths (cached credentials, Kerberoastable accounts)\n- Not correlating on-premises and cloud attack paths in hybrid environments\n- Running analysis once instead of continuously\n\n## Related Skills\n- implementing-continuous-security-validation-with-bas\n- performing-asset-criticality-scoring-for-vulns\n- detecting-lateral-movement-in-network\n- exploiting-active-directory-with-bloodhound\n","# Implementing Attack Path Analysis with XM Cyber\n\n## Overview\nXM Cyber is a continuous exposure management platform that uses attack graph analysis to identify how adversaries can chain together exposures -- vulnerabilities, misconfigurations, identity risks, and credential weaknesses -- to reach critical business assets. According to XM Cyber's 2024 research analyzing over 40 million exposures across 11.5 million entities, organizations typically have around 15,000 exploitable exposures, but traditional CVEs account for less than 1% of total exposures. The platform identifies that only 2% of exposures reside on \"choke points\" of converging attack paths, enabling security teams to focus on fixes that eliminate the most risk with the least effort.\n\n\n## When to Use\n\n- When deploying or configuring implementing attack path analysis with xm cyber capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n- XM Cyber platform license and tenant access\n- Network connectivity to monitored environments (on-premises, cloud, hybrid)\n- Administrative access for agent deployment or agentless integration\n- Cloud provider API access (AWS, Azure, GCP) for cloud attack path analysis\n- Active Directory read access for identity-based attack path modeling\n- CMDB or asset inventory defining critical business assets\n\n## Core Concepts\n\n### Attack Graph Analysis\nUnlike point-in-time vulnerability scanning, XM Cyber continuously models all possible attack paths across the entire environment:\n\n| Traditional Scanning | XM Cyber Attack Path Analysis |\n|---------------------|-------------------------------|\n| Lists individual vulnerabilities | Maps chained attack paths |\n| Scores by CVSS severity | Scores by reachability to critical assets |\n| Point-in-time assessment | Continuous real-time modeling |\n| No context of lateral movement | Models full lateral movement chains |\n| Treats each vuln independently | Shows how vulns chain together |\n\n### Key Metrics from XM Cyber Research (2024)\n\n| Finding | Statistic |\n|---------|-----------|\n| Average exposures per organization | ~15,000 |\n| CVE-based exposures | \u003C 1% of total |\n| Misconfiguration-based exposures | ~80% of total |\n| Exposures on critical choke points | 2% |\n| Orgs where attackers can pivot on-prem to cloud | 70% |\n| Cloud critical assets compromisable in 2 hops | 93% |\n| Critical asset exposures in cloud platforms | 56% |\n\n### Choke Point Concept\nA choke point is a single entity (host, identity, credential, misconfiguration) that sits at the intersection of multiple attack paths leading to critical assets. Fixing a choke point eliminates many attack paths simultaneously, providing maximum risk reduction per remediation effort.\n\n```\nAttack Path 1:  Web Server -> SQL Injection -> DB Admin Creds\n                                                    \\\nAttack Path 2:  VPN -> Stolen Creds -> File Server   -> Domain Controller\n                                                    \u002F     (Critical Asset)\nAttack Path 3:  Workstation -> Mimikatz -> Cached Creds\n                                    ^\n                              CHOKE POINT\n                     (Cached Domain Admin credential)\n```\n\n### Exposure Categories\n\n| Category | % of Exposures | Examples |\n|----------|---------------|----------|\n| Identity & Credentials | 40% | Cached credentials, over-privileged accounts, Kerberoastable SPNs |\n| Misconfigurations | 38% | Open shares, weak permissions, missing hardening |\n| Network Exposures | 12% | Open ports, flat networks, missing segmentation |\n| Software Vulnerabilities | 8% | Unpatched CVEs, outdated software |\n| Cloud Exposures | 2% | IAM misconfig, public storage, overly permissive roles |\n\n## Workflow\n\n### Step 1: Define Critical Assets (Business Context)\n\n```\nCritical Asset Definition:\n    Tier 1 - Crown Jewels:\n        - Domain Controllers (Active Directory)\n        - Database servers with PII\u002Ffinancial data\n        - ERP systems (SAP, Oracle)\n        - Certificate Authority servers\n        - Backup infrastructure (Veeam, Commvault)\n\n    Tier 2 - High Value:\n        - Email servers (Exchange)\n        - File servers with IP\u002Ftrade secrets\n        - CI\u002FCD pipeline servers\n        - Jump servers \u002F PAM vaults\n\n    Tier 3 - Supporting Infrastructure:\n        - DNS\u002FDHCP servers\n        - Monitoring systems\n        - Logging infrastructure\n```\n\n### Step 2: Deploy XM Cyber Sensors\n\n```\nDeployment Architecture:\n    On-Premises:\n        - Install XM Cyber sensor on management server\n        - Configure AD integration (read-only service account)\n        - Enable network discovery protocols\n        - Set scanning scope (IP ranges, AD OUs)\n\n    Cloud (AWS):\n        - Deploy XM Cyber CloudConnect via CloudFormation\n        - Configure IAM role with read-only permissions\n        - Enable cross-account scanning for multi-account orgs\n\n    Cloud (Azure):\n        - Deploy via Azure Marketplace\n        - Configure Entra ID (Azure AD) integration\n        - Grant Reader role on subscriptions\n\n    Hybrid:\n        - Configure cross-environment path analysis\n        - Map on-premises to cloud trust relationships\n        - Enable identity correlation across environments\n```\n\n### Step 3: Configure Attack Scenarios\n\n```\nScenario 1: External Attacker to Domain Admin\n    Starting Point:  Internet-facing assets\n    Target:          Domain Admin privileges\n    Attack Techniques: Exploit public CVEs, credential theft,\n                      lateral movement, privilege escalation\n\nScenario 2: Insider Threat to Financial Data\n    Starting Point:  Any corporate workstation\n    Target:          Financial database servers\n    Attack Techniques: Credential harvesting, share enumeration,\n                      privilege escalation, data access\n\nScenario 3: Cloud Account Takeover\n    Starting Point:  Compromised cloud IAM user\n    Target:          Production cloud infrastructure\n    Attack Techniques: IAM privilege escalation, cross-account\n                      pivot, storage access, compute compromise\n\nScenario 4: Ransomware Propagation\n    Starting Point:  Phished workstation\n    Target:          Maximum host compromise (lateral spread)\n    Attack Techniques: Credential reuse, SMB exploitation,\n                      PsExec\u002FWMI lateral movement\n```\n\n### Step 4: Analyze Attack Path Results\n\n```python\n# Interpreting XM Cyber attack path analysis results\ndef analyze_choke_points(attack_graph_results):\n    \"\"\"Analyze attack graph results for priority remediation.\"\"\"\n\n    choke_points = []\n    for entity in attack_graph_results.get(\"entities\", []):\n        if entity.get(\"is_choke_point\"):\n            choke_points.append({\n                \"entity_name\": entity[\"name\"],\n                \"entity_type\": entity[\"type\"],\n                \"attack_paths_blocked\": entity[\"paths_through\"],\n                \"critical_assets_protected\": entity[\"protects_assets\"],\n                \"remediation_complexity\": entity[\"fix_complexity\"],\n                \"exposure_type\": entity[\"exposure_category\"],\n            })\n\n    # Sort by impact (paths blocked * assets protected)\n    choke_points.sort(\n        key=lambda x: x[\"attack_paths_blocked\"] * len(x[\"critical_assets_protected\"]),\n        reverse=True\n    )\n\n    print(f\"Total choke points identified: {len(choke_points)}\")\n    print(f\"\\nTop 10 choke points for maximum risk reduction:\")\n    for i, cp in enumerate(choke_points[:10], 1):\n        print(f\"  {i}. {cp['entity_name']} ({cp['entity_type']})\")\n        print(f\"     Paths blocked: {cp['attack_paths_blocked']}\")\n        print(f\"     Assets protected: {len(cp['critical_assets_protected'])}\")\n        print(f\"     Exposure type: {cp['exposure_type']}\")\n        print(f\"     Fix complexity: {cp['remediation_complexity']}\")\n\n    return choke_points\n```\n\n### Step 5: Prioritize Remediation by Impact\n\n```\nRemediation Priority Matrix:\n\nPriority 1 (Immediate - 48h):\n    - Choke points on paths to Tier 1 assets\n    - Identity exposures (cached Domain Admin creds)\n    - Internet-facing vulnerabilities with attack paths\n\nPriority 2 (Urgent - 7 days):\n    - Choke points on paths to Tier 2 assets\n    - Cloud IAM misconfigurations with privilege escalation\n    - Network segmentation gaps enabling lateral movement\n\nPriority 3 (Important - 30 days):\n    - Remaining choke points\n    - Misconfigurations reducing defense depth\n    - Non-critical software vulnerabilities on attack paths\n\nPriority 4 (Standard - 90 days):\n    - Exposures NOT on any attack path to critical assets\n    - Informational findings\n    - Hardening recommendations\n```\n\n## Best Practices\n1. Define critical assets before deploying the platform; attack paths without target context are meaningless\n2. Focus remediation on choke points first; fixing 2% of exposures can eliminate the majority of risk\n3. Use attack path context to justify remediation urgency to IT teams (show the chain, not just the vuln)\n4. Re-run attack path analysis after each remediation to verify paths are truly eliminated\n5. Include cloud environments in analysis; 56% of critical asset exposures exist in cloud platforms\n6. Monitor for new attack paths created by infrastructure changes (new servers, permission changes)\n7. Integrate findings with ticketing systems for automated remediation tracking\n\n## Common Pitfalls\n- Focusing solely on CVEs when 80% of exposures come from misconfigurations\n- Not defining critical assets, leading to unfocused attack path analysis\n- Treating all exposures equally instead of focusing on choke points\n- Ignoring identity-based attack paths (cached credentials, Kerberoastable accounts)\n- Not correlating on-premises and cloud attack paths in hybrid environments\n- Running analysis once instead of continuously\n\n## Related Skills\n- implementing-continuous-security-validation-with-bas\n- performing-asset-criticality-scoring-for-vulns\n- detecting-lateral-movement-in-network\n- exploiting-active-directory-with-bloodhound\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],"xm-cyber","attack-path-analysis","exposure-management","ctem","choke-points","breach-simulation","attack-surface","mahipal","cybersecurity","1.0",[37,38,39,40],"ID.RA-01","ID.RA-02","ID.IM-02","ID.RA-06","vulnerability-management",[43,44,45],"T1190","T1203","T1068","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Fimplementing-attack-path-analysis-with-xm-cyber","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":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add NeelakshSaxena\u002FVayu --skill implementing-attack-path-analysis-with-xm-cyber",{"tool":59,"command":60},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill implementing-attack-path-analysis-with-xm-cyber",{"tool":62,"command":63},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill implementing-attack-path-analysis-with-xm-cyber","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-attack-path-analysis-with-xm-cyber\u002FSKILL.md",true,[67,73,77,83,87,91,97],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"assets\u002Ftemplate.md","ASSET","资产文件",1241,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-attack-path-analysis-with-xm-cyber\u002Fassets\u002Ftemplate.md",{"path":74,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fapi-reference.md","REFERENCE","参考文档",1708,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-attack-path-analysis-with-xm-cyber\u002Freferences\u002Fapi-reference.md",{"path":84,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fstandards.md",1324,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-attack-path-analysis-with-xm-cyber\u002Freferences\u002Fstandards.md",{"path":88,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fworkflows.md",2928,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-attack-path-analysis-with-xm-cyber\u002Freferences\u002Fworkflows.md",{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"scripts\u002Fagent.py","SCRIPT","脚本",5714,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-attack-path-analysis-with-xm-cyber\u002Fscripts\u002Fagent.py",{"path":98,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":99,"sourceHtmlUrl":100},"scripts\u002Fprocess.py",8848,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-attack-path-analysis-with-xm-cyber\u002Fscripts\u002Fprocess.py",[102,109,116,123,130,137],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"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":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"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":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"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":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"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":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"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":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"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",[],[]]