[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ES5VY7YYR92EH37NTBKHWD":3,"skill-same:01M7ES5VY7YYR92EH37NTBKHWD":84},{"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":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M7ES5VY7YYR92EH37NTBKHWD","scanning-kubernetes-manifests-with-kubesec",null,"Scores Kubernetes resource manifests with Kubesec to flag misconfiguration and privilege-escalation risk before deployment, mapping each finding back to the securityContext change that fixes it. Use when gating manifests in CI, reviewing YAML or a rendered chart before it reaches a cluster, or explaining why a manifest scored negatively. Keywords: Kubesec, manifest score, securityContext, readOnlyRootFilesystem, runAsNonRoot, CI gate. Do not use for scanning built images for CVEs - use scanning-docker-images-with-trivy; for admission-time enforcement use implementing-opa-gatekeeper-for-policy-enforcement.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fscanning-kubernetes-manifests-with-kubesec\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: scanning-kubernetes-manifests-with-kubesec\ndescription: >-\n  Scores Kubernetes resource manifests with Kubesec to flag misconfiguration and\n  privilege-escalation risk before deployment, mapping each finding back to the\n  securityContext change that fixes it. Use when gating manifests in CI, reviewing YAML or a\n  rendered chart before it reaches a cluster, or explaining why a manifest scored negatively.\n  Keywords: Kubesec, manifest score, securityContext, readOnlyRootFilesystem, runAsNonRoot, CI\n  gate. Do not use for scanning built images for CVEs - use scanning-docker-images-with-trivy;\n  for admission-time enforcement use implementing-opa-gatekeeper-for-policy-enforcement.\ndomain: cybersecurity\nsubdomain: container-security\ntags:\n- kubesec\n- kubernetes\n- manifest-scanning\n- security-scanning\n- devsecops\n- misconfiguration\n- static-analysis\n- ci-cd\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- PR.IR-01\n- ID.AM-08\n- DE.CM-01\nmitre_attack:\n- T1610\n- T1611\n- T1609\n- T1525\n- T1068\n---\n\n# Scanning Kubernetes Manifests with Kubesec\n\n## Overview\n\nKubesec is an open-source security risk analysis tool developed by ControlPlane that inspects Kubernetes resource manifests for common exploitable risks such as privilege escalation, writable host mounts, and excessive capabilities. It assigns a numerical security score to each resource and provides actionable recommendations for hardening. Kubesec can be used as a CLI binary, Docker container, kubectl plugin, admission webhook, or REST API endpoint.\n\n\n## When to Use\n\n- When conducting security assessments that involve scanning kubernetes manifests with kubesec\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\n- Kubernetes manifest files (YAML\u002FJSON) for Deployments, Pods, DaemonSets, StatefulSets\n- Docker or Go runtime for local installation\n- kubectl access for scanning live cluster resources\n- CI\u002FCD pipeline access for automated scanning integration\n\n## Core Concepts\n\n### Security Scoring System\n\nKubesec assigns a score to each Kubernetes resource based on security checks:\n\n- **Positive scores**: Awarded for security-enhancing configurations (readOnlyRootFilesystem, runAsNonRoot)\n- **Zero or negative scores**: Indicate missing security controls or dangerous configurations\n- **Critical advisories**: Flagged configurations that represent immediate security risks\n\n### Check Categories\n\n1. **Privilege Controls**: Checks for privileged containers, host PID\u002Fnetwork access, root execution\n2. **Capabilities**: Identifies excessive Linux capabilities (SYS_ADMIN, NET_RAW)\n3. **Volume Mounts**: Detects dangerous host path mounts and writable sensitive paths\n4. **Resource Limits**: Validates presence of CPU\u002Fmemory resource constraints\n5. **Security Context**: Verifies seccomp profiles, AppArmor annotations, SELinux contexts\n\n## Installation\n\n### Binary Installation\n\n```bash\n# Linux\u002FmacOS\ncurl -sSL https:\u002F\u002Fgithub.com\u002Fcontrolplaneio\u002Fkubesec\u002Freleases\u002Flatest\u002Fdownload\u002Fkubesec_linux_amd64.tar.gz | \\\n  tar xz -C \u002Fusr\u002Flocal\u002Fbin\u002F kubesec\n\n# Verify installation\nkubesec version\n```\n\n### Docker Installation\n\n```bash\ndocker pull kubesec\u002Fkubesec:v2\n\n# Scan a manifest file\ndocker run -i kubesec\u002Fkubesec:v2 scan \u002Fdev\u002Fstdin \u003C deployment.yaml\n```\n\n### kubectl Plugin\n\n```bash\nkubectl krew install kubesec-scan\nkubectl kubesec-scan pod mypod -n default\n```\n\n## Practical Scanning\n\n### Scanning a Single Manifest\n\n```bash\n# Scan a deployment manifest\nkubesec scan deployment.yaml\n\n# Scan with JSON output\nkubesec scan -o json deployment.yaml\n\n# Scan from stdin\ncat pod.yaml | kubesec scan -\n```\n\n### Sample Output\n\n```json\n[\n  {\n    \"object\": \"Pod\u002Fweb-app.default\",\n    \"valid\": true,\n    \"fileName\": \"pod.yaml\",\n    \"message\": \"Passed with a score of 3 points\",\n    \"score\": 3,\n    \"scoring\": {\n      \"passed\": [\n        {\n          \"id\": \"ReadOnlyRootFilesystem\",\n          \"selector\": \"containers[] .securityContext .readOnlyRootFilesystem == true\",\n          \"reason\": \"An immutable root filesystem prevents applications from writing to their local disk\",\n          \"points\": 1\n        },\n        {\n          \"id\": \"RunAsNonRoot\",\n          \"selector\": \"containers[] .securityContext .runAsNonRoot == true\",\n          \"reason\": \"Force the running image to run as a non-root user\",\n          \"points\": 1\n        },\n        {\n          \"id\": \"LimitsCPU\",\n          \"selector\": \"containers[] .resources .limits .cpu\",\n          \"reason\": \"Enforcing CPU limits prevents DOS via resource exhaustion\",\n          \"points\": 1\n        }\n      ],\n      \"advise\": [\n        {\n          \"id\": \"ApparmorAny\",\n          \"selector\": \"metadata .annotations .\\\"container.apparmor.security.beta.kubernetes.io\u002Fnginx\\\"\",\n          \"reason\": \"Well defined AppArmor policies reduce the attack surface of the container\",\n          \"points\": 3\n        },\n        {\n          \"id\": \"ServiceAccountName\",\n          \"selector\": \".spec .serviceAccountName\",\n          \"reason\": \"Service accounts restrict Kubernetes API access and should be configured\",\n          \"points\": 3\n        }\n      ]\n    }\n  }\n]\n```\n\n### Scanning Multiple Resources\n\n```bash\n# Scan all YAML files in a directory\nfor file in manifests\u002F*.yaml; do\n  echo \"=== Scanning $file ===\"\n  kubesec scan \"$file\"\ndone\n\n# Scan multi-document YAML\nkubesec scan multi-resource.yaml\n```\n\n### Using the HTTP API\n\n```bash\n# Scan via the public API\ncurl -sSX POST --data-binary @deployment.yaml \\\n  https:\u002F\u002Fv2.kubesec.io\u002Fscan\n\n# Run a local API server\nkubesec http --port 8080 &\n\n# Scan against local server\ncurl -sSX POST --data-binary @deployment.yaml \\\n  http:\u002F\u002Flocalhost:8080\u002Fscan\n```\n\n## CI\u002FCD Integration\n\n### GitHub Actions\n\n```yaml\nname: Kubesec Scan\non: [pull_request]\njobs:\n  kubesec:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - name: Install Kubesec\n        run: |\n          curl -sSL https:\u002F\u002Fgithub.com\u002Fcontrolplaneio\u002Fkubesec\u002Freleases\u002Flatest\u002Fdownload\u002Fkubesec_linux_amd64.tar.gz | \\\n            tar xz -C \u002Fusr\u002Flocal\u002Fbin\u002F kubesec\n      - name: Scan Manifests\n        run: |\n          FAIL=0\n          for file in k8s\u002F*.yaml; do\n            SCORE=$(kubesec scan \"$file\" | jq '.[0].score')\n            echo \"$file: score=$SCORE\"\n            if [ \"$SCORE\" -lt 0 ]; then\n              echo \"FAIL: $file has critical issues (score: $SCORE)\"\n              FAIL=1\n            fi\n          done\n          exit $FAIL\n```\n\n### GitLab CI\n\n```yaml\nkubesec-scan:\n  stage: security\n  image: kubesec\u002Fkubesec:v2\n  script:\n    - |\n      for file in k8s\u002F*.yaml; do\n        kubesec scan \"$file\" > \u002Ftmp\u002Fresult.json\n        SCORE=$(cat \u002Ftmp\u002Fresult.json | jq '.[0].score')\n        if [ \"$SCORE\" -lt 0 ]; then\n          echo \"CRITICAL: $file scored $SCORE\"\n          cat \u002Ftmp\u002Fresult.json | jq '.[0].scoring.critical'\n          exit 1\n        fi\n      done\n  artifacts:\n    paths:\n      - kubesec-results\u002F\n```\n\n### Admission Webhook\n\nDeploy Kubesec as a ValidatingWebhookConfiguration to reject insecure manifests at deploy time:\n\n```yaml\napiVersion: admissionregistration.k8s.io\u002Fv1\nkind: ValidatingWebhookConfiguration\nmetadata:\n  name: kubesec-webhook\nwebhooks:\n  - name: kubesec.controlplane.io\n    rules:\n      - apiGroups: [\"\"]\n        apiVersions: [\"v1\"]\n        operations: [\"CREATE\", \"UPDATE\"]\n        resources: [\"pods\"]\n      - apiGroups: [\"apps\"]\n        apiVersions: [\"v1\"]\n        operations: [\"CREATE\", \"UPDATE\"]\n        resources: [\"deployments\", \"daemonsets\", \"statefulsets\"]\n    clientConfig:\n      service:\n        name: kubesec-webhook\n        namespace: kube-system\n        path: \u002Fscan\n    failurePolicy: Fail\n    sideEffects: None\n    admissionReviewVersions: [\"v1\"]\n```\n\n## Security Checks Reference\n\n### Critical Checks (Negative Score)\n\n| Check | Selector | Risk |\n|-------|----------|------|\n| Privileged | `securityContext.privileged == true` | Full host access |\n| HostPID | `spec.hostPID == true` | Process namespace escape |\n| HostNetwork | `spec.hostNetwork == true` | Network namespace escape |\n| SYS_ADMIN | `capabilities.add contains SYS_ADMIN` | Near-root capability |\n\n### Best Practice Checks (Positive Score)\n\n| Check | Points | Description |\n|-------|--------|-------------|\n| ReadOnlyRootFilesystem | +1 | Prevents filesystem writes |\n| RunAsNonRoot | +1 | Non-root process execution |\n| RunAsUser > 10000 | +1 | High UID reduces collision risk |\n| LimitsCPU | +1 | Prevents CPU resource exhaustion |\n| LimitsMemory | +1 | Prevents memory resource exhaustion |\n| RequestsCPU | +1 | Ensures scheduler resource awareness |\n| ServiceAccountName | +3 | Explicit service account |\n| AppArmor annotation | +3 | Kernel-level MAC enforcement |\n| Seccomp profile | +4 | Syscall filtering |\n\n## References\n\n- [Kubesec GitHub Repository](https:\u002F\u002Fgithub.com\u002Fcontrolplaneio\u002Fkubesec)\n- [Kubesec Online Scanner](https:\u002F\u002Fkubesec.io\u002F)\n- [ControlPlane Security Tools](https:\u002F\u002Fcontrolplane.io\u002F)\n- [CIS Kubernetes Benchmark](https:\u002F\u002Fwww.cisecurity.org\u002Fbenchmark\u002Fkubernetes)\n- [Kubernetes Pod Security Standards](https:\u002F\u002Fkubernetes.io\u002Fdocs\u002Fconcepts\u002Fsecurity\u002Fpod-security-standards\u002F)\n","# Scanning Kubernetes Manifests with Kubesec\n\n## Overview\n\nKubesec is an open-source security risk analysis tool developed by ControlPlane that inspects Kubernetes resource manifests for common exploitable risks such as privilege escalation, writable host mounts, and excessive capabilities. It assigns a numerical security score to each resource and provides actionable recommendations for hardening. Kubesec can be used as a CLI binary, Docker container, kubectl plugin, admission webhook, or REST API endpoint.\n\n\n## When to Use\n\n- When conducting security assessments that involve scanning kubernetes manifests with kubesec\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\n- Kubernetes manifest files (YAML\u002FJSON) for Deployments, Pods, DaemonSets, StatefulSets\n- Docker or Go runtime for local installation\n- kubectl access for scanning live cluster resources\n- CI\u002FCD pipeline access for automated scanning integration\n\n## Core Concepts\n\n### Security Scoring System\n\nKubesec assigns a score to each Kubernetes resource based on security checks:\n\n- **Positive scores**: Awarded for security-enhancing configurations (readOnlyRootFilesystem, runAsNonRoot)\n- **Zero or negative scores**: Indicate missing security controls or dangerous configurations\n- **Critical advisories**: Flagged configurations that represent immediate security risks\n\n### Check Categories\n\n1. **Privilege Controls**: Checks for privileged containers, host PID\u002Fnetwork access, root execution\n2. **Capabilities**: Identifies excessive Linux capabilities (SYS_ADMIN, NET_RAW)\n3. **Volume Mounts**: Detects dangerous host path mounts and writable sensitive paths\n4. **Resource Limits**: Validates presence of CPU\u002Fmemory resource constraints\n5. **Security Context**: Verifies seccomp profiles, AppArmor annotations, SELinux contexts\n\n## Installation\n\n### Binary Installation\n\n```bash\n# Linux\u002FmacOS\ncurl -sSL https:\u002F\u002Fgithub.com\u002Fcontrolplaneio\u002Fkubesec\u002Freleases\u002Flatest\u002Fdownload\u002Fkubesec_linux_amd64.tar.gz | \\\n  tar xz -C \u002Fusr\u002Flocal\u002Fbin\u002F kubesec\n\n# Verify installation\nkubesec version\n```\n\n### Docker Installation\n\n```bash\ndocker pull kubesec\u002Fkubesec:v2\n\n# Scan a manifest file\ndocker run -i kubesec\u002Fkubesec:v2 scan \u002Fdev\u002Fstdin \u003C deployment.yaml\n```\n\n### kubectl Plugin\n\n```bash\nkubectl krew install kubesec-scan\nkubectl kubesec-scan pod mypod -n default\n```\n\n## Practical Scanning\n\n### Scanning a Single Manifest\n\n```bash\n# Scan a deployment manifest\nkubesec scan deployment.yaml\n\n# Scan with JSON output\nkubesec scan -o json deployment.yaml\n\n# Scan from stdin\ncat pod.yaml | kubesec scan -\n```\n\n### Sample Output\n\n```json\n[\n  {\n    \"object\": \"Pod\u002Fweb-app.default\",\n    \"valid\": true,\n    \"fileName\": \"pod.yaml\",\n    \"message\": \"Passed with a score of 3 points\",\n    \"score\": 3,\n    \"scoring\": {\n      \"passed\": [\n        {\n          \"id\": \"ReadOnlyRootFilesystem\",\n          \"selector\": \"containers[] .securityContext .readOnlyRootFilesystem == true\",\n          \"reason\": \"An immutable root filesystem prevents applications from writing to their local disk\",\n          \"points\": 1\n        },\n        {\n          \"id\": \"RunAsNonRoot\",\n          \"selector\": \"containers[] .securityContext .runAsNonRoot == true\",\n          \"reason\": \"Force the running image to run as a non-root user\",\n          \"points\": 1\n        },\n        {\n          \"id\": \"LimitsCPU\",\n          \"selector\": \"containers[] .resources .limits .cpu\",\n          \"reason\": \"Enforcing CPU limits prevents DOS via resource exhaustion\",\n          \"points\": 1\n        }\n      ],\n      \"advise\": [\n        {\n          \"id\": \"ApparmorAny\",\n          \"selector\": \"metadata .annotations .\\\"container.apparmor.security.beta.kubernetes.io\u002Fnginx\\\"\",\n          \"reason\": \"Well defined AppArmor policies reduce the attack surface of the container\",\n          \"points\": 3\n        },\n        {\n          \"id\": \"ServiceAccountName\",\n          \"selector\": \".spec .serviceAccountName\",\n          \"reason\": \"Service accounts restrict Kubernetes API access and should be configured\",\n          \"points\": 3\n        }\n      ]\n    }\n  }\n]\n```\n\n### Scanning Multiple Resources\n\n```bash\n# Scan all YAML files in a directory\nfor file in manifests\u002F*.yaml; do\n  echo \"=== Scanning $file ===\"\n  kubesec scan \"$file\"\ndone\n\n# Scan multi-document YAML\nkubesec scan multi-resource.yaml\n```\n\n### Using the HTTP API\n\n```bash\n# Scan via the public API\ncurl -sSX POST --data-binary @deployment.yaml \\\n  https:\u002F\u002Fv2.kubesec.io\u002Fscan\n\n# Run a local API server\nkubesec http --port 8080 &\n\n# Scan against local server\ncurl -sSX POST --data-binary @deployment.yaml \\\n  http:\u002F\u002Flocalhost:8080\u002Fscan\n```\n\n## CI\u002FCD Integration\n\n### GitHub Actions\n\n```yaml\nname: Kubesec Scan\non: [pull_request]\njobs:\n  kubesec:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - name: Install Kubesec\n        run: |\n          curl -sSL https:\u002F\u002Fgithub.com\u002Fcontrolplaneio\u002Fkubesec\u002Freleases\u002Flatest\u002Fdownload\u002Fkubesec_linux_amd64.tar.gz | \\\n            tar xz -C \u002Fusr\u002Flocal\u002Fbin\u002F kubesec\n      - name: Scan Manifests\n        run: |\n          FAIL=0\n          for file in k8s\u002F*.yaml; do\n            SCORE=$(kubesec scan \"$file\" | jq '.[0].score')\n            echo \"$file: score=$SCORE\"\n            if [ \"$SCORE\" -lt 0 ]; then\n              echo \"FAIL: $file has critical issues (score: $SCORE)\"\n              FAIL=1\n            fi\n          done\n          exit $FAIL\n```\n\n### GitLab CI\n\n```yaml\nkubesec-scan:\n  stage: security\n  image: kubesec\u002Fkubesec:v2\n  script:\n    - |\n      for file in k8s\u002F*.yaml; do\n        kubesec scan \"$file\" > \u002Ftmp\u002Fresult.json\n        SCORE=$(cat \u002Ftmp\u002Fresult.json | jq '.[0].score')\n        if [ \"$SCORE\" -lt 0 ]; then\n          echo \"CRITICAL: $file scored $SCORE\"\n          cat \u002Ftmp\u002Fresult.json | jq '.[0].scoring.critical'\n          exit 1\n        fi\n      done\n  artifacts:\n    paths:\n      - kubesec-results\u002F\n```\n\n### Admission Webhook\n\nDeploy Kubesec as a ValidatingWebhookConfiguration to reject insecure manifests at deploy time:\n\n```yaml\napiVersion: admissionregistration.k8s.io\u002Fv1\nkind: ValidatingWebhookConfiguration\nmetadata:\n  name: kubesec-webhook\nwebhooks:\n  - name: kubesec.controlplane.io\n    rules:\n      - apiGroups: [\"\"]\n        apiVersions: [\"v1\"]\n        operations: [\"CREATE\", \"UPDATE\"]\n        resources: [\"pods\"]\n      - apiGroups: [\"apps\"]\n        apiVersions: [\"v1\"]\n        operations: [\"CREATE\", \"UPDATE\"]\n        resources: [\"deployments\", \"daemonsets\", \"statefulsets\"]\n    clientConfig:\n      service:\n        name: kubesec-webhook\n        namespace: kube-system\n        path: \u002Fscan\n    failurePolicy: Fail\n    sideEffects: None\n    admissionReviewVersions: [\"v1\"]\n```\n\n## Security Checks Reference\n\n### Critical Checks (Negative Score)\n\n| Check | Selector | Risk |\n|-------|----------|------|\n| Privileged | `securityContext.privileged == true` | Full host access |\n| HostPID | `spec.hostPID == true` | Process namespace escape |\n| HostNetwork | `spec.hostNetwork == true` | Network namespace escape |\n| SYS_ADMIN | `capabilities.add contains SYS_ADMIN` | Near-root capability |\n\n### Best Practice Checks (Positive Score)\n\n| Check | Points | Description |\n|-------|--------|-------------|\n| ReadOnlyRootFilesystem | +1 | Prevents filesystem writes |\n| RunAsNonRoot | +1 | Non-root process execution |\n| RunAsUser > 10000 | +1 | High UID reduces collision risk |\n| LimitsCPU | +1 | Prevents CPU resource exhaustion |\n| LimitsMemory | +1 | Prevents memory resource exhaustion |\n| RequestsCPU | +1 | Ensures scheduler resource awareness |\n| ServiceAccountName | +3 | Explicit service account |\n| AppArmor annotation | +3 | Kernel-level MAC enforcement |\n| Seccomp profile | +4 | Syscall filtering |\n\n## References\n\n- [Kubesec GitHub Repository](https:\u002F\u002Fgithub.com\u002Fcontrolplaneio\u002Fkubesec)\n- [Kubesec Online Scanner](https:\u002F\u002Fkubesec.io\u002F)\n- [ControlPlane Security Tools](https:\u002F\u002Fcontrolplane.io\u002F)\n- [CIS Kubernetes Benchmark](https:\u002F\u002Fwww.cisecurity.org\u002Fbenchmark\u002Fkubernetes)\n- [Kubernetes Pod Security Standards](https:\u002F\u002Fkubernetes.io\u002Fdocs\u002Fconcepts\u002Fsecurity\u002Fpod-security-standards\u002F)\n",{"name":5,"tags":24,"author":33,"domain":34,"license":15,"version":35,"nist_csf":36,"subdomain":41,"description":7,"mitre_attack":42},[25,26,27,28,29,30,31,32],"kubesec","kubernetes","manifest-scanning","security-scanning","devsecops","misconfiguration","static-analysis","ci-cd","mahipal","cybersecurity","1.0",[37,38,39,40],"PR.PS-01","PR.IR-01","ID.AM-08","DE.CM-01","container-security",[43,44,45,46,47],"T1610","T1611","T1609","T1525","T1068","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fscanning-kubernetes-manifests-with-kubesec",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill scanning-kubernetes-manifests-with-kubesec",{"tool":62,"command":63},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill scanning-kubernetes-manifests-with-kubesec",{"tool":65,"command":66},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill scanning-kubernetes-manifests-with-kubesec","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fscanning-kubernetes-manifests-with-kubesec\u002FSKILL.md",true,[70,76,80],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fapi-reference.md","REFERENCE","参考文档",1807,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fscanning-kubernetes-manifests-with-kubesec\u002Freferences\u002Fapi-reference.md",{"path":77,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fstandards.md",1875,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fscanning-kubernetes-manifests-with-kubesec\u002Freferences\u002Fstandards.md",{"path":81,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fworkflows.md",2088,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fscanning-kubernetes-manifests-with-kubesec\u002Freferences\u002Fworkflows.md",[85,94,99,106,113,120],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":93},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":95,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":93},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":93},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":93},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":93},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":93},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]