Agent skill

Detecting Container Runtime Threats With Falco

by mukul975 in mukul975/Anthropic-Cybersecurity-Skills

Deploys and operates Falco with the modern eBPF driver in Kubernetes and Docker, covering driver selection, Helm installation, output channels, and the built-in ruleset that detects container…

Apache-2.0Auto-check: warningsDevOps & Cloud

Install Detecting Container Runtime Threats With Falco

The automated check flagged lines worth reading first. See the safety section below.

skills CLI
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill detecting-container-runtime-threats-with-falco -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills detecting-container-runtime-threats-with-falco --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/detecting-container-runtime-threats-with-falco .claude/skills/detecting-container-runtime-threats-with-falco && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
detecting-container-runtime-threats-with-falco
GitHub stars
34k
Token cost
~3k tokens
SKILL.md length
597 words
Files
5 (incl. scripts, references)
Skills in repo
644
Repo updated
First seen
Licence
Apache-2.0

At a glance

Deploys and operates Falco with the modern eBPF driver in Kubernetes and Docker, covering driver selection, Helm installation, output channels, and the built-in ruleset that detects container…

  • Works in 9 steps: Install Falco and Confirm the Driver → Learn the Rule, Macro, and List Schema → Write a Container-Escape Detection Rule… → …
  • Standing Falco up on a cluster
  • SKILL.md covers Overview, When to Use, Prerequisites and Objectives, plus 5 more sections
  • Runs Python scripts from its folder; calls helm, kubectl and apt-get; reaches falco.org and falcosecurity.github.io

What it does

Detecting Container Runtime Threats With Falco is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Deploys and operates Falco with the modern eBPF driver in Kubernetes and Docker, covering driver selection, Helm installation, output channels, and the built-in ruleset that detects container escape, namespace abuse, privileged mounts, and anomalous syscalls. Use when standing Falco up on a cluster, choosing between the eBPF and kernel-module drivers, routing Falco alerts into a SIEM or Falcosidekick, or upgrading an existing deployment. Keywords: Falco, modernebpf, kernel module, Helm, Falcosidekick, runtime…

Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts and reference files (for example `references/api-reference.md`, `references/standards.md` and `scripts/agent.py`).

It sits in DevOps & Cloud, covering Container orchestration, Security operations and Containers. 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

  • Standing Falco up on a cluster
  • Choosing between the eBPF and kernel-module drivers
  • Routing Falco alerts into a SIEM
  • Upgrading an existing deployment

Example prompts

  • “Use the detecting-container-runtime-threats-with-falco skill to deploy and operates Falco with the modern eBPF driver in Kubernetes and Docker…”
  • “/detecting-container-runtime-threats-with-falco”

Requirements

  • Python 3
  • Docker

Workflow steps

9 steps, taken from the step headings in SKILL.md.

  1. Install Falco and Confirm the Driver
  2. Learn the Rule, Macro, and List Schema
  3. Write a Container-Escape Detection Rule (release_agent / cgroup)
  4. Detect Namespace Breakout (setns / nsenter)
  5. Detect Privileged Mount and Docker Socket Abuse
  6. Detect Reverse Shells and Sensitive File Reads
  7. Validate Rule Syntax and Load
  8. Trigger and Confirm (Purple-Team)
  9. Forward Alerts to a SIEM

What it can do on your machine

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 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • helm
    • kubectl
    • apt-get
    • curl

    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:

    • falco.org
    • falcosecurity.github.io
    • download.falco.org

    Also links to:

    • github.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 Runtime Threats With Falco loads about 3k tokens when it runs, and up to ~4.1k if it reads all its reference files. Until then it costs about 170 tokens; SKILL.md has 597 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~170
When it runs · the whole SKILL.md, loaded when a task matches
~3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.1k

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: warnings

