[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73CZGRGCZJZ9B91A3TD2KFS":3,"skill-same:01M73CZGRGCZJZ9B91A3TD2KFS":106},{"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":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M73CZGRGCZJZ9B91A3TD2KFS","implementing-pod-security-admission-controller",null,"Implement Kubernetes Pod Security Admission to enforce baseline and restricted security profiles at namespace level using built-in admission controller.","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\u002Fcore\u002Fskills\u002Fimplementing-pod-security-admission-controller\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fimplementing-pod-security-admission-controller\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: implementing-pod-security-admission-controller\ndescription: Implement Kubernetes Pod Security Admission to enforce baseline and restricted\n  security profiles at namespace level using built-in admission controller.\ndomain: cybersecurity\nsubdomain: container-security\ntags:\n- kubernetes\n- pod-security-admission\n- psa\n- pod-security-standards\n- admission-controller\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\nnote: \"Vendored verbatim from an external Apache-2.0 security-skill library, pinned by commit. Exceeds the internal 300-line skill guideline (agent-code-constraints.md) -- kept as-is because this is vendored reference material (forensics\u002Fthreat-intel procedure), not Yana AI-authored content, and trimming would damage technical accuracy.\"\n---\n\n# Implementing Pod Security Admission Controller\n\n## Overview\n\nPod Security Admission (PSA) is a built-in Kubernetes admission controller (stable since v1.25) that enforces Pod Security Standards at the namespace level. It replaces the deprecated PodSecurityPolicy (PSP) and provides three security profiles: Privileged, Baseline, and Restricted, with three enforcement modes: enforce, audit, and warn.\n\n\n## When to Use\n\n- When deploying or configuring implementing pod security admission controller 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 v1.25+ (PSA is stable\u002FGA)\n- kubectl with cluster-admin access\n- No dependency on external tools - PSA is built into kube-apiserver\n\n## Pod Security Standards\n\n### Privileged Profile\n- **Unrestricted** - No restrictions applied\n- Use case: System-level pods (kube-system, monitoring)\n\n### Baseline Profile\n- **Minimally restrictive** - Prevents known privilege escalation\n- Blocks: privileged containers, hostPID, hostIPC, hostNetwork, hostPorts, certain volume types, adding capabilities beyond runtime defaults\n\n### Restricted Profile\n- **Heavily restricted** - Follows security best practices\n- Requires: non-root, drop ALL capabilities, seccomp RuntimeDefault, read-only root filesystem considerations\n- Blocks: Everything in Baseline plus running as root, privilege escalation, non-approved volume types\n\n## Enforcement Modes\n\n| Mode | Behavior | Use Case |\n|------|----------|----------|\n| enforce | Reject pods violating policy | Production enforcement |\n| audit | Log violations to audit log | Pre-enforcement assessment |\n| warn | Show warnings to user | Developer feedback |\n\n## Implementation\n\n### Apply to Namespace via Labels\n\n```yaml\n# Restricted enforcement with audit and warn\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: production\n  labels:\n    pod-security.kubernetes.io\u002Fenforce: restricted\n    pod-security.kubernetes.io\u002Fenforce-version: v1.28\n    pod-security.kubernetes.io\u002Faudit: restricted\n    pod-security.kubernetes.io\u002Faudit-version: v1.28\n    pod-security.kubernetes.io\u002Fwarn: restricted\n    pod-security.kubernetes.io\u002Fwarn-version: v1.28\n```\n\n```yaml\n# Baseline enforcement for staging\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: staging\n  labels:\n    pod-security.kubernetes.io\u002Fenforce: baseline\n    pod-security.kubernetes.io\u002Fenforce-version: v1.28\n    pod-security.kubernetes.io\u002Faudit: restricted\n    pod-security.kubernetes.io\u002Faudit-version: v1.28\n    pod-security.kubernetes.io\u002Fwarn: restricted\n    pod-security.kubernetes.io\u002Fwarn-version: v1.28\n```\n\n```yaml\n# Privileged for system namespaces\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: kube-system\n  labels:\n    pod-security.kubernetes.io\u002Fenforce: privileged\n```\n\n### Apply Labels with kubectl\n\n```bash\n# Set restricted enforcement\nkubectl label namespace production \\\n  pod-security.kubernetes.io\u002Fenforce=restricted \\\n  pod-security.kubernetes.io\u002Fenforce-version=v1.28 \\\n  pod-security.kubernetes.io\u002Faudit=restricted \\\n  pod-security.kubernetes.io\u002Fwarn=restricted\n\n# Set baseline enforcement\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\n# Check current labels\nkubectl get namespace production -o jsonpath='{.metadata.labels}' | jq .\n```\n\n## Dry-Run Testing\n\n```bash\n# Test what would happen with restricted policy on a namespace\nkubectl label --dry-run=server --overwrite namespace staging \\\n  pod-security.kubernetes.io\u002Fenforce=restricted\n\n# Output shows existing pods that would violate the policy\n# Warning: existing pods in namespace \"staging\" violate the new PodSecurity enforce level \"restricted:latest\"\n```\n\n## Cluster-Wide Defaults (AdmissionConfiguration)\n\n```yaml\n# \u002Fetc\u002Fkubernetes\u002Fpsa-config.yaml\napiVersion: apiserver.config.k8s.io\u002Fv1\nkind: AdmissionConfiguration\nplugins:\n  - name: PodSecurity\n    configuration:\n      apiVersion: pod-security.admission.config.k8s.io\u002Fv1\n      kind: PodSecurityConfiguration\n      defaults:\n        enforce: baseline\n        enforce-version: latest\n        audit: restricted\n        audit-version: latest\n        warn: restricted\n        warn-version: latest\n      exemptions:\n        usernames: []\n        runtimeClasses: []\n        namespaces:\n          - kube-system\n          - kube-public\n          - kube-node-lease\n          - calico-system\n          - gatekeeper-system\n          - monitoring\n          - falco\n```\n\n### Apply to API Server\n\n```bash\n# Add to kube-apiserver manifests\n# \u002Fetc\u002Fkubernetes\u002Fmanifests\u002Fkube-apiserver.yaml\nspec:\n  containers:\n  - command:\n    - kube-apiserver\n    - --admission-control-config-file=\u002Fetc\u002Fkubernetes\u002Fpsa-config.yaml\n    volumeMounts:\n    - name: psa-config\n      mountPath: \u002Fetc\u002Fkubernetes\u002Fpsa-config.yaml\n      readOnly: true\n  volumes:\n  - name: psa-config\n    hostPath:\n      path: \u002Fetc\u002Fkubernetes\u002Fpsa-config.yaml\n      type: File\n```\n\n## Compliant Pod Examples\n\n### Restricted-Compliant Pod\n\n```yaml\napiVersion: v1\nkind: Pod\nmetadata:\n  name: restricted-pod\n  namespace: production\nspec:\n  securityContext:\n    runAsNonRoot: true\n    runAsUser: 1000\n    runAsGroup: 3000\n    fsGroup: 2000\n    seccompProfile:\n      type: RuntimeDefault\n  automountServiceAccountToken: false\n  containers:\n    - name: app\n      image: myregistry\u002Fmyapp:v1.0.0\n      securityContext:\n        allowPrivilegeEscalation: false\n        readOnlyRootFilesystem: true\n        capabilities:\n          drop:\n            - ALL\n      resources:\n        limits:\n          cpu: 500m\n          memory: 256Mi\n        requests:\n          cpu: 100m\n          memory: 128Mi\n      volumeMounts:\n        - name: tmp\n          mountPath: \u002Ftmp\n  volumes:\n    - name: tmp\n      emptyDir: {}\n```\n\n### Baseline-Compliant Pod\n\n```yaml\napiVersion: v1\nkind: Pod\nmetadata:\n  name: baseline-pod\n  namespace: staging\nspec:\n  containers:\n    - name: app\n      image: myregistry\u002Fmyapp:v1.0.0\n      securityContext:\n        allowPrivilegeEscalation: false\n      resources:\n        limits:\n          cpu: 500m\n          memory: 256Mi\n```\n\n## Migration from PodSecurityPolicy\n\n### Step 1: Audit Current State\n```bash\n# Check existing PSPs\nkubectl get psp\n\n# Check which service accounts use which PSP\nkubectl get clusterrolebinding -o json | \\\n  jq '.items[] | select(.roleRef.name | startswith(\"psp-\")) | {name: .metadata.name, subjects: .subjects}'\n```\n\n### Step 2: Map PSP to PSA Profiles\n```bash\n# For each namespace, determine required PSA level\nfor ns in $(kubectl get ns -o jsonpath='{.items[*].metadata.name}'); do\n  echo \"Namespace: $ns\"\n  kubectl label --dry-run=server namespace $ns \\\n    pod-security.kubernetes.io\u002Fenforce=restricted 2>&1 | head -5\ndone\n```\n\n### Step 3: Apply PSA Labels (Audit First)\n```bash\n# Start with audit mode\nkubectl label namespace production \\\n  pod-security.kubernetes.io\u002Faudit=restricted \\\n  pod-security.kubernetes.io\u002Fwarn=restricted\n```\n\n### Step 4: Review and Fix Violations\n```bash\n# Check audit logs for violations\nkubectl get events --field-selector reason=FailedCreate -A\n```\n\n### Step 5: Enable Enforcement\n```bash\nkubectl label namespace production \\\n  pod-security.kubernetes.io\u002Fenforce=restricted\n```\n\n## Monitoring\n\n```bash\n# Check PSA violations in events\nkubectl get events --all-namespaces --field-selector reason=FailedCreate\n\n# Check audit logs\nkubectl logs -n kube-system kube-apiserver-* | grep \"pod-security.kubernetes.io\"\n\n# List namespace PSA labels\nkubectl get namespaces -L pod-security.kubernetes.io\u002Fenforce\n```\n\n## Best Practices\n\n1. **Start with audit+warn** before enforce to assess impact\n2. **Use dry-run** to test enforcement before applying\n3. **Exempt system namespaces** (kube-system, monitoring) in cluster defaults\n4. **Pin version** (enforce-version) for predictable behavior across upgrades\n5. **Set cluster-wide baseline** as default, then restrict specific namespaces\n6. **Combine with Gatekeeper** for additional custom policies beyond PSA\n7. **Use restricted profile** for all production workloads\n8. **Document exemptions** with clear justification\n","# Implementing Pod Security Admission Controller\n\n## Overview\n\nPod Security Admission (PSA) is a built-in Kubernetes admission controller (stable since v1.25) that enforces Pod Security Standards at the namespace level. It replaces the deprecated PodSecurityPolicy (PSP) and provides three security profiles: Privileged, Baseline, and Restricted, with three enforcement modes: enforce, audit, and warn.\n\n\n## When to Use\n\n- When deploying or configuring implementing pod security admission controller 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 v1.25+ (PSA is stable\u002FGA)\n- kubectl with cluster-admin access\n- No dependency on external tools - PSA is built into kube-apiserver\n\n## Pod Security Standards\n\n### Privileged Profile\n- **Unrestricted** - No restrictions applied\n- Use case: System-level pods (kube-system, monitoring)\n\n### Baseline Profile\n- **Minimally restrictive** - Prevents known privilege escalation\n- Blocks: privileged containers, hostPID, hostIPC, hostNetwork, hostPorts, certain volume types, adding capabilities beyond runtime defaults\n\n### Restricted Profile\n- **Heavily restricted** - Follows security best practices\n- Requires: non-root, drop ALL capabilities, seccomp RuntimeDefault, read-only root filesystem considerations\n- Blocks: Everything in Baseline plus running as root, privilege escalation, non-approved volume types\n\n## Enforcement Modes\n\n| Mode | Behavior | Use Case |\n|------|----------|----------|\n| enforce | Reject pods violating policy | Production enforcement |\n| audit | Log violations to audit log | Pre-enforcement assessment |\n| warn | Show warnings to user | Developer feedback |\n\n## Implementation\n\n### Apply to Namespace via Labels\n\n```yaml\n# Restricted enforcement with audit and warn\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: production\n  labels:\n    pod-security.kubernetes.io\u002Fenforce: restricted\n    pod-security.kubernetes.io\u002Fenforce-version: v1.28\n    pod-security.kubernetes.io\u002Faudit: restricted\n    pod-security.kubernetes.io\u002Faudit-version: v1.28\n    pod-security.kubernetes.io\u002Fwarn: restricted\n    pod-security.kubernetes.io\u002Fwarn-version: v1.28\n```\n\n```yaml\n# Baseline enforcement for staging\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: staging\n  labels:\n    pod-security.kubernetes.io\u002Fenforce: baseline\n    pod-security.kubernetes.io\u002Fenforce-version: v1.28\n    pod-security.kubernetes.io\u002Faudit: restricted\n    pod-security.kubernetes.io\u002Faudit-version: v1.28\n    pod-security.kubernetes.io\u002Fwarn: restricted\n    pod-security.kubernetes.io\u002Fwarn-version: v1.28\n```\n\n```yaml\n# Privileged for system namespaces\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: kube-system\n  labels:\n    pod-security.kubernetes.io\u002Fenforce: privileged\n```\n\n### Apply Labels with kubectl\n\n```bash\n# Set restricted enforcement\nkubectl label namespace production \\\n  pod-security.kubernetes.io\u002Fenforce=restricted \\\n  pod-security.kubernetes.io\u002Fenforce-version=v1.28 \\\n  pod-security.kubernetes.io\u002Faudit=restricted \\\n  pod-security.kubernetes.io\u002Fwarn=restricted\n\n# Set baseline enforcement\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\n# Check current labels\nkubectl get namespace production -o jsonpath='{.metadata.labels}' | jq .\n```\n\n## Dry-Run Testing\n\n```bash\n# Test what would happen with restricted policy on a namespace\nkubectl label --dry-run=server --overwrite namespace staging \\\n  pod-security.kubernetes.io\u002Fenforce=restricted\n\n# Output shows existing pods that would violate the policy\n# Warning: existing pods in namespace \"staging\" violate the new PodSecurity enforce level \"restricted:latest\"\n```\n\n## Cluster-Wide Defaults (AdmissionConfiguration)\n\n```yaml\n# \u002Fetc\u002Fkubernetes\u002Fpsa-config.yaml\napiVersion: apiserver.config.k8s.io\u002Fv1\nkind: AdmissionConfiguration\nplugins:\n  - name: PodSecurity\n    configuration:\n      apiVersion: pod-security.admission.config.k8s.io\u002Fv1\n      kind: PodSecurityConfiguration\n      defaults:\n        enforce: baseline\n        enforce-version: latest\n        audit: restricted\n        audit-version: latest\n        warn: restricted\n        warn-version: latest\n      exemptions:\n        usernames: []\n        runtimeClasses: []\n        namespaces:\n          - kube-system\n          - kube-public\n          - kube-node-lease\n          - calico-system\n          - gatekeeper-system\n          - monitoring\n          - falco\n```\n\n### Apply to API Server\n\n```bash\n# Add to kube-apiserver manifests\n# \u002Fetc\u002Fkubernetes\u002Fmanifests\u002Fkube-apiserver.yaml\nspec:\n  containers:\n  - command:\n    - kube-apiserver\n    - --admission-control-config-file=\u002Fetc\u002Fkubernetes\u002Fpsa-config.yaml\n    volumeMounts:\n    - name: psa-config\n      mountPath: \u002Fetc\u002Fkubernetes\u002Fpsa-config.yaml\n      readOnly: true\n  volumes:\n  - name: psa-config\n    hostPath:\n      path: \u002Fetc\u002Fkubernetes\u002Fpsa-config.yaml\n      type: File\n```\n\n## Compliant Pod Examples\n\n### Restricted-Compliant Pod\n\n```yaml\napiVersion: v1\nkind: Pod\nmetadata:\n  name: restricted-pod\n  namespace: production\nspec:\n  securityContext:\n    runAsNonRoot: true\n    runAsUser: 1000\n    runAsGroup: 3000\n    fsGroup: 2000\n    seccompProfile:\n      type: RuntimeDefault\n  automountServiceAccountToken: false\n  containers:\n    - name: app\n      image: myregistry\u002Fmyapp:v1.0.0\n      securityContext:\n        allowPrivilegeEscalation: false\n        readOnlyRootFilesystem: true\n        capabilities:\n          drop:\n            - ALL\n      resources:\n        limits:\n          cpu: 500m\n          memory: 256Mi\n        requests:\n          cpu: 100m\n          memory: 128Mi\n      volumeMounts:\n        - name: tmp\n          mountPath: \u002Ftmp\n  volumes:\n    - name: tmp\n      emptyDir: {}\n```\n\n### Baseline-Compliant Pod\n\n```yaml\napiVersion: v1\nkind: Pod\nmetadata:\n  name: baseline-pod\n  namespace: staging\nspec:\n  containers:\n    - name: app\n      image: myregistry\u002Fmyapp:v1.0.0\n      securityContext:\n        allowPrivilegeEscalation: false\n      resources:\n        limits:\n          cpu: 500m\n          memory: 256Mi\n```\n\n## Migration from PodSecurityPolicy\n\n### Step 1: Audit Current State\n```bash\n# Check existing PSPs\nkubectl get psp\n\n# Check which service accounts use which PSP\nkubectl get clusterrolebinding -o json | \\\n  jq '.items[] | select(.roleRef.name | startswith(\"psp-\")) | {name: .metadata.name, subjects: .subjects}'\n```\n\n### Step 2: Map PSP to PSA Profiles\n```bash\n# For each namespace, determine required PSA level\nfor ns in $(kubectl get ns -o jsonpath='{.items[*].metadata.name}'); do\n  echo \"Namespace: $ns\"\n  kubectl label --dry-run=server namespace $ns \\\n    pod-security.kubernetes.io\u002Fenforce=restricted 2>&1 | head -5\ndone\n```\n\n### Step 3: Apply PSA Labels (Audit First)\n```bash\n# Start with audit mode\nkubectl label namespace production \\\n  pod-security.kubernetes.io\u002Faudit=restricted \\\n  pod-security.kubernetes.io\u002Fwarn=restricted\n```\n\n### Step 4: Review and Fix Violations\n```bash\n# Check audit logs for violations\nkubectl get events --field-selector reason=FailedCreate -A\n```\n\n### Step 5: Enable Enforcement\n```bash\nkubectl label namespace production \\\n  pod-security.kubernetes.io\u002Fenforce=restricted\n```\n\n## Monitoring\n\n```bash\n# Check PSA violations in events\nkubectl get events --all-namespaces --field-selector reason=FailedCreate\n\n# Check audit logs\nkubectl logs -n kube-system kube-apiserver-* | grep \"pod-security.kubernetes.io\"\n\n# List namespace PSA labels\nkubectl get namespaces -L pod-security.kubernetes.io\u002Fenforce\n```\n\n## Best Practices\n\n1. **Start with audit+warn** before enforce to assess impact\n2. **Use dry-run** to test enforcement before applying\n3. **Exempt system namespaces** (kube-system, monitoring) in cluster defaults\n4. **Pin version** (enforce-version) for predictable behavior across upgrades\n5. **Set cluster-wide baseline** as default, then restrict specific namespaces\n6. **Combine with Gatekeeper** for additional custom policies beyond PSA\n7. **Use restricted profile** for all production workloads\n8. **Document exemptions** with clear justification\n",{"name":5,"note":25,"tags":26,"author":32,"domain":33,"source":34,"license":15,"version":35,"nist_csf":36,"subdomain":41,"description":7,"mitre_attack":42,"source_commit":47},"Vendored verbatim from an external Apache-2.0 security-skill library, pinned by commit. Exceeds the internal 300-line skill guideline (agent-code-constraints.md) -- kept as-is because this is vendored reference material (forensics\u002Fthreat-intel procedure), not Yana AI-authored content, and trimming would damage technical accuracy.",[27,28,29,30,31],"kubernetes","pod-security-admission","psa","pod-security-standards","admission-controller","mahipal","cybersecurity","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","1.0",[37,38,39,40],"PR.PS-01","PR.IR-01","ID.AM-08","DE.CM-01","container-security",[43,44,45,46],"T1610","T1611","T1609","T1525","04450304b12645cb2b974ab96d28c0664758a88d","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Fimplementing-pod-security-admission-controller",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":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill implementing-pod-security-admission-controller",{"tool":64,"command":65},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill implementing-pod-security-admission-controller",{"tool":67,"command":68},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill implementing-pod-security-admission-controller","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fimplementing-pod-security-admission-controller\u002FSKILL.md",true,[72,78,82,88,92,96,102],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"assets\u002Ftemplate.md","ASSET","资产文件",1290,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fimplementing-pod-security-admission-controller\u002Fassets\u002Ftemplate.md",{"path":79,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fapi-reference.md","REFERENCE","参考文档",5229,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fimplementing-pod-security-admission-controller\u002Freferences\u002Fapi-reference.md",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fstandards.md",1099,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fimplementing-pod-security-admission-controller\u002Freferences\u002Fstandards.md",{"path":93,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fworkflows.md",1066,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fimplementing-pod-security-admission-controller\u002Freferences\u002Fworkflows.md",{"path":97,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":100,"sourceHtmlUrl":101},"scripts\u002Fagent.py","SCRIPT","脚本",11706,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fimplementing-pod-security-admission-controller\u002Fscripts\u002Fagent.py",{"path":103,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":104,"sourceHtmlUrl":105},"scripts\u002Fprocess.py",5185,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fimplementing-pod-security-admission-controller\u002Fscripts\u002Fprocess.py",[107,115,122,130,138,146],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":111,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"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":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"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":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"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":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":134,"sourceHtmlUrl":135,"categories":136,"keywords":137,"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":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":142,"sourceHtmlUrl":143,"categories":144,"keywords":145,"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":147,"name":148,"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":149,"categories":150,"keywords":151,"publishedAt":20},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]