[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M731A5G5894N6S9KSW7GEESX":3,"skill-same:01M731A5G5894N6S9KSW7GEESX":47},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M731A5G5894N6S9KSW7GEESX","cni-network-policies",null,"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\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcni-network-policies\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: cni-network-policies\ndescription: Container Network Interface (CNI) plugin patterns and Kubernetes NetworkPolicy for agent network isolation. CNI plugin structure, IPAM, namespace-level firewall rules, egress restrictions, and deny-all defaults. Sources: containernetworking\u002Fplugins (Apache-2.0).\norigin: yana-ai — synthesized from containernetworking\u002Fplugins (Apache-2.0)\nlicense: Apache-2.0\nversion: 1.0.0\ncompatibility: yana-ai >= 1.3.52\n---\n\n# \u002Fcni-network-policies\n\n## When to Use\n\n- Isolate agent namespaces: agent-A cannot reach agent-B's pods directly\n- Deny-all default with explicit allow: principle of least-privilege networking\n- Restrict egress: sandboxed agents can only call approved external endpoints\n- Block inter-namespace traffic: dev agents cannot reach prod database pods\n\n## Do NOT use for\n\n- L7 policy (use [[istio-traffic-management]] for HTTP-level AuthorizationPolicy)\n- Performance-sensitive East-West (NetworkPolicy adds iptables rules, minor overhead)\n\n---\n\n## NetworkPolicy: deny all ingress\u002Fegress by default\n\n```yaml\n# Apply first in every namespace — blocks all traffic until explicitly allowed\napiVersion: networking.k8s.io\u002Fv1\nkind: NetworkPolicy\nmetadata:\n  name:      deny-all\n  namespace: yamtam\nspec:\n  podSelector: {}       # applies to all pods in namespace\n  policyTypes:\n    - Ingress\n    - Egress\n  # No ingress\u002Fegress rules = deny everything\n```\n\n---\n\n## Allow specific ingress (agent-b accepts from agent-a only)\n\n```yaml\napiVersion: networking.k8s.io\u002Fv1\nkind: NetworkPolicy\nmetadata:\n  name:      allow-agent-a-to-b\n  namespace: yamtam\nspec:\n  podSelector:\n    matchLabels: { app: agent-b }\n  policyTypes: [Ingress]\n  ingress:\n    - from:\n        - podSelector:\n            matchLabels: { app: agent-a }\n      ports:\n        - protocol: TCP\n          port:     3000\n```\n\n---\n\n## Allow DNS egress (required for all pods)\n\n```yaml\n# Without this, pods can't resolve service names after deny-all\napiVersion: networking.k8s.io\u002Fv1\nkind: NetworkPolicy\nmetadata:\n  name:      allow-dns\n  namespace: yamtam\nspec:\n  podSelector: {}\n  policyTypes: [Egress]\n  egress:\n    - ports:\n        - protocol: UDP\n          port:     53\n        - protocol: TCP\n          port:     53\n```\n\n---\n\n## Restrict agent egress to approved external IPs\n\n```yaml\n# Sandbox agents: only reach internal services + specific external IPs\napiVersion: networking.k8s.io\u002Fv1\nkind: NetworkPolicy\nmetadata:\n  name:      sandbox-egress\n  namespace: yamtam-sandbox\nspec:\n  podSelector:\n    matchLabels: { tier: sandbox }\n  policyTypes: [Egress]\n  egress:\n    # Allow internal cluster traffic\n    - to:\n        - namespaceSelector: {}\n    # Allow specific external API (e.g., Anthropic API)\n    - to:\n        - ipBlock:\n            cidr: 160.79.104.0\u002F23   # api.anthropic.com range\n      ports:\n        - protocol: TCP\n          port:     443\n```\n\n---\n\n## CNI plugin configuration (reference)\n\n```json\n{\n  \"cniVersion\": \"1.0.0\",\n  \"name\":       \"yamtam-net\",\n  \"type\":       \"bridge\",\n  \"bridge\":     \"cni0\",\n  \"isGateway\":  true,\n  \"ipMasq\":     true,\n  \"ipam\": {\n    \"type\":   \"host-local\",\n    \"subnet\": \"10.88.0.0\u002F16\",\n    \"routes\": [{ \"dst\": \"0.0.0.0\u002F0\" }]\n  }\n}\n```\n\n---\n\n## Anti-Fake-Pass Checklist\n\n```\n❌ NetworkPolicy without DNS egress allow → pods can't resolve DNS → all outbound connections fail\n❌ podSelector: {} on Egress means all pods → correct; but leaving egress rules empty = deny all egress\n❌ Policy not enforced without CNI plugin that supports NetworkPolicy (e.g., bare Flannel doesn't) → use Calico\u002FCilium\n❌ ipBlock CIDR for external API → cloud provider NAT may change IPs; use FQDN with Cilium instead\n❌ Deny-all applied before allow rules → window where all traffic is blocked (apply atomically)\n❌ NetworkPolicy only applies to pods in same namespace by default → namespaceSelector required for cross-namespace\n```\n","# \u002Fcni-network-policies\n\n## When to Use\n\n- Isolate agent namespaces: agent-A cannot reach agent-B's pods directly\n- Deny-all default with explicit allow: principle of least-privilege networking\n- Restrict egress: sandboxed agents can only call approved external endpoints\n- Block inter-namespace traffic: dev agents cannot reach prod database pods\n\n## Do NOT use for\n\n- L7 policy (use [[istio-traffic-management]] for HTTP-level AuthorizationPolicy)\n- Performance-sensitive East-West (NetworkPolicy adds iptables rules, minor overhead)\n\n---\n\n## NetworkPolicy: deny all ingress\u002Fegress by default\n\n```yaml\n# Apply first in every namespace — blocks all traffic until explicitly allowed\napiVersion: networking.k8s.io\u002Fv1\nkind: NetworkPolicy\nmetadata:\n  name:      deny-all\n  namespace: yamtam\nspec:\n  podSelector: {}       # applies to all pods in namespace\n  policyTypes:\n    - Ingress\n    - Egress\n  # No ingress\u002Fegress rules = deny everything\n```\n\n---\n\n## Allow specific ingress (agent-b accepts from agent-a only)\n\n```yaml\napiVersion: networking.k8s.io\u002Fv1\nkind: NetworkPolicy\nmetadata:\n  name:      allow-agent-a-to-b\n  namespace: yamtam\nspec:\n  podSelector:\n    matchLabels: { app: agent-b }\n  policyTypes: [Ingress]\n  ingress:\n    - from:\n        - podSelector:\n            matchLabels: { app: agent-a }\n      ports:\n        - protocol: TCP\n          port:     3000\n```\n\n---\n\n## Allow DNS egress (required for all pods)\n\n```yaml\n# Without this, pods can't resolve service names after deny-all\napiVersion: networking.k8s.io\u002Fv1\nkind: NetworkPolicy\nmetadata:\n  name:      allow-dns\n  namespace: yamtam\nspec:\n  podSelector: {}\n  policyTypes: [Egress]\n  egress:\n    - ports:\n        - protocol: UDP\n          port:     53\n        - protocol: TCP\n          port:     53\n```\n\n---\n\n## Restrict agent egress to approved external IPs\n\n```yaml\n# Sandbox agents: only reach internal services + specific external IPs\napiVersion: networking.k8s.io\u002Fv1\nkind: NetworkPolicy\nmetadata:\n  name:      sandbox-egress\n  namespace: yamtam-sandbox\nspec:\n  podSelector:\n    matchLabels: { tier: sandbox }\n  policyTypes: [Egress]\n  egress:\n    # Allow internal cluster traffic\n    - to:\n        - namespaceSelector: {}\n    # Allow specific external API (e.g., Anthropic API)\n    - to:\n        - ipBlock:\n            cidr: 160.79.104.0\u002F23   # api.anthropic.com range\n      ports:\n        - protocol: TCP\n          port:     443\n```\n\n---\n\n## CNI plugin configuration (reference)\n\n```json\n{\n  \"cniVersion\": \"1.0.0\",\n  \"name\":       \"yamtam-net\",\n  \"type\":       \"bridge\",\n  \"bridge\":     \"cni0\",\n  \"isGateway\":  true,\n  \"ipMasq\":     true,\n  \"ipam\": {\n    \"type\":   \"host-local\",\n    \"subnet\": \"10.88.0.0\u002F16\",\n    \"routes\": [{ \"dst\": \"0.0.0.0\u002F0\" }]\n  }\n}\n```\n\n---\n\n## Anti-Fake-Pass Checklist\n\n```\n❌ NetworkPolicy without DNS egress allow → pods can't resolve DNS → all outbound connections fail\n❌ podSelector: {} on Egress means all pods → correct; but leaving egress rules empty = deny all egress\n❌ Policy not enforced without CNI plugin that supports NetworkPolicy (e.g., bare Flannel doesn't) → use Calico\u002FCilium\n❌ ipBlock CIDR for external API → cloud provider NAT may change IPs; use FQDN with Cilium instead\n❌ Deny-all applied before allow rules → window where all traffic is blocked (apply atomically)\n❌ NetworkPolicy only applies to pods in same namespace by default → namespaceSelector required for cross-namespace\n```\n",{},"main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa",".claude\u002Fskills\u002Fcni-network-policies",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":7,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill cni-network-policies",{"tool":39,"command":40},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill cni-network-policies",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill cni-network-policies","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcni-network-policies\u002FSKILL.md",true,[],[48,56,63,71,79,87],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":52,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":18},"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":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":18},"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":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":67,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":75,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"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":88,"name":89,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":18},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]