The automated check found patterns that need a careful read before installing.

  • NoteRuns commands with sudoSKILL.md:64
    sudo gpg --dearmor -o /usr/share/keyrings/falco-archive-keyring.gpg
  • NoteRuns commands with sudoSKILL.md:67
    sudo tee /etc/apt/sources.list.d/falcosecurity.list
  • NoteRuns commands with sudoSKILL.md:68
    sudo apt-get update -y && sudo apt-get install -y falco
  • NoteRuns commands with sudoSKILL.md:101
    sudo falcoctl driver config --type modern_ebpf
  • NoteRuns commands with sudoSKILL.md:102
    sudo systemctl enable --now falco-modern-bpf.service
  • NoteRuns commands with sudoSKILL.md:103
    sudo systemctl status falco-modern-bpf.service
  • WarningMentions a credentials file (SSH keys, cloud or package-manager tokens)SKILL.md:215
    (/etc/shadow, /etc/sudoers, /root/.ssh/id_rsa)
  • NoteRuns commands with sudoSKILL.md:227
    sudo falco --validate /etc/falco/rules.d/custom-escape.yaml
  • NoteRuns commands with sudoSKILL.md:230
    sudo falco -r /etc/falco/rules.d/custom-escape.yaml

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.

SKILL.md

The full file from mukul975/Anthropic-Cybersecurity-Skills at commit 54a7988, republished under its Apache-2.0 licence (© mukul975). 597 words, ~2,969 tokens.

Download SKILL.mdSave it as .claude/skills/detecting-container-runtime-threats-with-falco/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
detecting-container-runtime-threats-with-falco
description
Deploys and operates Falco with the modern eBPF driver in Kubernetes and Docker, covering driver selection, Helm installation, output channels, and the built-in ruleset that detects container escape, namespace abuse, privileged mounts, and anomalous syscalls. Use when standing Falco up on a cluster, choosing between the eBPF and kernel-module drivers, routing Falco alerts into a SIEM or Falcosidekick, or upgrading an existing deployment. Keywords: Falco, modern_ebpf, kernel module, Helm, Falcosidekick, runtime security, syscall. Do not use for authoring individual escape rules - use detecting-container-escape-with-falco-rules.
domain
cybersecurity
subdomain
container-security
tags
falco, runtime-security, ebpf, container-escape, syscall-monitoring, detection-engineering, kubernetes, threat-detection
version
1.0
author
mahipal
license
Apache-2.0
nist_csf
DE.CM-01
mitre_attack
T1611

Detecting Container Runtime Threats with Falco

Overview

Falco is the CNCF graduated runtime-security project (originally by Sysdig) that consumes Linux kernel syscalls and Kubernetes audit events through a driver, evaluates them against a YAML rule engine, and emits real-time alerts. It is the de facto open-source detection tool for runtime threats inside containers, including container escape (MITRE ATT&CK T1611, Escape to Host), namespace manipulation (setns), privileged mounts, reverse shells, and unexpected outbound connections.

Falco supports three drivers: the modern eBPF probe (preferred default, requires kernel >= 5.8, shipped directly inside the Falco binary so no init container is needed), the legacy eBPF probe, and the kernel module (kmod). Driver selection is handled by falcoctl driver config --type {kmod|ebpf|modern_ebpf} or driver.kind=modern_ebpf in the Helm chart. On Kubernetes, Falco runs as a DaemonSet so every node is monitored, and falcoctl automatically installs and updates rule artifacts from the Falco rules registry.

This skill covers authoring and deploying custom Falco rules to detect the container-escape primitives and anomalous-behavior signals that the breakout techniques in this collection produce. Each Falco rule has the fields rule, desc, condition, output, priority, and optional tags; reusable logic is factored into macro and list objects. Source: falco.org official documentation; falcosecurity/rules repository; Sysdig Falco detection research (e.g., CVE-2025-22224).

When to Use

  • Building runtime detections for a Kubernetes or Docker environment
  • Validating that container-escape and lateral-movement attempts generate alerts (purple-team)
  • Adding coverage for a newly disclosed runtime CVE
  • Hardening a SOC's container telemetry pipeline (Falco -> Falcosidekick -> SIEM)

