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 eunomia-bpf/bpfix --skill ebpf-verifier-repairgit clone --depth 1 https://github.com/eunomia-bpf/bpfixWrote 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/eunomia-bpf/bpfix/ebpf-verifier-repair)<a href="https://agentmods.dev/skills/eunomia-bpf/bpfix/ebpf-verifier-repair"><img src="https://agentmods.dev/badge/skills/eunomia-bpf/bpfix/ebpf-verifier-repair/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/eunomia-bpf/bpfix/ebpf-verifier-repair"><img src="https://agentmods.dev/badge/skills/eunomia-bpf/bpfix/ebpf-verifier-repair.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.00134 | $0.01836 |
| Opus 5 | $0.00067 | $0.00918 |
| Sonnet 5 | $0.00027 | $0.00367 |
| Haiku 4.5 | $0.00013 | $0.00184 |
Grade A, and why
ebpf-verifier-repair 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 11d 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
eBPF Verifier Repair
Overview
Repair verifier failures as missing proof obligations, not as string-matched
terminal errors. A full verbose verifier log plus source is sufficient evidence
to start; use bpfix only when it is available and helpful. Make the smallest
verifier-visible source change that preserves program semantics and proves the
required safety fact to the kernel verifier.
Do not split work into one skill per verifier error family. BPFIX-E*,
failure_class, and next_action values are routing signals inside this
workflow; the reusable user job is "repair this verifier rejection."
Resource Routing
- Read
references/log-collection.mdwhen the user did not provide a full verbose verifier log, the log is incomplete, or the framework/loader command is unclear. - Read
references/raw-log-triage.mdwhenever repairing from a raw verifier log. Use its rejected-instruction and proof-lifecycle procedure before selecting a source rewrite. - Read
references/diagnostic-routing.mdonly when a BPFix diagnostic is provided or generated. Do not block raw-log repair on this file. - Read
references/repair-patterns.mdbefore editing source, selecting a verifier-visible rewrite, or reviewing a proposed patch. - Read
references/semantic-preservation.mdbefore editing a nontrivial program, especially when it updates maps, emits events, has fallback policy, or uses multiple acquired resources. - Read
references/failure-directed-retry.mdafter any candidate fails to compile, load, or pass the semantic oracle. Route the next edit by the failure stage instead of starting a new speculative repair. - Run
scripts/run-bpfix-diagnostic.shonly when BPFix is available and a repeatable plain-text diagnostic artifact would make the repair loop clearer. - Run
scripts/extract_verifier_failure.py verifier.logwhen a raw log is too large for the working context. Keep the original log and inspect omitted PCs when the initial slice does not reveal proof origin or loss.
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- .claude-plugin/plugin.json 477 B
- agents/openai.yaml 243 B
- references/diagnostic-routing.md 4.1 KB
- references/failure-directed-retry.md 2.1 KB
- references/log-collection.md 2.5 KB
- references/raw-log-triage.md 3.9 KB
- references/repair-patterns.md 9.7 KB
- references/semantic-preservation.md 2.9 KB
- scripts/extract_verifier_failure.py 2.4 KB runs code
- scripts/run-bpfix-diagnostic.sh 2.7 KB runs code
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.
- 11d ago First seen · 156 lines · 134 tokens per session scan A ea715d727ad9
ebpf-verifier-repair is a skill published in the GitHub repository eunomia-bpf/bpfix (19 stars, last pushed 1mo ago), licensed MIT. It adds 134 tokens to every session and 1,836 once invoked, about $0.0007 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-08-30.
Other skills, from other repositories
agentsight-system-friction
Analyze AgentSight system evidence to recommend operational improvements for agent runs.
ebpf-skill
Practical guidance for choosing, writing, loading, and debugging eBPF programs. Prioritizes correct toolchain and hook selection, map choice, kernel-version fit, verifier triage, and concise production-ready examples using libbpf, ebpf-go, and bpftrace.
uringscope
Diagnose iouring performance and correctness problems with uringscope, an eBPF tracer and analyzer. Use when a Linux process that uses iouring shows tail latency, unexplained iou-wrk- thread explosions, suspiciously syscall-heavy behavior, silent buffer corruption, or completions that never arrive, or when strace…
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.