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 bx33661/Wireshark-MCP --skill tshark-cli-analysisgit clone --depth 1 https://github.com/bx33661/Wireshark-MCPWrote 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/bx33661/wireshark-mcp/tshark-cli-analysis)<a href="https://agentmods.dev/skills/bx33661/wireshark-mcp/tshark-cli-analysis"><img src="https://agentmods.dev/badge/skills/bx33661/wireshark-mcp/tshark-cli-analysis/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/bx33661/wireshark-mcp/tshark-cli-analysis"><img src="https://agentmods.dev/badge/skills/bx33661/wireshark-mcp/tshark-cli-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00052 | $0.00718 |
| Opus 5 | $0.00026 | $0.00359 |
| Sonnet 5 | $0.00010 | $0.00144 |
| Haiku 4.5 | $0.00005 | $0.00072 |
Grade A, and why
tshark-cli-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 3d 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Traffic Investigation — TShark CLI
This is the direct-execution companion to the MCP workflow. It remains a locally usable prototype pending comparative evaluation; it does not require the MCP skill to be installed.
Select the smallest investigation
Identify the capture and question from context. For unknown input, inspect metadata and a compact protocol summary. For a known frame, endpoint, or symptom, start with that scope. Use a query that would distinguish the leading explanation from its strongest alternative; simple lookups need no hypothesis exercise.
Reuse successful queries while input and decoding settings are unchanged. Stop when the question is answered or the remaining uncertainty requires unavailable packets, keys, or external observations. Do not launch a broad audit or live capture merely to fill a template.
Execution contract
Use tshark --version and discover optional capinfos only when needed. Verify uncertain fields against the installed engine's -G fields output; cache that glossary outside model context and search exact field abbreviations. Missing optional utilities should not block otherwise available analysis.
Use argument arrays in subprocess code; when using a shell, quote paths and pass the entire display filter as one argument. Use -n to avoid unnecessary name resolution. Keep capture filters (-f) distinct from display filters (-Y). Read commands.md for executable patterns and output/occurrence semantics.
Do not infer a whole-capture count from head, a selected page, or -c: -c limits packets read, including packets rejected by the display filter. An early-terminated pipeline is partial even if its final command succeeds. For global statistics, finish the scan into a bounded summary or a size-monitored local artifact, check tshark's exit status and stderr, then inspect only relevant results.
Apply a timeout and output/storage budget suited to the capture. On overflow, terminate and reap the subprocess, mark the scan partial, and narrow the query. Do not rerun the same failing command unchanged. Streaming a pipeline alone does not prove bounded memory or a complete scan.
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.
- 3d ago First seen · 37 lines · 52 tokens per session scan A 4b8165a3d700
tshark-cli-analysis is a skill published in the GitHub repository bx33661/Wireshark-MCP (236 stars, last pushed 4d ago), licensed MIT. It adds 52 tokens to every session and 718 once invoked, about $0.0003 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-06.
Other skills, from other repositories
analyzing-network-traffic-with-wireshark
Captures and analyzes network packet data using Wireshark and tshark to identify malicious traffic patterns, diagnose protocol issues, extract artifacts, and support incident response investigations on authorized network segments.
analyzing-network-traffic-with-wireshark
A guide for using Wireshark and tshark to capture and inspect network packets. Packets are the small pieces of data sent across a network; the guide focuses on authorized troubleshooting and security investigations.
analyzing-network-traffic-with-wireshark
Captures and analyzes network packet data using Wireshark and tshark to identify malicious traffic patterns, diagnose protocol issues, extract artifacts, and support incident response investigations on authorized network segments.
analyzing-network-traffic-with-wireshark
Captures and analyzes network packet data using Wireshark and tshark to identify malicious traffic patterns, diagnose protocol issues, extract artifacts, and support incident response investigations on authorized network segments.
analyzing-network-traffic-with-wireshark
Captures and analyzes network packet data using Wireshark and tshark to identify malicious traffic patterns, diagnose protocol issues, extract artifacts, and support incident response investigations on authorized network segments.
analyzing-network-traffic-with-wireshark
Captures and analyzes network packet data using Wireshark and tshark to identify malicious traffic patterns, diagnose protocol issues, extract artifacts, and support incident response investigations on authorized network segments.