Prerequisites

  • A Linux host (kernel >= 5.8 for modern eBPF) or Kubernetes cluster you administer
  • Falco install:
    bash
    # Helm (Kubernetes, modern eBPF, JSON output for SIEM ingest)
    helm repo add falcosecurity https://falcosecurity.github.io/charts
    helm repo update
    helm install falco falcosecurity/falco \
      --namespace falco --create-namespace \
      --set driver.kind=modern_ebpf \
      --set collectors.containerd.enabled=true \
      --set falco.json_output=true \
      --set tty=true
    
    # Linux package install (Debian/Ubuntu)
    curl -fsSL https://falco.org/repo/falcosecurity-packages.asc | \
      sudo gpg --dearmor -o /usr/share/keyrings/falco-archive-keyring.gpg
    echo "deb [signed-by=/usr/share/keyrings/falco-archive-keyring.gpg] \
      https://download.falco.org/packages/deb stable main" | \
      sudo tee /etc/apt/sources.list.d/falcosecurity.list
    sudo apt-get update -y && sudo apt-get install -y falco
  • Basic familiarity with Falco fields (evt.type, proc.name, container.id, fd.name)

Objectives

  • Install Falco with the modern eBPF driver
  • Understand the rule/macro/list schema and key Falco filter fields
  • Author custom rules for container escape, setns, privileged mounts, sensitive-file reads, and reverse shells
  • Load custom rules and validate syntax
  • Trigger and confirm detections (purple-team validation)
  • Forward alerts to a SIEM via Falcosidekick
Show full SKILL.md (276 more words)Show less

MITRE ATT&CK Mapping

Technique IDNameTactic
T1611Escape to HostPrivilege Escalation
T1059.004Command and Scripting Interpreter: Unix ShellExecution
T1610Deploy ContainerDefense Evasion / Execution
T1543Create or Modify System ProcessPersistence
T1071.001Application Layer Protocol: Web ProtocolsCommand and Control

Workflow

Step 1: Install Falco and Confirm the Driver
bash
# Kubernetes: confirm the DaemonSet is running on every node
kubectl get pods -n falco -o wide
kubectl logs -n falco -l app.kubernetes.io/name=falco | grep -i "driver"

# Linux host: configure driver and start
sudo falcoctl driver config --type modern_ebpf
sudo systemctl enable --now falco-modern-bpf.service
sudo systemctl status falco-modern-bpf.service
Step 2: Learn the Rule, Macro, and List Schema

Custom rules live in /etc/falco/falco_rules.local.yaml or /etc/falco/rules.d/, referenced from rules_files in /etc/falco/falco.yaml.

yaml
# /etc/falco/rules.d/custom-escape.yaml
- list: shell_binaries
  items: [bash, sh, zsh, dash, ash, ksh]

- macro: spawned_process
  condition: evt.type in (execve, execveat) and evt.dir = <

- macro: container
  condition: container.id != host
Step 3: Write a Container-Escape Detection Rule (release_agent / cgroup)
yaml
- rule: Container Escape via cgroup release_agent
  desc: >
    Detect a process inside a container writing to a cgroup release_agent or
    notify_on_release file, a classic privileged-container breakout primitive.
  condition: >
    container
    and spawned_process
    and (evt.type in (open, openat, openat2) or evt.type=write)
    and (fd.name endswith "release_agent"
         or fd.name endswith "notify_on_release")
    and evt.is_open_write=true
  output: >
    Container escape attempt via cgroup release_agent
    (user=%user.name command=%proc.cmdline file=%fd.name
     container=%container.name image=%container.image.repository)
  priority: CRITICAL
  tags: [container, mitre_privilege_escalation, T1611]
Step 4: Detect Namespace Breakout (setns / nsenter)
yaml
- rule: Namespace Change via setns to Host
  desc: >
    Detect setns/nsenter used to enter the host namespace (e.g. nsenter -t 1),
    a common container-to-host escape technique.
  condition: >
    evt.type = setns
    and container
    and proc.name in (nsenter, unshare)
  output: >
    Namespace breakout via setns/nsenter
    (user=%user.name proc=%proc.name cmd=%proc.cmdline
     container=%container.name image=%container.image.repository)
  priority: CRITICAL
  tags: [container, mitre_privilege_escalation, T1611]
Step 5: Detect Privileged Mount and Docker Socket Abuse
yaml
- rule: Mount Launched in Privileged Container
  desc: Detect the mount binary running inside a privileged container.
  condition: >
    spawned_process
    and container
    and container.privileged = true
    and proc.name = mount
  output: >
    Mount executed in privileged container
    (cmd=%proc.cmdline container=%container.name image=%container.image.repository)
  priority: WARNING
  tags: [container, mitre_privilege_escalation, T1611]

