[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A4H8YVM5KX617CV7BV0ZCF":3,"skill-same:01M7A4H8YVM5KX617CV7BV0ZCF":81},{"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":40,"commitSha":41,"skillDirectory":42,"forksCount":14,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":45,"updatedAt":46,"install":47,"resources":60},"01M7A4H8YVM5KX617CV7BV0ZCF","benchmarking-kubernetes-with-kube-bench",null,"Installs and runs the kube-bench tool against a Kubernetes cluster as a Job, DaemonSet, or standalone binary, selecting the correct benchmark version and targets (control plane, etcd, kubelet, worker nodes) and emitting JSON or JUnit output for pipelines. Use when setting kube-bench up for the first time, choosing which benchmark version and node targets to run, wiring it into CI, or troubleshooting skipped or misdetected checks. Keywords: kube-bench, DaemonSet, --benchmark, --targets, JSON output, JUnit, CI integration. Do not use for interpreting the findings or producing an audit report - use performing-kubernetes-cis-benchmark-with-kube-bench.","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\u002Fbenchmarking-kubernetes-with-kube-bench\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbenchmarking-kubernetes-with-kube-bench\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: benchmarking-kubernetes-with-kube-bench\ndescription: >-\n  Installs and runs the kube-bench tool against a Kubernetes cluster as a Job, DaemonSet, or\n  standalone binary, selecting the correct benchmark version and targets (control plane, etcd,\n  kubelet, worker nodes) and emitting JSON or JUnit output for pipelines. Use when setting\n  kube-bench up for the first time, choosing which benchmark version and node targets to run,\n  wiring it into CI, or troubleshooting skipped or misdetected checks. Keywords: kube-bench,\n  DaemonSet, --benchmark, --targets, JSON output, JUnit, CI integration. Do not use for\n  interpreting the findings or producing an audit report - use\n  performing-kubernetes-cis-benchmark-with-kube-bench.\ndomain: cybersecurity\nsubdomain: container-security\ntags:\n- kubernetes\n- kube-bench\n- cis-benchmark\n- container-security\n- hardening\n- compliance\n- cluster-security\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\nmitre_attack:\n- T1610\n---\n# Benchmarking Kubernetes with kube-bench\n\n## Overview\n\nkube-bench (by Aqua Security) is an open-source tool that checks whether a Kubernetes cluster is deployed securely by running the checks documented in the **CIS Kubernetes Benchmark**. It inspects the control-plane components (API server, controller manager, scheduler, etcd), the kubelet and worker-node configuration, and cluster-wide policy settings, then reports each check as PASS, FAIL, WARN, or INFO with a remediation recommendation drawn directly from the CIS guidance. Tests are configuration-driven YAML files, so kube-bench tracks new Kubernetes versions and benchmark revisions and supports managed distributions (EKS, GKE, AKS, ACK, OpenShift, RKE, k3s).\n\nHardening a cluster against the CIS Benchmark directly reduces the attack surface for **T1610 (Deploy Container)**, where an adversary deploys a container to execute code or evade defenses — for example by abusing privileged containers, host namespaces, anonymous API access, or insecure kubelet settings that an unhardened cluster leaves exposed.\n\nkube-bench can run as a standalone binary on a node, inside a container, or — most commonly — as a Kubernetes Job whose pod has the host filesystem mounted so it can read the relevant config files. Output is available as human-readable text, JSON, JUnit, or AWS Security Finding Format (ASFF) and can be pushed to a PostgreSQL database for trend tracking.\n\n## When to Use\n\n- When establishing a security baseline for a new Kubernetes cluster against the CIS Kubernetes Benchmark.\n- When performing periodic compliance audits of control-plane and node hardening.\n- When validating remediation after applying hardening changes (re-run to confirm checks now PASS).\n- When integrating cluster compliance scanning into CI\u002FCD or a continuous monitoring pipeline.\n- When preparing evidence for SOC 2, PCI DSS, or internal hardening compliance.\n\n## Prerequisites\n\n- Access to the cluster: either SSH access to a control-plane\u002Fworker node (binary mode) or `kubectl` with permission to create Jobs (in-cluster mode).\n- Knowledge of the cluster's Kubernetes version (kube-bench auto-detects, or specify with `--version` \u002F `--benchmark`).\n- Install kube-bench (Aqua Security official methods):\n\n```bash\n# Binary release (Linux)\nKB_VERSION=0.10.7\ncurl -L -o kube-bench.tgz \\\n  \"https:\u002F\u002Fgithub.com\u002Faquasecurity\u002Fkube-bench\u002Freleases\u002Fdownload\u002Fv${KB_VERSION}\u002Fkube-bench_${KB_VERSION}_linux_amd64.tar.gz\"\ntar -xzf kube-bench.tgz\nsudo mv kube-bench \u002Fusr\u002Flocal\u002Fbin\u002F\nsudo cp -R cfg \u002Fetc\u002Fkube-bench\u002Fcfg\n\n# Via Go install\ngo install github.com\u002Faquasecurity\u002Fkube-bench@latest\n\n# Run as a one-off container directly on a node (mounts host config)\ndocker run --rm --pid=host \\\n  -v \u002Fetc:\u002Fetc:ro -v \u002Fvar:\u002Fvar:ro \\\n  -t docker.io\u002Faquasec\u002Fkube-bench:latest run --targets node\n\n# Verify\nkube-bench version\n```\n\n## Objectives\n\n- Run kube-bench against the appropriate benchmark for the cluster's Kubernetes version.\n- Scan control-plane (master), node, etcd, control-plane policies, and managed-service targets.\n- Produce machine-readable JSON\u002FJUnit output for pipelines and dashboards.\n- Triage FAIL and WARN results and apply CIS remediation guidance.\n- Re-run to validate that remediations now PASS.\n\n## MITRE ATT&CK Mapping\n\n| Technique ID | Name | Tactic | Relevance |\n|--------------|------|--------|-----------|\n| T1610 | Deploy Container | Execution \u002F Defense Evasion | CIS Benchmark hardening enforced by kube-bench restricts privileged\u002Fhost-namespace deployments, anonymous API access, and insecure kubelet settings that adversaries abuse when deploying malicious containers. |\n\n## Workflow\n\n### 1. Run the default scan (auto-detect)\n\nRun all applicable targets, letting kube-bench detect the Kubernetes version and benchmark:\n\n```bash\nsudo kube-bench\n```\n\n### 2. Run as a Kubernetes Job (in-cluster)\n\nApply the provided Job manifest from the kube-bench repo and read the results from the pod logs:\n\n```bash\n# General-purpose job\nkubectl apply -f https:\u002F\u002Fraw.githubusercontent.com\u002Faquasecurity\u002Fkube-bench\u002Fmain\u002Fjob.yaml\n\n# Wait, then retrieve results\nkubectl get pods -l app=kube-bench\nkubectl logs -l app=kube-bench\n\n# Platform-specific jobs are available, e.g. EKS:\nkubectl apply -f https:\u002F\u002Fraw.githubusercontent.com\u002Faquasecurity\u002Fkube-bench\u002Fmain\u002Fjob-eks.yaml\n```\n\n### 3. Target specific components\n\nUse `run --targets` to scope the scan to particular component groups:\n\n```bash\n# Control-plane (API server, scheduler, controller manager)\nsudo kube-bench run --targets master\n\n# Worker node (kubelet, proxy)\nsudo kube-bench run --targets node\n\n# etcd datastore\nsudo kube-bench run --targets etcd\n\n# Cluster-wide policies (RBAC, pod security, network policy)\nsudo kube-bench run --targets policies\n\n# Combine multiple targets\nsudo kube-bench run --targets master,node,etcd,policies\n```\n\n### 4. Pin a specific benchmark or Kubernetes version\n\nWhen auto-detection is wrong or you must audit against a specific revision, pin the benchmark explicitly:\n\n```bash\n# Pin to a specific CIS benchmark revision\nsudo kube-bench run --benchmark cis-1.8\n\n# Or map by Kubernetes version\nsudo kube-bench --version 1.27\n\n# Managed\u002Fdistribution-specific benchmarks\nsudo kube-bench run --benchmark eks-1.5.0\nsudo kube-bench run --benchmark gke-1.6.0\nsudo kube-bench run --benchmark rke2-cis-1.7\n```\n\n### 5. Run or skip individual checks\n\nFocus on or exclude specific check IDs during remediation cycles:\n\n```bash\n# Run only specific checks\nsudo kube-bench run --targets master --check 1.2.1,1.2.2\n\n# Skip noisy\u002Fknown-accepted checks\nsudo kube-bench run --targets node --skip 4.2.6\n```\n\n### 6. Produce machine-readable output\n\nEmit JSON or JUnit for ingestion into pipelines, SIEM, or dashboards, and write to a file:\n\n```bash\n# JSON to a file\nsudo kube-bench run --targets master,node --json --outputfile kube-bench-report.json\n\n# JUnit (for CI test reporting)\nsudo kube-bench --junit --outputfile kube-bench-junit.xml\n\n# AWS Security Finding Format (for Security Hub)\nsudo kube-bench run --targets node --asff\n```\n\n### 7. Triage and remediate FAIL\u002FWARN findings\n\nEach failing check prints a remediation. Apply the CIS-recommended fix on the node\u002Fmanifest, for example tightening API server flags in the static pod manifest:\n\n```bash\n# Example remediation for a common control-plane FAIL:\n# CIS 1.2.x — ensure anonymous-auth is disabled on the API server.\n# Edit the static pod manifest and set the flag:\nsudo vi \u002Fetc\u002Fkubernetes\u002Fmanifests\u002Fkube-apiserver.yaml\n#   - --anonymous-auth=false\n# The kubelet restarts the static pod automatically.\n\n# Example node remediation — kubelet config file permissions (CIS 4.1.x):\nsudo chmod 600 \u002Fetc\u002Fkubernetes\u002Fkubelet\u002Fkubelet-config.json\nsudo chown root:root \u002Fetc\u002Fkubernetes\u002Fkubelet\u002Fkubelet-config.json\n```\n\n### 8. Re-validate after remediation\n\nRe-run the relevant target and confirm the previously failing checks now PASS, then track the score over time:\n\n```bash\nsudo kube-bench run --targets master --check 1.2.1 --json --outputfile recheck.json\n\n# Optional: persist results to PostgreSQL for trend tracking\nsudo kube-bench run --targets master,node --pgsql\n```\n\n## Tools and Resources\n\n| Tool \u002F Resource | Purpose | Link |\n|------------------|---------|------|\n| kube-bench | CIS Kubernetes Benchmark checker | https:\u002F\u002Fgithub.com\u002Faquasecurity\u002Fkube-bench |\n| kube-bench docs | Running \u002F platforms \u002F flags | https:\u002F\u002Faquasecurity.github.io\u002Fkube-bench\u002F |\n| CIS Kubernetes Benchmark | Source hardening standard | https:\u002F\u002Fwww.cisecurity.org\u002Fbenchmark\u002Fkubernetes |\n| Trivy Operator | Continuous in-cluster compliance + vuln scanning | https:\u002F\u002Fgithub.com\u002Faquasecurity\u002Ftrivy-operator |\n| kube-hunter | Complementary penetration-testing tool | https:\u002F\u002Fgithub.com\u002Faquasecurity\u002Fkube-hunter |\n\n## Validation Criteria\n\n- [ ] kube-bench installed (`kube-bench version`) or running as a Job.\n- [ ] Scan run against the correct benchmark for the cluster's Kubernetes version.\n- [ ] master, node, etcd, and policies targets each scanned.\n- [ ] JSON\u002FJUnit output produced for pipeline\u002Fdashboard ingestion.\n- [ ] FAIL and WARN findings triaged and prioritized.\n- [ ] CIS remediation applied to control-plane manifests and node configs.\n- [ ] Re-run confirms previously failing checks now PASS.\n- [ ] Results tracked over time (file archive or PostgreSQL).\n","# Benchmarking Kubernetes with kube-bench\n\n## Overview\n\nkube-bench (by Aqua Security) is an open-source tool that checks whether a Kubernetes cluster is deployed securely by running the checks documented in the **CIS Kubernetes Benchmark**. It inspects the control-plane components (API server, controller manager, scheduler, etcd), the kubelet and worker-node configuration, and cluster-wide policy settings, then reports each check as PASS, FAIL, WARN, or INFO with a remediation recommendation drawn directly from the CIS guidance. Tests are configuration-driven YAML files, so kube-bench tracks new Kubernetes versions and benchmark revisions and supports managed distributions (EKS, GKE, AKS, ACK, OpenShift, RKE, k3s).\n\nHardening a cluster against the CIS Benchmark directly reduces the attack surface for **T1610 (Deploy Container)**, where an adversary deploys a container to execute code or evade defenses — for example by abusing privileged containers, host namespaces, anonymous API access, or insecure kubelet settings that an unhardened cluster leaves exposed.\n\nkube-bench can run as a standalone binary on a node, inside a container, or — most commonly — as a Kubernetes Job whose pod has the host filesystem mounted so it can read the relevant config files. Output is available as human-readable text, JSON, JUnit, or AWS Security Finding Format (ASFF) and can be pushed to a PostgreSQL database for trend tracking.\n\n## When to Use\n\n- When establishing a security baseline for a new Kubernetes cluster against the CIS Kubernetes Benchmark.\n- When performing periodic compliance audits of control-plane and node hardening.\n- When validating remediation after applying hardening changes (re-run to confirm checks now PASS).\n- When integrating cluster compliance scanning into CI\u002FCD or a continuous monitoring pipeline.\n- When preparing evidence for SOC 2, PCI DSS, or internal hardening compliance.\n\n## Prerequisites\n\n- Access to the cluster: either SSH access to a control-plane\u002Fworker node (binary mode) or `kubectl` with permission to create Jobs (in-cluster mode).\n- Knowledge of the cluster's Kubernetes version (kube-bench auto-detects, or specify with `--version` \u002F `--benchmark`).\n- Install kube-bench (Aqua Security official methods):\n\n```bash\n# Binary release (Linux)\nKB_VERSION=0.10.7\ncurl -L -o kube-bench.tgz \\\n  \"https:\u002F\u002Fgithub.com\u002Faquasecurity\u002Fkube-bench\u002Freleases\u002Fdownload\u002Fv${KB_VERSION}\u002Fkube-bench_${KB_VERSION}_linux_amd64.tar.gz\"\ntar -xzf kube-bench.tgz\nsudo mv kube-bench \u002Fusr\u002Flocal\u002Fbin\u002F\nsudo cp -R cfg \u002Fetc\u002Fkube-bench\u002Fcfg\n\n# Via Go install\ngo install github.com\u002Faquasecurity\u002Fkube-bench@latest\n\n# Run as a one-off container directly on a node (mounts host config)\ndocker run --rm --pid=host \\\n  -v \u002Fetc:\u002Fetc:ro -v \u002Fvar:\u002Fvar:ro \\\n  -t docker.io\u002Faquasec\u002Fkube-bench:latest run --targets node\n\n# Verify\nkube-bench version\n```\n\n## Objectives\n\n- Run kube-bench against the appropriate benchmark for the cluster's Kubernetes version.\n- Scan control-plane (master), node, etcd, control-plane policies, and managed-service targets.\n- Produce machine-readable JSON\u002FJUnit output for pipelines and dashboards.\n- Triage FAIL and WARN results and apply CIS remediation guidance.\n- Re-run to validate that remediations now PASS.\n\n## MITRE ATT&CK Mapping\n\n| Technique ID | Name | Tactic | Relevance |\n|--------------|------|--------|-----------|\n| T1610 | Deploy Container | Execution \u002F Defense Evasion | CIS Benchmark hardening enforced by kube-bench restricts privileged\u002Fhost-namespace deployments, anonymous API access, and insecure kubelet settings that adversaries abuse when deploying malicious containers. |\n\n## Workflow\n\n### 1. Run the default scan (auto-detect)\n\nRun all applicable targets, letting kube-bench detect the Kubernetes version and benchmark:\n\n```bash\nsudo kube-bench\n```\n\n### 2. Run as a Kubernetes Job (in-cluster)\n\nApply the provided Job manifest from the kube-bench repo and read the results from the pod logs:\n\n```bash\n# General-purpose job\nkubectl apply -f https:\u002F\u002Fraw.githubusercontent.com\u002Faquasecurity\u002Fkube-bench\u002Fmain\u002Fjob.yaml\n\n# Wait, then retrieve results\nkubectl get pods -l app=kube-bench\nkubectl logs -l app=kube-bench\n\n# Platform-specific jobs are available, e.g. EKS:\nkubectl apply -f https:\u002F\u002Fraw.githubusercontent.com\u002Faquasecurity\u002Fkube-bench\u002Fmain\u002Fjob-eks.yaml\n```\n\n### 3. Target specific components\n\nUse `run --targets` to scope the scan to particular component groups:\n\n```bash\n# Control-plane (API server, scheduler, controller manager)\nsudo kube-bench run --targets master\n\n# Worker node (kubelet, proxy)\nsudo kube-bench run --targets node\n\n# etcd datastore\nsudo kube-bench run --targets etcd\n\n# Cluster-wide policies (RBAC, pod security, network policy)\nsudo kube-bench run --targets policies\n\n# Combine multiple targets\nsudo kube-bench run --targets master,node,etcd,policies\n```\n\n### 4. Pin a specific benchmark or Kubernetes version\n\nWhen auto-detection is wrong or you must audit against a specific revision, pin the benchmark explicitly:\n\n```bash\n# Pin to a specific CIS benchmark revision\nsudo kube-bench run --benchmark cis-1.8\n\n# Or map by Kubernetes version\nsudo kube-bench --version 1.27\n\n# Managed\u002Fdistribution-specific benchmarks\nsudo kube-bench run --benchmark eks-1.5.0\nsudo kube-bench run --benchmark gke-1.6.0\nsudo kube-bench run --benchmark rke2-cis-1.7\n```\n\n### 5. Run or skip individual checks\n\nFocus on or exclude specific check IDs during remediation cycles:\n\n```bash\n# Run only specific checks\nsudo kube-bench run --targets master --check 1.2.1,1.2.2\n\n# Skip noisy\u002Fknown-accepted checks\nsudo kube-bench run --targets node --skip 4.2.6\n```\n\n### 6. Produce machine-readable output\n\nEmit JSON or JUnit for ingestion into pipelines, SIEM, or dashboards, and write to a file:\n\n```bash\n# JSON to a file\nsudo kube-bench run --targets master,node --json --outputfile kube-bench-report.json\n\n# JUnit (for CI test reporting)\nsudo kube-bench --junit --outputfile kube-bench-junit.xml\n\n# AWS Security Finding Format (for Security Hub)\nsudo kube-bench run --targets node --asff\n```\n\n### 7. Triage and remediate FAIL\u002FWARN findings\n\nEach failing check prints a remediation. Apply the CIS-recommended fix on the node\u002Fmanifest, for example tightening API server flags in the static pod manifest:\n\n```bash\n# Example remediation for a common control-plane FAIL:\n# CIS 1.2.x — ensure anonymous-auth is disabled on the API server.\n# Edit the static pod manifest and set the flag:\nsudo vi \u002Fetc\u002Fkubernetes\u002Fmanifests\u002Fkube-apiserver.yaml\n#   - --anonymous-auth=false\n# The kubelet restarts the static pod automatically.\n\n# Example node remediation — kubelet config file permissions (CIS 4.1.x):\nsudo chmod 600 \u002Fetc\u002Fkubernetes\u002Fkubelet\u002Fkubelet-config.json\nsudo chown root:root \u002Fetc\u002Fkubernetes\u002Fkubelet\u002Fkubelet-config.json\n```\n\n### 8. Re-validate after remediation\n\nRe-run the relevant target and confirm the previously failing checks now PASS, then track the score over time:\n\n```bash\nsudo kube-bench run --targets master --check 1.2.1 --json --outputfile recheck.json\n\n# Optional: persist results to PostgreSQL for trend tracking\nsudo kube-bench run --targets master,node --pgsql\n```\n\n## Tools and Resources\n\n| Tool \u002F Resource | Purpose | Link |\n|------------------|---------|------|\n| kube-bench | CIS Kubernetes Benchmark checker | https:\u002F\u002Fgithub.com\u002Faquasecurity\u002Fkube-bench |\n| kube-bench docs | Running \u002F platforms \u002F flags | https:\u002F\u002Faquasecurity.github.io\u002Fkube-bench\u002F |\n| CIS Kubernetes Benchmark | Source hardening standard | https:\u002F\u002Fwww.cisecurity.org\u002Fbenchmark\u002Fkubernetes |\n| Trivy Operator | Continuous in-cluster compliance + vuln scanning | https:\u002F\u002Fgithub.com\u002Faquasecurity\u002Ftrivy-operator |\n| kube-hunter | Complementary penetration-testing tool | https:\u002F\u002Fgithub.com\u002Faquasecurity\u002Fkube-hunter |\n\n## Validation Criteria\n\n- [ ] kube-bench installed (`kube-bench version`) or running as a Job.\n- [ ] Scan run against the correct benchmark for the cluster's Kubernetes version.\n- [ ] master, node, etcd, and policies targets each scanned.\n- [ ] JSON\u002FJUnit output produced for pipeline\u002Fdashboard ingestion.\n- [ ] FAIL and WARN findings triaged and prioritized.\n- [ ] CIS remediation applied to control-plane manifests and node configs.\n- [ ] Re-run confirms previously failing checks now PASS.\n- [ ] Results tracked over time (file archive or PostgreSQL).\n",{"name":5,"tags":25,"author":33,"domain":34,"license":15,"version":35,"nist_csf":36,"subdomain":29,"description":7,"mitre_attack":38},[26,27,28,29,30,31,32],"kubernetes","kube-bench","cis-benchmark","container-security","hardening","compliance","cluster-security","mahipal","cybersecurity","1.0",[37],"PR.PS-01",[39],"T1610","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Fbenchmarking-kubernetes-with-kube-bench","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":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add NeelakshSaxena\u002FVayu --skill benchmarking-kubernetes-with-kube-bench",{"tool":53,"command":54},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill benchmarking-kubernetes-with-kube-bench",{"tool":56,"command":57},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill benchmarking-kubernetes-with-kube-bench","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbenchmarking-kubernetes-with-kube-bench\u002FSKILL.md",true,[61,65,71,75],{"path":62,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fapi-reference.md","REFERENCE","参考文档",2969,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbenchmarking-kubernetes-with-kube-bench\u002Freferences\u002Fapi-reference.md",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fstandards.md",1650,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbenchmarking-kubernetes-with-kube-bench\u002Freferences\u002Fstandards.md",{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"scripts\u002Fagent.py","SCRIPT","脚本",5717,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbenchmarking-kubernetes-with-kube-bench\u002Fscripts\u002Fagent.py",[82,89,96,103,110,117],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"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":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},"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":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},"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":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},"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",[],[]]