Borrowing it
Nothing to install: this file belongs to bx33661/Wireshark-MCP. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bx33661/Wireshark-MCP/main/.github/prompts/wireshark-traffic-analysis.prompt.mdgit 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/commands/bx33661/wireshark-mcp/wireshark-traffic-analysis)<a href="https://agentmods.dev/commands/bx33661/wireshark-mcp/wireshark-traffic-analysis"><img src="https://agentmods.dev/badge/commands/bx33661/wireshark-mcp/wireshark-traffic-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/commands/bx33661/wireshark-mcp/wireshark-traffic-analysis"><img src="https://agentmods.dev/badge/commands/bx33661/wireshark-mcp/wireshark-traffic-analysis.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.00000 | $0.00303 |
| Opus 5 | $0.00000 | $0.00151 |
| Sonnet 5 | $0.00000 | $0.00061 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
wireshark-traffic-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 5d 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.
What it actually says
Use the wireshark-traffic-analysis project skill in this repository to investigate a packet capture with a professional, evidence-backed workflow.
Inputs:
- Capture path:
${input:capture_path:Path to the pcap or pcapng file} - Goal:
${input:goal:triage | security | incident-response | troubleshoot} - Optional scope:
${input:scope:Suspicious host, protocol, time window, domain, stream, or symptom}
Requirements:
- Start with the supplied question; use broad triage only for unfamiliar captures.
- Use the project skill playbook that matches the goal.
- Use
wireshark_aggregatefor full-capture totals, grouped distributions, distinct counts, top-k, or time buckets. - Include exact filters, streams, frames, or extracted fields for every important finding.
- Label confidence as
confirmed,likely,candidate, orunresolved. - Check result coverage and errors before interpreting counts or absence.
- Stop when the question is answered; propose a next step only for an unresolved gap.
Relevant files:
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.
- 5d ago First seen · 25 lines · 0 tokens per session scan A 0aed3e1b7218
wireshark-traffic-analysis is a command published in the GitHub repository bx33661/Wireshark-MCP (237 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 303 tokens. 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 commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.