wireshark-analysis

wireshark-analysis is a skill for Claude Code, Codex from zebbern/claude-code-guide. It costs 79 tokens per session (2,722 once invoked), scanned A, original, MIT.

A guide to analysing network traffic with Wireshark, a tool that captures and inspects network packets. It covers live captures and PCAP files, which are saved records of network traffic.

In plain words
What is it for?
Use it to troubleshoot connections, filter captures, follow TCP or UDP conversations, investigate incidents, analyse malware traffic, and study network protocols.
Why use it?
Network problems and security incidents can be hard to understand from application logs alone. Examining packets can reveal communication patterns, protocol errors, and suspicious activity.

Skill for Claude CodeCodex

About the project

Claude Code Guide is a reference collection for configuring and using Claude Code, Anthropic’s command-line coding agent. Developers use it to learn commands, skills, agents, MCP, automation, security, integrations, and troubleshooting. Its catalogue add-ons provide many of the documented skills and agents.

zebbern/claude-code-guide · 4,600 stars · on GitHub

Install

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.

agentmods
npx agentmods add skills/zebbern/claude-code-guide/wireshark-analysis
Any agent
npx skills add zebbern/claude-code-guide --skill wireshark-analysis
Clone the repo
git clone --depth 1 https://github.com/zebbern/claude-code-guide

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for wireshark-analysis

README.md
[![agentmods](https://agentmods.dev/badge/skills/zebbern/claude-code-guide/wireshark-analysis.svg)](https://agentmods.dev/skills/zebbern/claude-code-guide/wireshark-analysis)
Your own site
<a href="https://agentmods.dev/skills/zebbern/claude-code-guide/wireshark-analysis"><img src="https://agentmods.dev/badge/skills/zebbern/claude-code-guide/wireshark-analysis.svg" alt="Measured on agentmods" height="20"></a>
Per session 79 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,722 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00079 $0.02722
Opus 5 $0.00039 $0.01361
Sonnet 5 $0.00016 $0.00544
Haiku 4.5 $0.00008 $0.00272

Measured yesterday against content hash d2bd91505acc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

wireshark-analysis 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 yesterday.

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.

skills/wireshark-analysis/SKILL.md · 498 lines

How it starts

The opening of the file, as written. The whole thing — 498 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Wireshark Network Traffic Analysis

Purpose

Execute comprehensive network traffic analysis using Wireshark to capture, filter, and examine network packets for security investigations, performance optimization, and troubleshooting. This skill enables systematic analysis of network protocols, detection of anomalies, and reconstruction of network conversations from PCAP files.

Inputs / Prerequisites

Required Tools

  • Wireshark installed (Windows, macOS, or Linux)
  • Network interface with capture permissions
  • PCAP/PCAPNG files for offline analysis
  • Administrator/root privileges for live capture

Technical Requirements

  • Understanding of network protocols (TCP, UDP, HTTP, DNS)
  • Familiarity with IP addressing and ports
  • Knowledge of OSI model layers
  • Understanding of common attack patterns

Use Cases

  • Network troubleshooting and connectivity issues
  • Security incident investigation
  • Malware traffic analysis
  • Performance monitoring and optimization
  • Protocol learning and education

Outputs / Deliverables

Primary Outputs

  • Filtered packet captures for specific traffic
  • Reconstructed communication streams
  • Traffic statistics and visualizations
  • Evidence documentation for incidents

Core Workflow

Phase 1: Capturing Network Traffic

Start Live Capture

Begin capturing packets on network interface:

1. Launch Wireshark
2. Select network interface from main screen
3. Click shark fin icon or double-click interface
4. Capture begins immediately
Capture Controls
Action Shortcut Description
Start/Stop Capture Ctrl+E Toggle capture on/off
Restart Capture Ctrl+R Stop and start new capture
Open PCAP File Ctrl+O Load existing capture file
Save Capture Ctrl+S Save current capture
Capture Filters

Apply filters before capture to limit data collection:

# Capture only specific host
host 192.168.1.100

# Capture specific port
port 80

# Capture specific network
net 192.168.1.0/24

# Exclude specific traffic
not arp

# Combine filters
host 192.168.1.100 and port 443

Read the full file on GitHub · 498 lines

Changes

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.

  1. yesterday First seen · 498 lines · 79 tokens per session scan A d2bd91505acc

Subscribe to this mod's changes

wireshark-analysis is a skill published in the GitHub repository zebbern/claude-code-guide (4,600 stars, last pushed yesterday), licensed MIT. It adds 79 tokens to every session and 2,722 once invoked, about $0.0004 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.