Identify which processes, connections, and remote hosts are actually using bandwidth before you chase the wrong incident hypothesis.
Scanned 6/8/2026
Install via CLI
openskills install agentskillexchange/skills---
name: "Trace which local processes and hosts are consuming bandwidth during incidents with bandwhich"
slug: "trace-which-local-processes-and-hosts-are-consuming-bandwidth-during-incidents-with-bandwhich"
description: "Identify which processes, connections, and remote hosts are actually using bandwidth before you chase the wrong incident hypothesis."
github_stars: 11691
verification: "security_reviewed"
source: "https://github.com/imsnif/bandwhich"
author: "imsnif"
publisher_type: "individual"
category: "Runbooks & Diagnostics"
framework: "Multi-Framework"
tool_ecosystem:
github_repo: "imsnif/bandwhich"
github_stars: 11691
---
# Trace which local processes and hosts are consuming bandwidth during incidents with bandwhich
Identify which processes, connections, and remote hosts are actually using bandwidth before you chase the wrong incident hypothesis.
## Prerequisites
bandwhich CLI, network interface access, elevated privileges on Linux
## Installation
Use the upstream install or setup path that matches your environment:
- git clone https://github.com/imsnif/bandwhich.git
- cargo build --release
- cargo install --git https://github.com/cross-rs/cross.git cross
Requirements and caveats from upstream:
- Since bandwhich sniffs network packets, it requires elevated privileges.
- Require privilege escalation every time.
Basic usage or getting-started notes:
- [Usage](#usage)
- ### Downstream packaging status
- For detailed instructions for each platform, see [INSTALL.md](INSTALL.md).
- Source: https://github.com/imsnif/bandwhich
- Extracted from upstream docs: https://raw.githubusercontent.com/imsnif/bandwhich/HEAD/README.md
## Documentation
- https://github.com/imsnif/bandwhich
## Source
- [Agent Skill Exchange](https://agentskillexchange.com/skills/trace-which-local-processes-and-hosts-are-consuming-bandwidth-during-incidents-with-bandwhich/)
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.