- rule: Docker Socket Accessed From Container
  desc: A container process reads/writes the host Docker daemon socket.
  condition: >
    container
    and (evt.type in (open, openat, openat2, connect))
    and fd.name = /var/run/docker.sock
  output: >
    Container touched docker.sock - possible daemon-API escape
    (proc=%proc.name cmd=%proc.cmdline container=%container.name)
  priority: CRITICAL
  tags: [container, mitre_execution, T1610]
Step 6: Detect Reverse Shells and Sensitive File Reads
yaml
- rule: Reverse Shell From Container
  desc: A shell in a container with stdin/stdout wired to a network socket.
  condition: >
    spawned_process
    and container
    and proc.name in (shell_binaries)
    and (fd.num in (0, 1, 2))
    and fd.type in (ipv4, ipv6)
  output: >
    Reverse shell detected in container
    (proc=%proc.cmdline connection=%fd.name container=%container.name)
  priority: CRITICAL
  tags: [container, mitre_execution, T1059.004]

- rule: Read Sensitive Host File From Container
  desc: Container reads /etc/shadow or similar after a likely escape.
  condition: >
    container
    and (evt.type in (open, openat, openat2))
    and evt.is_open_read=true
    and fd.name in (/etc/shadow, /etc/sudoers, /root/.ssh/id_rsa)
  output: >
    Sensitive file read from container (file=%fd.name proc=%proc.cmdline
     container=%container.name)
  priority: WARNING
  tags: [container, mitre_credential_access]
Step 7: Validate Rule Syntax and Load
bash
# Dry-run validate a rules file without starting the engine
sudo falco --validate /etc/falco/rules.d/custom-escape.yaml

# Run Falco with only the custom rules to test
sudo falco -r /etc/falco/rules.d/custom-escape.yaml

# Helm: ship custom rules via values (mounted into /etc/falco/rules.d)
helm upgrade falco falcosecurity/falco -n falco --reuse-values \
  --set-file "customRules.custom-escape\.yaml"=./custom-escape.yaml
Step 8: Trigger and Confirm (Purple-Team)
bash
# In a test container, trigger the setns rule
kubectl run pwn --rm -it --image=alpine --overrides='
{"spec":{"hostPID":true,"containers":[{"name":"pwn","image":"alpine",
"securityContext":{"privileged":true},"stdin":true,"tty":true,
"command":["sh"]}]}}' -- sh -c 'nsenter -t 1 -m -u -i -n -p -- id'

# Confirm the alert fired
kubectl logs -n falco -l app.kubernetes.io/name=falco | grep -i "Namespace breakout"
Step 9: Forward Alerts to a SIEM
bash
# Deploy Falcosidekick to fan out alerts (Elastic, Slack, Splunk, etc.)
helm upgrade falco falcosecurity/falco -n falco --reuse-values \
  --set falcosidekick.enabled=true \
  --set falcosidekick.config.elasticsearch.hostport=https://elastic:9200 \
  --set falcosidekick.config.elasticsearch.index=falco

Tools and Resources

ToolPurposeSource
FalcoRuntime syscall detection enginehttps://falco.org
falcoctlDriver + rules artifact managerhttps://github.com/falcosecurity/falcoctl
falcosecurity/rulesMaintained default rulesethttps://github.com/falcosecurity/rules
FalcosidekickAlert fan-out to SIEM/chathttps://github.com/falcosecurity/falcosidekick
Falco Helm chartKubernetes DaemonSet deployhttps://github.com/falcosecurity/charts

Key Falco Filter Fields

FieldMeaning
evt.typeSyscall name (execve, setns, open, connect)
evt.dirEvent direction (< exit, > enter)
proc.name / proc.cmdlineProcess name / full command line
container.id / container.privilegedContainer identity / privileged flag
container.image.repositoryImage name
fd.name / fd.typeFile/socket path / type (ipv4, ipv6)
evt.is_open_write / evt.is_open_readOpen intent
user.nameActing user

