Instructions for bx33661/Wireshark-MCP: For packet capture, protocol analysis, network security monitoring, incident response, and troubleshooting tasks, prefer the project skill in .github/skills/wireshark-traffic-analysis/.
Instructions for bx33661/Wireshark-MCP: For packet capture and traffic-analysis work in this repository, load the project skill from .claude/skills/wireshark-traffic-analysis/SKILL.md.
Use when analyzing packet captures or live network traffic with Wireshark MCP; choose the right workflow for triage, security hunting, incident response, or troubleshooting, then produce evidence-backed findings with exact filters, streams, frames, and next steps.
CVSS v3.1 vector and score computation agent for oh-my-vul. Use during omv-audit and omv-report to derive a CVSS vector from a finding's evidence. Operates purely from provided impact fields and the cvss-builder reference — no network, no file access beyond the reference. Refuses to inflate severity and treats unknown…
Source → sink → guard dataflow analysis agent for oh-my-vul. Use during omv-find and omv-audit to inspect 2-5 source files per candidate and build a concrete dataflow note with file:line references. Static analysis only — never executes code. Also writes the ThreatMap.v1 sidecar for confirmed findings.
Duplicate advisory detection agent for oh-my-vul. Use during omv-report, omv-dedup, and omv-critic to search NVD, GitHub Security Advisories, and ecosystem-specific databases for existing CVEs/advisories before a report is written. Refuses to invent CVE IDs and marks unreachable searches as not-searched rather than…
Adversarial guard/bypass assessment agent for oh-my-vul. Use after dataflow-tracer has identified a candidate source→sink chain to independently assess whether an existing guard actually prevents exploitation. Biased toward finding bypasses — only concedes "guard is effective" when bypass truly cannot be constructed.
Platform-specific advisory rendering agent for oh-my-vul. Use during omv-report to render VulDB, GHSA, OSV JSON, or Markdown advisory formats from a confirmed Evidence.v1 object. Refuses to produce submission-ready output when submissionscore < 75 and refuses entirely for blocked findings.
Adversarial verification agent for oh-my-vul. Use after dataflow-tracer and guard-checker have produced a candidate audit conclusion, to independently refute it. The default stance is skeptical — assume the conclusion is wrong and find evidence supporting that. Only concedes agreement when refutation genuinely fails.…
Passive candidate discovery agent for oh-my-vul. Use proactively during omv-find to scan public GitHub search results and registry metadata for packages worth auditing. Reads public sources only — does not clone, run live exploit attempts, or execute code.
Deep-audits a candidate finding from an Evidence.v1 file. Use when the user has an omv-find result they want to investigate further, wants to prove or disprove a vulnerability, needs to fill Evidence.v1 fields for omv-report, or invokes /omv-audit. Reads .omv/findings/ .yaml and produces a confirmed or blocked finding…
Performs adversarial pre-submission review of an Evidence.v1 finding plus optional ThreatMap.v1 and Verification.v1 sidecars. Use before /omv-report when the user wants likely CNA rejection reasons, report argument quality review, a rejectrisk rating, or a recommendation of which researchergoal (VulDB, CVE, GHSA…
Checks whether an Evidence.v1 finding is likely already disclosed. Use when the user asks to deduplicate a finding, check CNA duplicate risk, search NVD/GHSA/OSV/ecosystem advisory databases or public discussion (issues, PRs, commits, blogs), or invokes /omv-dedup. Produces deterministic queries, grades novelty risk…
Helps prepare responsible disclosure communications and timelines from an Evidence.v1 finding. Use when the user asks to contact a vendor, create initial/follow-up/deadline disclosure email templates, plan a 90-day timeline, record disclosure fields, or invokes /omv-disclose.
Finds and ranks open-source packages worth auditing for passive CVE/VulDB research. Use when the user asks for vulnerability research targets, CVE hunting candidates, packages to audit, projects to fuzz, or /omv-find. Supports npm, Python, Go, Rust, Java, Ruby, PHP, C#, Swift, Dart, Elixir, Perl, R, and Lua, with…
Variant-driven diffusion hunting for oh-my-vul. Use when the user has a confirmed or publicly disclosed vulnerability pattern and wants to find the same bug class in sibling packages, forks, or downstream consumers; also when they ask for watchlist maintenance, radar brief, or /omv-radar. Reads seeds from findings and…
Guides a researcher through local reproduction of a vulnerability finding. Use when the user has an omv-audit result with evidence.reproducer filled but evidence.observedresult still unknown, wants to confirm a finding by running it locally, or invokes /omv-repro. Reads .omv/findings/ .yaml and guides step-by-step…
Bootstrap discipline for oh-my-vul research. Use at the start of any vulnerability research conversation, when the user asks to audit/find/report a package, dig for CVEs, or run omv skills — and before claiming a finding is confirmed, ready to submit, or “done”. Establishes mandatory process, hard gates, and…