kubernetes-security
Skill1 starsChanged 3 months agoMITView on GitHub
Kubernetes and container security skill for cluster hardening, RBAC review, admission control (OPA Gatekeeper, Kyverno), Pod Security Standards, network policies, secrets management, runtime defense (Falco, Tetragon), image supply chain (cosign, SLSA, in-toto), and CIS benchmark compliance. Use to assess and harden clusters you operate.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- kcns008/cluster-skillstheir own version, first seen Nov 8, 2026
- Masriyan/gemini-security-skillsword for word, first seen Oct 25, 2026
- abevz/devops-skillstheir own version, first seen Oct 15, 2026
- GoldenWing-360/claude-security-skillstheir own version, first seen May 12, 2026
Other versions4 projects use a version of this.
Word for word · 1
- Masriyan/gemini-security-skills★ 4100% same
Edited · 0
None found.
Wrote their own version · 3
- GoldenWing-360/claude-security-skills★ 16same name
- kcns008/cluster-skills★ 4same name
- abevz/devops-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository23 other files it gives its agents.
- ai-redteamSkill
- api-security-automationSkill
- assembly-programmingSkill
- bug-bounty-workflowSkill
- claude-mythos-emulationSkill
- cloud-security-automationSkill
- cybersecurity-partnerSkill
- detection-engineeringSkill
- devsecopsSkill
- exploit-developmentSkill
- forensics-triageSkill
- gemini-tool-orchestratorSkill
- go-programmingSkill
- malware-reverse-engineeringSkill
- multilingualSkill
- offensive-securitySkill
- osint-recon-automationSkill
- prompt-enhancementSkill
- purple-team-automationSkill
- python-programmingSkill
- smart-contract-auditSkill
- soc-operationsSkill
- threat-intel-fusionSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Avoid disruptive runtime probes on production.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Kubernetes Security
Authorization Boundary
- Require cluster context, namespace scope, and read-only kubeconfig before live queries.
- Avoid disruptive runtime probes on production; prefer staging or ephemeral clusters.
Hardening Workflow
- Inventory: API server flags, node OS, CNI, CSI, ingress, service mesh, admission plugins, controllers.
- Scan:
kube-bench,kubescape,trivy k8s,polaris,kubeaudit,popeye. - RBAC: enumerate
ClusterRole/RoleBinding; flag wildcard verbs,system:masters,escalate,bind,impersonate, secret reads from broad subjects. - Workloads: enforce Pod Security
restricted, drop capabilities, read-only rootfs, non-root UID, seccompRuntimeDefault, nohostPath/hostNetwork/hostPID. - Network: default-deny
NetworkPolicy; explicit egress to known services; mTLS via mesh where applicable. - Supply chain: signed images (
cosign verify), provenance attestations (SLSA), admission policy that blocks unsigned. - Runtime: Falco/Tetragon rules for exec-in-container, reverse shells, crypto miners, sensitive mounts.
Multi-Tenant Patterns
- Namespace-per-tenant with quotas, limit ranges, and
NetworkPolicyisolation. - Separate node pools for untrusted workloads; gVisor or Kata for sandboxing.
- Per-tenant audit log filters; secrets via external KMS, never inline.
Output Contract
inventory.yaml,findings.csv,policies/(Gatekeeper/Kyverno),netpol/,runtime/falco-rules.yaml.runbook.md: incident response for compromised pod, leaked token, miner detection.gap.md: missing telemetry and proposed fixes.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.