Install the "detecting-container-escape-attempts" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/detecting-container-escape-attempts into .claude/skills/detecting-container-escape-attempts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "detecting-container-escape-attempts", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill detecting-container-escape-attempts -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "detecting-container-escape-attempts" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/detecting-container-escape-attempts into .agents/skills/detecting-container-escape-attempts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "detecting-container-escape-attempts", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill detecting-container-escape-attempts -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "detecting-container-escape-attempts" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/detecting-container-escape-attempts into .cursor/skills/detecting-container-escape-attempts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "detecting-container-escape-attempts", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill detecting-container-escape-attempts -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "detecting-container-escape-attempts" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/detecting-container-escape-attempts into .gemini/skills/detecting-container-escape-attempts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "detecting-container-escape-attempts", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill detecting-container-escape-attempts -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "detecting-container-escape-attempts" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/detecting-container-escape-attempts into .github/skills/detecting-container-escape-attempts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "detecting-container-escape-attempts", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill detecting-container-escape-attempts -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "detecting-container-escape-attempts" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/detecting-container-escape-attempts into .opencode/skills/detecting-container-escape-attempts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "detecting-container-escape-attempts", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
detecting-container-escape-attempts
GitHub stars
34k
Token cost
~2.9k tokens
SKILL.md length
294 words
Files
8 (incl. scripts, references, assets)
Skills in repo
644
Repo updated
First seen
Licence
Apache-2.0
At a glance
Detects container escape at runtime across tooling - namespace manipulation, capability abuse, kernel exploits, sensitive host mounts, and anomalous syscalls - and explains which signals matter…
Works in 5 steps: Deploy Falco for Runtime Detection → Custom Falco Rules for Escape Detection → Configure Seccomp Profile for Escape… → …
Deciding what breakout behaviour to monitor
SKILL.md covers Overview, When to Use, Prerequisites and Core Concepts, plus 3 more sections
Runs Python scripts from its folder; calls helm, kubectl and docker; reaches falcosecurity.github.io and hooks.slack.com
What it does
Detecting Container Escape Attempts is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Detects container escape at runtime across tooling - namespace manipulation, capability abuse, kernel exploits, sensitive host mounts, and anomalous syscalls - and explains which signals matter regardless of whether Falco, Sysdig, auditd, or an EDR is doing the collection. Use when deciding what breakout behaviour to monitor, investigating a suspected Docker or Kubernetes breakout, or comparing escape coverage across runtime sensors. Keywords: container escape, breakout, namespaces, CAPSYSADMIN, privileged…
Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including scripts, reference files and assets (for example `assets/template.md`, `references/api-reference.md` and `references/standards.md`).
It sits in DevOps & Cloud, covering Containers, Container orchestration and Security operations. It works with Docker and Kubernetes. The repository describes itself as: 817 structured cybersecurity skills for AI agents · Mapped to 6 frameworks: MITRE ATT&CK, NIST CSF 2.0, MITRE ATLAS, D3FEND, NIST AI RMF & MITRE F3 (Fight Fraud) · agentskills.io…. The licence is Apache-2.0.
When your agent uses it
Deciding what breakout behaviour to monitor
Investigating a suspected Docker
Kubernetes breakout
Comparing escape coverage across runtime sensors
Example prompts
“Use the detecting-container-escape-attempts skill to detect container escape at runtime across tooling - namespace manipulation, capability abuse…”
“/detecting-container-escape-attempts”
Requirements
Python 3
Docker
Workflow steps
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 54a7988. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 2 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
helm
kubectl
docker
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
falcosecurity.github.io
hooks.slack.com
Also links to:
falco.org
book.hacktricks.xyz
attack.mitre.org
sysdig.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Detecting Container Escape Attempts loads about 2.9k tokens when it runs, and up to ~4.8k if it reads all its reference files. Until then it costs about 188 tokens; SKILL.md has 294 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~188
When it runs· the whole SKILL.md, loaded when a task matches
~2.9k
With references· SKILL.md plus every file in references/, read only if the agent opens them
~4.8k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
Download SKILL.mdSave it as .claude/skills/detecting-container-escape-attempts/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
detecting-container-escape-attempts
description
Detects container escape at runtime across tooling - namespace manipulation, capability abuse, kernel exploits, sensitive host mounts, and anomalous syscalls - and explains which signals matter regardless of whether Falco, Sysdig, auditd, or an EDR is doing the collection. Use when deciding what breakout behaviour to monitor, investigating a suspected Docker or Kubernetes breakout, or comparing escape coverage across runtime sensors. Keywords: container escape, breakout, namespaces, CAP_SYS_ADMIN, privileged, hostPath, kernel exploit, syscall. Do not use for Falco rule syntax itself - use detecting-container-escape-with-falco-rules; for a static configuration sweep use performing-container-escape-detection.
Platform Monitoring, Process Code Segment Verification, Stack Frame Canary Validation, Segment Address Offset Randomization, Process Analysis
nist_csf
PR.PS-01, PR.IR-01, ID.AM-08, DE.CM-01
mitre_attack
T1610, T1611, T1609, T1525
Detecting Container Escape Attempts
Overview
Container escape is a critical attack technique where an adversary breaks out of container isolation to access the host system or other containers. Detection involves monitoring for escape indicators such as namespace manipulation, capability abuse, kernel exploits, mounted sensitive paths, and anomalous syscall patterns using runtime security tools like Falco, Sysdig, and custom seccomp/audit rules.
When to Use
When investigating security incidents that require detecting container escape attempts
When building detection rules or threat hunting queries for this domain
When SOC analysts need structured procedures for this analysis type
When validating security monitoring coverage for related attack techniques
Prerequisites
Linux host with kernel 5.10+ (eBPF support)
Falco 0.37+ installed (kernel module or eBPF probe)
Detecting Container Escape Attempts next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Detecting Container Escape Attempts compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Detecting Container Escape Attempts this skillmukul975/Anthropic-Cybersecurity-Skills
Deploys and configures a LangBot instance with Docker Compose or Kubernetes, covering config.yaml, the Box sandbox runtime, the plugin runtime and the global API key.
Walks through reverse engineering Go-compiled malware in Ghidra: parsing buildinfo and pclntab, recovering stripped function names and extracting dependencies.
Detects DNS tunneling, ICMP exfiltration and HTTP-based covert channels in packet captures and DNS logs when hunting for hidden command-and-control traffic.
Questions about Detecting Container Escape Attempts
What does Detecting Container Escape Attempts do?
Detects container escape at runtime across tooling - namespace manipulation, capability abuse, kernel exploits, sensitive host mounts, and anomalous syscalls - and explains which signals matter…. Detecting Container Escape Attempts is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Detects container escape at runtime across tooling - namespace manipulation, capability abuse, kernel exploits, sensitive host mounts, and anomalous syscalls - and explains which signals matter regardless of whether Falco, Sysdig, auditd, or an EDR is doing the collection.
When should I use Detecting Container Escape Attempts?
Detecting Container Escape Attempts fits situations like: deciding what breakout behaviour to monitor; investigating a suspected Docker; Kubernetes breakout; comparing escape coverage across runtime sensors.
How do I install Detecting Container Escape Attempts in Claude Code?
Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill detecting-container-escape-attempts -a claude-code`. Or copy the skill folder (skills/detecting-container-escape-attempts in mukul975/Anthropic-Cybersecurity-Skills) into .claude/skills/detecting-container-escape-attempts in your project. Claude Code loads it when a task matches its description.
How do I install Detecting Container Escape Attempts in Codex?
Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill detecting-container-escape-attempts -a codex`. Or copy the skill folder (skills/detecting-container-escape-attempts in mukul975/Anthropic-Cybersecurity-Skills) into .agents/skills/detecting-container-escape-attempts in your project. Codex loads it when a task matches its description.
Can I use Detecting Container Escape Attempts in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill detecting-container-escape-attempts -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/detecting-container-escape-attempts, .gemini/skills/detecting-container-escape-attempts, .github/skills/detecting-container-escape-attempts and .opencode/skills/detecting-container-escape-attempts in your project.
What does Detecting Container Escape Attempts need to run?
Going by SKILL.md and its folder, Detecting Container Escape Attempts needs Python for the scripts in its folder and the command-line tools its instructions call (helm, kubectl and docker). Our summary lists: Python 3; Docker.
Does Detecting Container Escape Attempts access the network?
SKILL.md names 6 domains. In commands or code: falcosecurity.github.io and hooks.slack.com; the agent is likely to contact these when it follows the instructions. As links in the text: falco.org, book.hacktricks.xyz, attack.mitre.org and sysdig.com. This is read from the text; nothing was executed.
Is Detecting Container Escape Attempts safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Detecting Container Escape Attempts use?
Detecting Container Escape Attempts is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Detecting Container Escape Attempts use?
About 2.9k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.9k tokens, read only when the agent opens those files.
What are the alternatives to Detecting Container Escape Attempts?
Skills that share tags, products or a category with Detecting Container Escape Attempts: Alibabacloud Ecs Sec Userspace (aliyun/alibabacloud-ecs-troubleshoot-skills, 148 stars), Infrastructure Audit (forefy/.context, 152 stars), LangBot Deployment Guide (langbot-app/LangBot, 18k stars) and Build Openshell Mxc Windows (NVIDIA/OpenShell, 16k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Detecting Container Escape Attempts?
mukul975 (a GitHub user) maintains it in mukul975/Anthropic-Cybersecurity-Skills, which has 34,116 GitHub stars. The repository holds 644 skills in this directory. The repository was last updated on August 31, 2026.