[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7349Q92CXJMMDZ2AFZ2XQDD":3,"skill-same:01M7349Q92CXJMMDZ2AFZ2XQDD":105},{"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":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M7349Q92CXJMMDZ2AFZ2XQDD","implementing-kubernetes-pod-security-standards",null,"Pod Security Standards (PSS) define three levels of security policies -- Privileged, Baseline, and Restricted -- enforced by the Pod Security Admission (PSA) controller built into Kubernetes 1.25+. PS","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-kubernetes-pod-security-standards\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-kubernetes-pod-security-standards\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: implementing-kubernetes-pod-security-standards\ndescription: Pod Security Standards (PSS) define three levels of security policies\n  -- Privileged, Baseline, and Restricted -- enforced by the Pod Security Admission\n  (PSA) controller built into Kubernetes 1.25+. PS\ndomain: cybersecurity\nsubdomain: container-security\ntags:\n- containers\n- kubernetes\n- security\n- pod-security\n- PSA\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\nsource: https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\nsource_commit: 04450304b12645cb2b974ab96d28c0664758a88d\n---\n# Implementing Kubernetes Pod Security Standards\n\n## Overview\n\nPod Security Standards (PSS) define three levels of security policies -- Privileged, Baseline, and Restricted -- enforced by the Pod Security Admission (PSA) controller built into Kubernetes 1.25+. PSA replaces the deprecated PodSecurityPolicy and provides namespace-level enforcement with three modes: enforce, audit, and warn.\n\n\n## When to Use\n\n- When deploying or configuring implementing kubernetes pod security standards 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\n- Kubernetes cluster 1.25+ (PSA GA)\n- kubectl configured with cluster-admin access\n- Understanding of Linux capabilities and security contexts\n\n## Core Concepts\n\n### Three Security Profiles\n\n| Profile | Purpose | Restrictions |\n|---------|---------|-------------|\n| **Privileged** | Unrestricted, system workloads | None |\n| **Baseline** | Prevents known escalations | No hostNetwork, hostPID, hostIPC, privileged containers, dangerous capabilities |\n| **Restricted** | Hardened best practices | Non-root, drop ALL caps, seccomp required, read-only rootfs recommended |\n\n### Three Enforcement Modes\n\n| Mode | Behavior |\n|------|----------|\n| **enforce** | Rejects pods that violate the policy |\n| **audit** | Logs violations in audit log but allows pod |\n| **warn** | Returns warning to user but allows pod |\n\n## Workflow\n\n### Step 1: Label Namespaces for PSA\n\n```yaml\n# Restricted namespace - production workloads\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: production\n  labels:\n    pod-security.kubernetes.io\u002Fenforce: restricted\n    pod-security.kubernetes.io\u002Fenforce-version: latest\n    pod-security.kubernetes.io\u002Faudit: restricted\n    pod-security.kubernetes.io\u002Faudit-version: latest\n    pod-security.kubernetes.io\u002Fwarn: restricted\n    pod-security.kubernetes.io\u002Fwarn-version: latest\n```\n\n```yaml\n# Baseline namespace - general workloads\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: staging\n  labels:\n    pod-security.kubernetes.io\u002Fenforce: baseline\n    pod-security.kubernetes.io\u002Fenforce-version: latest\n    pod-security.kubernetes.io\u002Faudit: restricted\n    pod-security.kubernetes.io\u002Faudit-version: latest\n    pod-security.kubernetes.io\u002Fwarn: restricted\n    pod-security.kubernetes.io\u002Fwarn-version: latest\n```\n\n```yaml\n# Privileged namespace - system components only\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: kube-system\n  labels:\n    pod-security.kubernetes.io\u002Fenforce: privileged\n    pod-security.kubernetes.io\u002Fenforce-version: latest\n```\n\n### Step 2: Apply Labels to Existing Namespaces\n\n```bash\n# Apply restricted enforcement to production\nkubectl label namespace production \\\n  pod-security.kubernetes.io\u002Fenforce=restricted \\\n  pod-security.kubernetes.io\u002Faudit=restricted \\\n  pod-security.kubernetes.io\u002Fwarn=restricted \\\n  --overwrite\n\n# Apply baseline to staging with restricted warnings\nkubectl label namespace staging \\\n  pod-security.kubernetes.io\u002Fenforce=baseline \\\n  pod-security.kubernetes.io\u002Faudit=restricted \\\n  pod-security.kubernetes.io\u002Fwarn=restricted \\\n  --overwrite\n\n# Check labels on all namespaces\nkubectl get namespaces -L pod-security.kubernetes.io\u002Fenforce\n```\n\n### Step 3: Create Compliant Pod Specs\n\n```yaml\n# Restricted-compliant deployment\napiVersion: apps\u002Fv1\nkind: Deployment\nmetadata:\n  name: secure-app\n  namespace: production\nspec:\n  replicas: 3\n  selector:\n    matchLabels:\n      app: secure-app\n  template:\n    metadata:\n      labels:\n        app: secure-app\n    spec:\n      automountServiceAccountToken: false\n      securityContext:\n        runAsNonRoot: true\n        runAsUser: 65534\n        runAsGroup: 65534\n        fsGroup: 65534\n        seccompProfile:\n          type: RuntimeDefault\n      containers:\n        - name: app\n          image: myregistry.com\u002Fmyapp:v1.0.0@sha256:abc123\n          ports:\n            - containerPort: 8080\n              protocol: TCP\n          securityContext:\n            allowPrivilegeEscalation: false\n            readOnlyRootFilesystem: true\n            capabilities:\n              drop:\n                - ALL\n            runAsNonRoot: true\n            runAsUser: 65534\n          resources:\n            requests:\n              memory: \"64Mi\"\n              cpu: \"100m\"\n            limits:\n              memory: \"256Mi\"\n              cpu: \"500m\"\n          volumeMounts:\n            - name: tmp\n              mountPath: \u002Ftmp\n            - name: cache\n              mountPath: \u002Fvar\u002Fcache\n      volumes:\n        - name: tmp\n          emptyDir:\n            sizeLimit: 100Mi\n        - name: cache\n          emptyDir:\n            sizeLimit: 50Mi\n```\n\n### Step 4: Gradual Migration Strategy\n\n```bash\n# Phase 1: Audit mode - discover violations without blocking\nkubectl label namespace my-namespace \\\n  pod-security.kubernetes.io\u002Faudit=restricted \\\n  pod-security.kubernetes.io\u002Fwarn=restricted\n\n# Check audit logs for violations\nkubectl logs -n kube-system -l component=kube-apiserver | grep \"pod-security\"\n\n# Phase 2: Enforce baseline, warn on restricted\nkubectl label namespace my-namespace \\\n  pod-security.kubernetes.io\u002Fenforce=baseline \\\n  pod-security.kubernetes.io\u002Fwarn=restricted \\\n  --overwrite\n\n# Phase 3: Full restricted enforcement\nkubectl label namespace my-namespace \\\n  pod-security.kubernetes.io\u002Fenforce=restricted \\\n  --overwrite\n```\n\n### Step 5: Dry-Run Enforcement Testing\n\n```bash\n# Test what would happen with restricted enforcement\nkubectl label --dry-run=server --overwrite namespace my-namespace \\\n  pod-security.kubernetes.io\u002Fenforce=restricted\n\n# Example output:\n# Warning: existing pods in namespace \"my-namespace\" violate the new\n# PodSecurity enforce level \"restricted:latest\"\n# Warning: nginx-xxx: allowPrivilegeEscalation != false,\n#   unrestricted capabilities, runAsNonRoot != true, seccompProfile\n```\n\n## Baseline Profile Restrictions\n\n| Control | Restricted | Requirement |\n|---------|-----------|-------------|\n| HostProcess | Must not set | Pods cannot use Windows HostProcess |\n| Host Namespaces | Must not set | No hostNetwork, hostPID, hostIPC |\n| Privileged | Must not set | No privileged: true |\n| Capabilities | Baseline list only | Only NET_BIND_SERVICE, drop ALL for restricted |\n| HostPath Volumes | Must not use | No hostPath volume mounts |\n| Host Ports | Must not use | No hostPort in container spec |\n| AppArmor | Default\u002Fruntime | Cannot set to unconfined |\n| SELinux | Limited types | Only container_t, container_init_t, container_kvm_t |\n| \u002Fproc Mount Type | Default only | Must use Default proc mount |\n| Seccomp | RuntimeDefault or Localhost | Must specify seccomp profile (restricted) |\n| Sysctls | Safe set only | Limited to safe sysctls |\n\n## Validation Commands\n\n```bash\n# Verify namespace labels\nkubectl get ns --show-labels | grep pod-security\n\n# Test pod creation against policy\nkubectl run test-pod --image=nginx --namespace=production --dry-run=server\n\n# Check for violations in audit logs\nkubectl get events --field-selector reason=FailedCreate -A\n\n# Scan with Kubescape for PSS compliance\nkubescape scan framework nsa --namespace production\n```\n\n## References\n\n- [Pod Security Standards - Kubernetes](https:\u002F\u002Fkubernetes.io\u002Fdocs\u002Fconcepts\u002Fsecurity\u002Fpod-security-standards\u002F)\n- [Pod Security Admission - Kubernetes](https:\u002F\u002Fkubernetes.io\u002Fdocs\u002Fconcepts\u002Fsecurity\u002Fpod-security-admission\u002F)\n- [Migrate from PodSecurityPolicy](https:\u002F\u002Fkubernetes.io\u002Fdocs\u002Ftasks\u002Fconfigure-pod-container\u002Fmigrate-from-psp\u002F)\n- [Kubescape PSS Scanner](https:\u002F\u002Fgithub.com\u002Fkubescape\u002Fkubescape)\n","# Implementing Kubernetes Pod Security Standards\n\n## Overview\n\nPod Security Standards (PSS) define three levels of security policies -- Privileged, Baseline, and Restricted -- enforced by the Pod Security Admission (PSA) controller built into Kubernetes 1.25+. PSA replaces the deprecated PodSecurityPolicy and provides namespace-level enforcement with three modes: enforce, audit, and warn.\n\n\n## When to Use\n\n- When deploying or configuring implementing kubernetes pod security standards 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\n- Kubernetes cluster 1.25+ (PSA GA)\n- kubectl configured with cluster-admin access\n- Understanding of Linux capabilities and security contexts\n\n## Core Concepts\n\n### Three Security Profiles\n\n| Profile | Purpose | Restrictions |\n|---------|---------|-------------|\n| **Privileged** | Unrestricted, system workloads | None |\n| **Baseline** | Prevents known escalations | No hostNetwork, hostPID, hostIPC, privileged containers, dangerous capabilities |\n| **Restricted** | Hardened best practices | Non-root, drop ALL caps, seccomp required, read-only rootfs recommended |\n\n### Three Enforcement Modes\n\n| Mode | Behavior |\n|------|----------|\n| **enforce** | Rejects pods that violate the policy |\n| **audit** | Logs violations in audit log but allows pod |\n| **warn** | Returns warning to user but allows pod |\n\n## Workflow\n\n### Step 1: Label Namespaces for PSA\n\n```yaml\n# Restricted namespace - production workloads\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: production\n  labels:\n    pod-security.kubernetes.io\u002Fenforce: restricted\n    pod-security.kubernetes.io\u002Fenforce-version: latest\n    pod-security.kubernetes.io\u002Faudit: restricted\n    pod-security.kubernetes.io\u002Faudit-version: latest\n    pod-security.kubernetes.io\u002Fwarn: restricted\n    pod-security.kubernetes.io\u002Fwarn-version: latest\n```\n\n```yaml\n# Baseline namespace - general workloads\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: staging\n  labels:\n    pod-security.kubernetes.io\u002Fenforce: baseline\n    pod-security.kubernetes.io\u002Fenforce-version: latest\n    pod-security.kubernetes.io\u002Faudit: restricted\n    pod-security.kubernetes.io\u002Faudit-version: latest\n    pod-security.kubernetes.io\u002Fwarn: restricted\n    pod-security.kubernetes.io\u002Fwarn-version: latest\n```\n\n```yaml\n# Privileged namespace - system components only\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: kube-system\n  labels:\n    pod-security.kubernetes.io\u002Fenforce: privileged\n    pod-security.kubernetes.io\u002Fenforce-version: latest\n```\n\n### Step 2: Apply Labels to Existing Namespaces\n\n```bash\n# Apply restricted enforcement to production\nkubectl label namespace production \\\n  pod-security.kubernetes.io\u002Fenforce=restricted \\\n  pod-security.kubernetes.io\u002Faudit=restricted \\\n  pod-security.kubernetes.io\u002Fwarn=restricted \\\n  --overwrite\n\n# Apply baseline to staging with restricted warnings\nkubectl label namespace staging \\\n  pod-security.kubernetes.io\u002Fenforce=baseline \\\n  pod-security.kubernetes.io\u002Faudit=restricted \\\n  pod-security.kubernetes.io\u002Fwarn=restricted \\\n  --overwrite\n\n# Check labels on all namespaces\nkubectl get namespaces -L pod-security.kubernetes.io\u002Fenforce\n```\n\n### Step 3: Create Compliant Pod Specs\n\n```yaml\n# Restricted-compliant deployment\napiVersion: apps\u002Fv1\nkind: Deployment\nmetadata:\n  name: secure-app\n  namespace: production\nspec:\n  replicas: 3\n  selector:\n    matchLabels:\n      app: secure-app\n  template:\n    metadata:\n      labels:\n        app: secure-app\n    spec:\n      automountServiceAccountToken: false\n      securityContext:\n        runAsNonRoot: true\n        runAsUser: 65534\n        runAsGroup: 65534\n        fsGroup: 65534\n        seccompProfile:\n          type: RuntimeDefault\n      containers:\n        - name: app\n          image: myregistry.com\u002Fmyapp:v1.0.0@sha256:abc123\n          ports:\n            - containerPort: 8080\n              protocol: TCP\n          securityContext:\n            allowPrivilegeEscalation: false\n            readOnlyRootFilesystem: true\n            capabilities:\n              drop:\n                - ALL\n            runAsNonRoot: true\n            runAsUser: 65534\n          resources:\n            requests:\n              memory: \"64Mi\"\n              cpu: \"100m\"\n            limits:\n              memory: \"256Mi\"\n              cpu: \"500m\"\n          volumeMounts:\n            - name: tmp\n              mountPath: \u002Ftmp\n            - name: cache\n              mountPath: \u002Fvar\u002Fcache\n      volumes:\n        - name: tmp\n          emptyDir:\n            sizeLimit: 100Mi\n        - name: cache\n          emptyDir:\n            sizeLimit: 50Mi\n```\n\n### Step 4: Gradual Migration Strategy\n\n```bash\n# Phase 1: Audit mode - discover violations without blocking\nkubectl label namespace my-namespace \\\n  pod-security.kubernetes.io\u002Faudit=restricted \\\n  pod-security.kubernetes.io\u002Fwarn=restricted\n\n# Check audit logs for violations\nkubectl logs -n kube-system -l component=kube-apiserver | grep \"pod-security\"\n\n# Phase 2: Enforce baseline, warn on restricted\nkubectl label namespace my-namespace \\\n  pod-security.kubernetes.io\u002Fenforce=baseline \\\n  pod-security.kubernetes.io\u002Fwarn=restricted \\\n  --overwrite\n\n# Phase 3: Full restricted enforcement\nkubectl label namespace my-namespace \\\n  pod-security.kubernetes.io\u002Fenforce=restricted \\\n  --overwrite\n```\n\n### Step 5: Dry-Run Enforcement Testing\n\n```bash\n# Test what would happen with restricted enforcement\nkubectl label --dry-run=server --overwrite namespace my-namespace \\\n  pod-security.kubernetes.io\u002Fenforce=restricted\n\n# Example output:\n# Warning: existing pods in namespace \"my-namespace\" violate the new\n# PodSecurity enforce level \"restricted:latest\"\n# Warning: nginx-xxx: allowPrivilegeEscalation != false,\n#   unrestricted capabilities, runAsNonRoot != true, seccompProfile\n```\n\n## Baseline Profile Restrictions\n\n| Control | Restricted | Requirement |\n|---------|-----------|-------------|\n| HostProcess | Must not set | Pods cannot use Windows HostProcess |\n| Host Namespaces | Must not set | No hostNetwork, hostPID, hostIPC |\n| Privileged | Must not set | No privileged: true |\n| Capabilities | Baseline list only | Only NET_BIND_SERVICE, drop ALL for restricted |\n| HostPath Volumes | Must not use | No hostPath volume mounts |\n| Host Ports | Must not use | No hostPort in container spec |\n| AppArmor | Default\u002Fruntime | Cannot set to unconfined |\n| SELinux | Limited types | Only container_t, container_init_t, container_kvm_t |\n| \u002Fproc Mount Type | Default only | Must use Default proc mount |\n| Seccomp | RuntimeDefault or Localhost | Must specify seccomp profile (restricted) |\n| Sysctls | Safe set only | Limited to safe sysctls |\n\n## Validation Commands\n\n```bash\n# Verify namespace labels\nkubectl get ns --show-labels | grep pod-security\n\n# Test pod creation against policy\nkubectl run test-pod --image=nginx --namespace=production --dry-run=server\n\n# Check for violations in audit logs\nkubectl get events --field-selector reason=FailedCreate -A\n\n# Scan with Kubescape for PSS compliance\nkubescape scan framework nsa --namespace production\n```\n\n## References\n\n- [Pod Security Standards - Kubernetes](https:\u002F\u002Fkubernetes.io\u002Fdocs\u002Fconcepts\u002Fsecurity\u002Fpod-security-standards\u002F)\n- [Pod Security Admission - Kubernetes](https:\u002F\u002Fkubernetes.io\u002Fdocs\u002Fconcepts\u002Fsecurity\u002Fpod-security-admission\u002F)\n- [Migrate from PodSecurityPolicy](https:\u002F\u002Fkubernetes.io\u002Fdocs\u002Ftasks\u002Fconfigure-pod-container\u002Fmigrate-from-psp\u002F)\n- [Kubescape PSS Scanner](https:\u002F\u002Fgithub.com\u002Fkubescape\u002Fkubescape)\n",{"name":5,"tags":25,"author":31,"domain":32,"source":33,"license":15,"version":34,"nist_csf":35,"subdomain":40,"description":7,"mitre_attack":41,"source_commit":46},[26,27,28,29,30],"containers","kubernetes","security","pod-security","PSA","mahipal","cybersecurity","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","1.0",[36,37,38,39],"PR.PS-01","PR.IR-01","ID.AM-08","DE.CM-01","container-security",[42,43,44,45],"T1610","T1611","T1609","T1525","04450304b12645cb2b974ab96d28c0664758a88d","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa",".claude\u002Fskills\u002Fimplementing-kubernetes-pod-security-standards",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-14 13:24:09",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill implementing-kubernetes-pod-security-standards",{"tool":63,"command":64},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill implementing-kubernetes-pod-security-standards",{"tool":66,"command":67},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill implementing-kubernetes-pod-security-standards","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-kubernetes-pod-security-standards\u002FSKILL.md",true,[71,77,81,87,91,95,101],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"assets\u002Ftemplate.md","ASSET","资产文件",1681,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-kubernetes-pod-security-standards\u002Fassets\u002Ftemplate.md",{"path":78,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fapi-reference.md","REFERENCE","参考文档",1575,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-kubernetes-pod-security-standards\u002Freferences\u002Fapi-reference.md",{"path":88,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fstandards.md",3276,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-kubernetes-pod-security-standards\u002Freferences\u002Fstandards.md",{"path":92,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fworkflows.md",3701,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-kubernetes-pod-security-standards\u002Freferences\u002Fworkflows.md",{"path":96,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":99,"sourceHtmlUrl":100},"scripts\u002Fagent.py","SCRIPT","脚本",7680,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-kubernetes-pod-security-standards\u002Fscripts\u002Fagent.py",{"path":102,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":103,"sourceHtmlUrl":104},"scripts\u002Fprocess.py",11335,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-kubernetes-pod-security-standards\u002Fscripts\u002Fprocess.py",[106,114,121,129,137,145],{"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":110,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":20},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":20},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":125,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":20},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":133,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":20},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\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":141,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":20},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":146,"name":147,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":20},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]