Validation Criteria

  • Falco installed with the modern eBPF driver (DaemonSet on all nodes)
  • Custom rules file validated with falco --validate
  • release_agent / setns / privileged-mount / docker.sock rules loaded
  • Reverse-shell and sensitive-file-read rules loaded
  • Each rule triggered in a lab and the alert confirmed in logs
  • Priorities set appropriately (CRITICAL for escape primitives)
  • Alerts forwarded to the SIEM via Falcosidekick
  • Rule tags include the relevant MITRE technique IDs

© mukul975, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (scripts, references) in skills/detecting-container-runtime-threats-with-falco of mukul975/Anthropic-Cybersecurity-Skills.

  • SKILL.md
  • LICENSE
  • references/api-reference.md
  • references/standards.md
  • scripts/agent.py

Open the folder on GitHubat commit 54a7988

Compare with similar skills

Detecting Container Runtime Threats With Falco 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 Runtime Threats With Falco compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Detecting Container Runtime Threats With Falco this skillmukul975/Anthropic-Cybersecurity-Skills34k—~3kAutomated safety check: WarnApache-2.0
LangBot Deployment Guidelangbot-app/LangBot18k—~1.5kAutomated safety check: NotesApache-2.0
Build Openshell Mxc WindowsNVIDIA/OpenShell16k—~4.9kAutomated safety check: PassApache-2.0
Devopsnicepkg/auto-company1952 repos~814Automated safety check: PassMIT
Debug Openshell ClusterNVIDIA/OpenShell16k—~20kAutomated safety check: NotesApache-2.0
Deepseek Harness Dockerrunzhliu/deepseek-harness-docker110—~2.7kAutomated safety check: NotesMIT

Similar skills

  • LangBot Deployment Guide

    langbot-app/LangBot

    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.

    18k GitHub stars~1.5k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • Official

    Maintain and validate OpenShell's build-only Windows MSVC lane for x64 and ARM64.

    16k GitHub stars~4.9k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Devops

    nicepkg/auto-company

    Deploy to Cloudflare (Workers, R2, D1), Docker, GCP (Cloud Run, GKE), Kubernetes (kubectl, Helm).

    195 GitHub starsUsed in 2 repos~814 tokens
    DevOps & CloudAuto-check passed
  • Debug Openshell Cluster

    NVIDIA/OpenShell

    Official

    Debug why an OpenShell gateway deployment is unhealthy, unreachable, or unable to create sandboxes.

    16k GitHub stars~20k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes
  • Deepseek Harness Docker

    runzhliu/deepseek-harness-docker

    Deploy, configure, verify, upgrade, and troubleshoot DeepSeek Harness with the community Docker, Docker Compose, rootless Podman, and Helm runtime, including the built-in Chromium/noVNC browser…

    110 GitHub stars~2.7k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes
  • Cleanup

    ericboy0224/learn-docker-and-k8s

    Clean up Docker resources created by the Learn Docker & K8s game.

    491 GitHub stars~454 tokensUpdated 6 mo ago
    DevOps & CloudAuto-check passed

More from mukul975/Anthropic-Cybersecurity-Skills

All 644 skills in this repo
  • Campaign Attribution Evidence Analysis

    mukul975/Anthropic-Cybersecurity-Skills

    Weighs infrastructure, TTP, malware code and timing evidence with the Diamond Model and competing hypotheses to reach a confidence-rated attribution.

    34k GitHub stars~2.3k tokensUpdated 1 mo ago
    Auto-check passed
  • Go Malware Analysis in Ghidra

    mukul975/Anthropic-Cybersecurity-Skills

    Walks through reverse engineering Go-compiled malware in Ghidra: parsing buildinfo and pclntab, recovering stripped function names and extracting dependencies.

    34k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed
  • LNK and Jump List Forensics

    mukul975/Anthropic-Cybersecurity-Skills

    Guides forensic analysis of Windows LNK shortcut files and Jump Lists with LECmd, JLECmd and manual parsing to show file access and program execution.

    34k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed
  • Malware Persistence Analysis with Autoruns

    mukul975/Anthropic-Cybersecurity-Skills

    Hunts Windows malware persistence with Sysinternals Autoruns, covering run keys, services, scheduled tasks and drivers, with baseline comparison.

    34k GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed
  • NTFS MFT Deleted File Recovery

    mukul975/Anthropic-Cybersecurity-Skills

    Guides a Windows forensic examination of the NTFS Master File Table to recover deleted-file evidence, build timelines and spot timestomping.

    34k GitHub stars~2.7k tokensUpdated 1 mo ago
    Auto-check passed
  • Network Covert Channel Analysis

    mukul975/Anthropic-Cybersecurity-Skills

    Detects DNS tunneling, ICMP exfiltration and HTTP-based covert channels in packet captures and DNS logs when hunting for hidden command-and-control traffic.

    34k GitHub stars~2k tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Detecting Container Runtime Threats With Falco

