Detects container escape attempts by analyzing namespace configurations, privileged container checks, dangerous capability assignments, and host path mounts using the kubernetes Python client. Identifies CVE-2022-0492 style escapes via cgroup abuse. Use when auditing container security posture or investigating escape attempts.
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add mukul975/Anthropic-Cybersecurity-Skills/performing-container-escape-detectionCompatible with
Supported agents
| name | performing-container-escape-detection |
| description | 'Detects container escape attempts by analyzing namespace configurations, privileged container checks, dangerous capability assignments, and host path mounts using the kubernetes Python client. Identifies CVE-2022-0492 style escapes via cgroup abuse. Use when auditing container security posture or investigating escape attempts. ' |
| domain | cybersecurity |
| subdomain | container-security |
| tags | - performing - container - escape - detection |
| version | '1.0' |
| author | mahipal |
| license | Apache-2.0 |
| nist_csf | - PR.PS-01 - PR.IR-01 - ID.AM-08 - DE.CM-01 |
Audit Kubernetes pods for container escape vectors including privileged mode, dangerous capabilities, host namespace sharing, and writable hostPath mounts.
from kubernetes import client, config
config.load_kube_config()
v1 = client.CoreV1Api()
pods = v1.list_pod_for_all_namespaces()
for pod in pods.items:
for container in pod.spec.containers:
sc = container.security_context
if sc and sc.privileged:
print(f"PRIVILEGED: {pod.metadata.namespace}/{pod.metadata.name}")
Key escape vectors:
# Check for docker socket mounts
for vol in pod.spec.volumes or []:
if vol.host_path and "docker.sock" in (vol.host_path.path or ""):
print(f"Docker socket exposed: {pod.metadata.name}")
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionperforming-container-escape-detectionExecute the skills CLI command in your project's root directory to begin installation:
epx add mukul975/Anthropic-Cybersecurity-Skills/performing-container-escape-detectionFetches performing-container-escape-detection from mukul975/Anthropic-Cybersecurity-Skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/performing-container-escape-detection
Restart Cursor to activate performing-container-escape-detection. Access via /performing-container-escape-detectionin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
correlating-security-events-in-qradar
mukul975/Anthropic-Cybersecurity-Skills · correlating-security-events-in-qradar · same repo
performing-hash-cracking-with-hashcat
mukul975/Anthropic-Cybersecurity-Skills · performing-hash-cracking-with-hashcat · same repo
performing-dark-web-monitoring-for-threats
mukul975/Anthropic-Cybersecurity-Skills · performing-dark-web-monitoring-for-threats · same repo
performing-hardware-security-module-integration
mukul975/Anthropic-Cybersecurity-Skills · performing-hardware-security-module-integration · same repo
extracting-browser-history-artifacts
mukul975/Anthropic-Cybersecurity-Skills · extracting-browser-history-artifacts · same repo
implementing-ddos-mitigation-with-cloudflare
mukul975/Anthropic-Cybersecurity-Skills · implementing-ddos-mitigation-with-cloudflare · same repo
performing-container-escape-detection fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
performing-container-escape-detection reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: performing-container-escape-detection is focused, and the summary matches what you get after install.
We added performing-container-escape-detection from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: performing-container-escape-detection is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: performing-container-escape-detection is focused, and the summary matches what you get after install.
performing-container-escape-detection is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend performing-container-escape-detection for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in performing-container-escape-detection — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
performing-container-escape-detection is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 40