Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add j4flmao/agent-skills --skill ebpf-networkinggit clone --depth 1 https://github.com/j4flmao/agent-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/j4flmao/agent-skills/ebpf-networking)<a href="https://agentmods.dev/skills/j4flmao/agent-skills/ebpf-networking"><img src="https://agentmods.dev/badge/skills/j4flmao/agent-skills/ebpf-networking/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/j4flmao/agent-skills/ebpf-networking"><img src="https://agentmods.dev/badge/skills/j4flmao/agent-skills/ebpf-networking.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00023 | $0.00613 |
| Opus 5 | $0.00012 | $0.00307 |
| Sonnet 5 | $0.00005 | $0.00123 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
eBPF Networking and Cilium Architecture scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cilium & eBPF Networking: Kernel Space Packet Processing
eBPF (Extended Berkeley Packet Filter) Fundamentals
eBPF allows sandboxed execution of user-defined bytecode within the Linux kernel. Programs are verified by the kernel's eBPF verifier to ensure safety (no infinite loops, bounds checking) and compiled via JIT (Just-In-Time) into native machine code. In networking, eBPF programs can be attached to various hooks (XDP, TC, cgroup socket hooks) to inspect, modify, or drop packets before they traverse the full kernel network stack.
XDP (eXpress Data Path) Hooks
XDP provides the earliest possible interception point in the Linux kernel network data path, executing eBPF programs directly within the network interface controller (NIC) driver (or even offloaded to hardware).
XDP_DROP: Discard packets at wire speed (ideal for DDoS mitigation).XDP_PASS: Pass packets to the standard network stack.XDP_TX: Bounce packets back out the same interface.XDP_REDIRECT: Forward packets to another interface or CPU queue.
Cilium Architecture
Cilium heavily utilizes eBPF and XDP to implement high-performance container networking, security policies, and load balancing (replacing kube-proxy). Cilium attaches eBPF programs to the TC (Traffic Control) ingress/egress hooks on virtual ethernet (veth) pairs associated with pods. This allows for identity-based security policies enforced via eBPF maps rather than iptables rules. When combined with XDP, Cilium provides DSR (Direct Server Return) for LoadBalancer services, bypassing the standard netfilter stack entirely.
Architecture Map
%%{init: {"theme": "default", "flowchart": {"useMaxWidth": true}}}%%
flowchart TD
NIC[Network Interface Card] -->|Driver RX| XDP[XDP eBPF Hook]
XDP -->|XDP_PASS| TC_Ingress[TC Ingress eBPF Hook]
XDP -->|XDP_DROP| Dropped[Packet Dropped - DDoS]
subgraph "Host Kernel Space"
TC_Ingress --> Routing[IP Routing Subsystem]
Routing --> TC_Egress[TC Egress eBPF Hook]
TC_Egress --> VethHost[Host Veth Interface]
end
VethHost -- Link --> VethPod[Pod Veth Interface]
CiliumAgent[Cilium Agent - User Space] -. "Updates BPF Maps" .-> TC_Ingress
CiliumAgent -. "Updates BPF Maps" .-> XDP
CiliumAgent -. "Listens to K8s API" .-> K8sAPI[Kubernetes API Server]
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 42 lines · 23 tokens per session scan A 2de72bf4e79a
eBPF Networking and Cilium Architecture is a skill published in the GitHub repository j4flmao/agent-skills (23 stars, last pushed 5d ago), licensed MIT. It adds 23 tokens to every session and 613 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
compute-env-setup
Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.
securing-kubernetes-on-cloud
This skill covers hardening managed Kubernetes clusters on EKS, AKS, and GKE by implementing Pod Security Standards, network policies, workload identity, RBAC scoping, image admission controls, and runtime security monitoring. It addresses cloud-specific security features including IRSA for EKS, Workload Identity for…
detecting-privilege-escalation-in-kubernetes-pods
Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.
implementing-rbac-hardening-for-kubernetes
Harden Kubernetes Role-Based Access Control by implementing least-privilege policies, auditing role bindings, eliminating cluster-admin sprawl, and integrating external identity providers.
docker-socket-mount
Docker / containerd socket mounted into a container → host RCE. Common in CI runners, GitOps controllers (ArgoCD, Flux), and 'Docker-in-Docker' setups. Single-command escape via docker run --rm --privileged -v /:/host alpine chroot /host.