What does Detecting Container Runtime Threats With Falco do?

Deploys and operates Falco with the modern eBPF driver in Kubernetes and Docker, covering driver selection, Helm installation, output channels, and the built-in ruleset that detects container…. Detecting Container Runtime Threats With Falco is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Deploys and operates Falco with the modern eBPF driver in Kubernetes and Docker, covering driver selection, Helm installation, output channels, and the built-in ruleset that detects container escape, namespace abuse, privileged mounts, and anomalous syscalls.

When should I use Detecting Container Runtime Threats With Falco?

Detecting Container Runtime Threats With Falco fits situations like: standing Falco up on a cluster; choosing between the eBPF and kernel-module drivers; routing Falco alerts into a SIEM; upgrading an existing deployment.

How do I install Detecting Container Runtime Threats With Falco in Claude Code?

Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill detecting-container-runtime-threats-with-falco -a claude-code`. Or copy the skill folder (skills/detecting-container-runtime-threats-with-falco in mukul975/Anthropic-Cybersecurity-Skills) into .claude/skills/detecting-container-runtime-threats-with-falco in your project. Claude Code loads it when a task matches its description.

How do I install Detecting Container Runtime Threats With Falco in Codex?

Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill detecting-container-runtime-threats-with-falco -a codex`. Or copy the skill folder (skills/detecting-container-runtime-threats-with-falco in mukul975/Anthropic-Cybersecurity-Skills) into .agents/skills/detecting-container-runtime-threats-with-falco in your project. Codex loads it when a task matches its description.

Can I use Detecting Container Runtime Threats With Falco 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-runtime-threats-with-falco -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-runtime-threats-with-falco, .gemini/skills/detecting-container-runtime-threats-with-falco, .github/skills/detecting-container-runtime-threats-with-falco and .opencode/skills/detecting-container-runtime-threats-with-falco in your project.

What does Detecting Container Runtime Threats With Falco need to run?

Going by SKILL.md and its folder, Detecting Container Runtime Threats With Falco needs Python for the scripts in its folder and the command-line tools its instructions call (helm, kubectl, apt-get and curl). Our summary lists: Python 3; Docker.

Does Detecting Container Runtime Threats With Falco access the network?

SKILL.md names 4 domains. In commands or code: falco.org, falcosecurity.github.io and download.falco.org; the agent is likely to contact these when it follows the instructions. As links in the text: github.com. This is read from the text; nothing was executed.

Is Detecting Container Runtime Threats With Falco safe to install?

Our automated static check of SKILL.md flagged 1 warning(s): mentions a credentials file (ssh keys, cloud or package-manager tokens). Read the flagged lines before installing; the check is not a guarantee either way. 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 Runtime Threats With Falco use?

Detecting Container Runtime Threats With Falco 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 Runtime Threats With Falco use?

About 3k 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.1k tokens, read only when the agent opens those files.

What are the alternatives to Detecting Container Runtime Threats With Falco?

Skills that share tags, products or a category with Detecting Container Runtime Threats With Falco: LangBot Deployment Guide (langbot-app/LangBot, 18k stars), Build Openshell Mxc Windows (NVIDIA/OpenShell, 16k stars), Devops (nicepkg/auto-company, 195 stars) and Debug Openshell Cluster (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 Runtime Threats With Falco?

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.

Source: mukul975/Anthropic-Cybersecurity-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.