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 vectra-ai-research/vectra-soc-agent-starter --skill vectra-pcapgit clone --depth 1 https://github.com/vectra-ai-research/vectra-soc-agent-starterWrote 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/vectra-ai-research/vectra-soc-agent-starter/vectra-pcap)<a href="https://agentmods.dev/skills/vectra-ai-research/vectra-soc-agent-starter/vectra-pcap"><img src="https://agentmods.dev/badge/skills/vectra-ai-research/vectra-soc-agent-starter/vectra-pcap/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/vectra-ai-research/vectra-soc-agent-starter/vectra-pcap"><img src="https://agentmods.dev/badge/skills/vectra-ai-research/vectra-soc-agent-starter/vectra-pcap.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.00142 | $0.02926 |
| Opus 5 | $0.00071 | $0.01463 |
| Sonnet 5 | $0.00028 | $0.00585 |
| Haiku 4.5 | $0.00014 | $0.00293 |
Grade A, and why
vectra-pcap 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 12d 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vectra PCAP — Detection PCAP Retrieval & Local Triage
This skill bridges Vectra's per-detection PCAP attachment to a local
tshark triage pass. It does two things:
- Pull the PCAP for a given
detection_idby calling the Vectra MCP toolvectra-ai-mcp:get_detection_pcap, decoding the base64 response, and writing the bytes to disk. - Triage the resulting capture file with
scripts/pcap-context.sh— a single tshark-driven helper that emits TLS metadata plus HTTP / Windows / SSH auth, SMB shares, RPC, DNS, andProcessCommandLineindicators in one pass, formatted for analyst review and pipe-friendly JSON.
The output feeds back into the detection's verdict (the
vectra-investigator Step 5 / matching playbook-<category>.md
evidence column). PCAP-derived signals do not override Vectra's
behavioral verdict — they corroborate or refute it.
Use this skill when
- The user names a specific Vectra detection and asks "show me the packets" / "pull the PCAP" / "what's actually on the wire".
- A
vectra-investigatorplaybook-<category>.mdneeds a 5-tuple confirmation, a TLS SNI, an SMB share name, or a Kerberos principal that the Vectra metadata view doesn't surface directly. - A
vectra-huntrecipe lands on a suspicious detection and the user wants to confirm the conversation contents (e.g. failed NTLM auth, unusual ALPN, large HTTP POST) before escalating. - The user has a PCAP on disk already (from another tool) and wants the
same structured triage (
scripts/pcap-context.sh <file>works standalone — the MCP fetch is optional).
Do not use this skill to:
- Pull a PCAP for a cloud / log-based detection (M365, Azure AD,
AWS, Entra). Those have no underlying capture — the Vectra API
returns
406 Not Acceptable. Route back tovectra-investigator(which will load the matching cloudplaybook-<category>.md). - Do live capture. Local
tshark/tcpdumpagainst the analyst host is out of scope here. - Override the Vectra behavioral verdict. PCAP evidence is corroboration, not a kill switch.
- Hunt across the tenant. Use
vectra-huntfor metadata-level queries that often answer the same question without leaving the platform.
What ships with it
4 files 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.
- 12d ago First seen · 241 lines · 142 tokens per session scan A b2b5c425cab4
vectra-pcap is a skill published in the GitHub repository vectra-ai-research/vectra-soc-agent-starter (2 stars, last pushed 3d ago), licensed MIT. It adds 142 tokens to every session and 2,926 once invoked, about $0.0007 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-08-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.