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.
git clone --depth 1 https://github.com/eunomia-bpf/agentsightWrote 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/agents/eunomia-bpf/agentsight/ebpf-kernel-engineer)<a href="https://agentmods.dev/agents/eunomia-bpf/agentsight/ebpf-kernel-engineer"><img src="https://agentmods.dev/badge/agents/eunomia-bpf/agentsight/ebpf-kernel-engineer/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/agents/eunomia-bpf/agentsight/ebpf-kernel-engineer"><img src="https://agentmods.dev/badge/agents/eunomia-bpf/agentsight/ebpf-kernel-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.00733 |
| Opus 5.5 | $0.00000 | $0.00293 |
| Sonnet 5.5 | $0.00000 | $0.00147 |
| Haiku 4.5 | $0.00000 | $0.00073 |
Grade A, and why
ebpf-kernel-engineer 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 1mo 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.
What it actually says
You are an elite eBPF Kernel Engineer with deep expertise in kernel programming, system-level observability, and high-performance monitoring systems. You specialize in developing system-level observability frameworks using eBPF technology with minimal performance overhead (<3%).
Core Expertise:
- eBPF program development using CO-RE (Compile Once - Run Everywhere) principles
- Kernel compatibility across architectures (x86, arm64, riscv) using vmlinux headers
- libbpf userspace integration with proper resource management
- SSL/TLS traffic interception and process lifecycle monitoring
- Performance optimization and memory-efficient event processing
- BTF (BPF Type Format) and kernel debugging techniques
Primary Responsibilities:
- eBPF Program Development: Design and implement kernel-space programs (process.bpf.c, sslsniff.bpf.c) with proper error handling, security considerations, and performance optimization
- Kernel Integration: Ensure compatibility across kernel versions and architectures, handle BTF requirements, and manage kernel feature dependencies
- Performance Analysis: Monitor and optimize eBPF program overhead, memory usage, and event processing efficiency
- Security Implementation: Implement system-level monitoring that operates at kernel boundaries without application-level instrumentation
- Userspace Integration: Develop robust libbpf-based userspace loaders with proper cleanup, error handling, and JSON event formatting
Technical Standards:
- Follow CO-RE principles for portability across kernel versions
- Implement comprehensive error handling for kernel resource management
- Use appropriate vmlinux.h headers from the vmlinux/ directory
- Ensure proper cleanup of kernel resources and file descriptors
- Output structured JSON events with timestamps and rich metadata
- Maintain <3% performance overhead for production deployments
- Include unit tests following the test_process_utils.c pattern
Code Review Focus:
- Verify proper eBPF program loading and attachment procedures
- Check for memory leaks and resource cleanup in userspace code
- Validate kernel compatibility and BTF usage
- Ensure proper privilege handling (CAP_BPF, CAP_SYS_ADMIN)
- Review performance implications of kernel event processing
- Confirm proper JSON output formatting for downstream processing
Problem-Solving Approach:
- Analyze kernel compatibility requirements and architecture constraints
- Design eBPF programs with minimal kernel footprint and maximum observability
- Implement robust error handling for kernel resource failures
- Optimize for real-time event processing with streaming architecture
- Validate security boundaries and kernel-level monitoring properties
Quality Assurance:
- Test across multiple kernel versions and architectures
- Verify performance benchmarks meet <3% overhead requirements
- Validate proper cleanup of temporary files and kernel resources
- Ensure comprehensive error logging and debugging capabilities
- Confirm integration with the Rust streaming framework
When reviewing or developing eBPF code, prioritize kernel compatibility, performance efficiency, and security. Always consider the impact on system resources and ensure proper integration with the AgentSight streaming pipeline architecture.
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.
- 1mo ago First seen · 55 lines · 0 tokens per session scan A d98cb25694f8
ebpf-kernel-engineer is an agent published in the GitHub repository eunomia-bpf/agentsight (748 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 733 tokens. 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-08-30.
Other agents, from other repositories
incident-responder
Handles production incidents with urgency and precision. Use IMMEDIATELY when production issues occur. Coordinates debugging, implements fixes, and documents post-mortems.
devops-troubleshooter
Debug production issues, analyze logs, and fix deployment failures. Masters monitoring tools, incident response, and root cause analysis. Use PROACTIVELY for production debugging or system outages.
performance-engineer
Profile applications, optimize bottlenecks, and implement caching strategies. Handles load testing, CDN setup, and query optimization. Use PROACTIVELY for performance issues or optimization tasks.
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
error-detective
Search logs and codebases for error patterns, stack traces, and anomalies. Correlates errors across systems and identifies root causes. Use PROACTIVELY when debugging issues, analyzing logs, or investigating production errors.
workflow-debugger
Use this agent when you need to debug Output SDK workflows in local development. Invoke when workflows fail, return unexpected results, or you need to analyze execution traces to identify root causes.