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 agentmods add skills/batteryshark/rekit/net-capturenpx skills add batteryshark/rekit --skill net-capturegit clone --depth 1 https://github.com/batteryshark/rekitWrote 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/batteryshark/rekit/net-capture)<a href="https://agentmods.dev/skills/batteryshark/rekit/net-capture"><img src="https://agentmods.dev/badge/skills/batteryshark/rekit/net-capture.svg" alt="Measured on agentmods" 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 | $0.00069 | $0.00383 |
| Opus 5 | $0.00034 | $0.00192 |
| Sonnet 5 | $0.00014 | $0.00077 |
| Haiku 4.5 | $0.00007 | $0.00038 |
Grade B, and why
net-capture scanned grade B with 1 finding 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 4d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- **`tcpdump`** on PATH; **capturing usually needs root** (sudo / capture caps). Absent What it actually says
Network Capture
⚡ Dynamic tier — runs the target and sniffs the wire. Run only where you don't mind the risk (ideally an isolated/sinkholed network).
When to use
You want to see what a sample talks to — C2, exfil, downloads. net-capture runs it
while capturing the interface, then shows the IPs it reached and DNS it asked for, and
leaves a pcap for deeper analysis.
What it does
Starts tcpdump on an interface, runs the target for a bounded duration, stops the
capture, and summarizes: packet count, talkers (IPs), and DNS query lines. Writes the
full capture.pcap. For safe detonation, run inside a VM with a sinkholed/proxied
network and point --iface at it.
Consent & prerequisites
- Dynamic:
rekit run --allow-dynamic net-capture <target>(or--yes-i-consent/REKIT_ALLOW_DYNAMIC=1). tcpdumpon PATH; capturing usually needs root (sudo / capture caps). Absent or unprivileged → the runner reports the honest failure.
Usage
rekit run --allow-dynamic net-capture ./sample --iface eth0 --duration 20
Feed the recovered IPs/domains into ioc-extract.
What ships with it
1 file 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.
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.
- 4d ago First seen · 38 lines · 69 tokens per session scan B f4cbd4e6ce89
net-capture is a skill published in the GitHub repository batteryshark/rekit (11 stars, last pushed 26d ago), licensed Apache-2.0. It adds 69 tokens to every session and 383 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…