Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/vectra-ai-research/vectra-soc-agent-starternpx agentmods add skills/vectra-ai-research/vectra-soc-agent-starter/vectra-reports-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/vectra-ai-research/vectra-soc-agent-starter/vectra-reports-mcp)<a href="https://agentmods.dev/skills/vectra-ai-research/vectra-soc-agent-starter/vectra-reports-mcp"><img src="https://agentmods.dev/badge/skills/vectra-ai-research/vectra-soc-agent-starter/vectra-reports-mcp/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-reports-mcp"><img src="https://agentmods.dev/badge/skills/vectra-ai-research/vectra-soc-agent-starter/vectra-reports-mcp.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.00202 | $0.03003 |
| Opus 5 | $0.00101 | $0.01502 |
| Sonnet 5 | $0.00040 | $0.00601 |
| Haiku 4.5 | $0.00020 | $0.00300 |
Grade A, and why
vectra-reports-mcp 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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vectra AI Reports (MCP channel)
Render canned, named, repeatable dashboards against a Vectra AI tenant
using the Vectra MCP server for all API calls. Each report is a YAML file
in definitions/ that bundles one or more SQL queries plus rendering
instructions (summary KPIs, tables, charts). You read the YAML, substitute
parameters into the SQL templates, call the MCP tools, and format the results.
No Python scripts, no venv, no pip install. The MCP server handles authentication, rate limiting, and query execution.
When to use this skill
Use only when the user explicitly names a canned report from the catalogue below. Examples:
- "Run the C2 beacon report for the last 24 h"
- "Render the top-talkers dashboard"
- "Show me the DNS error rate report, last 7 d"
- "Generate the zone-to-zone data transfer report"
- "Give me the daily threat summary"
The trigger is the report name, not the data domain. A report
can be named by its exact ID (protocol_distribution) or by its
catalog label phrased as a question ("what's the protocol
distribution across the network?", "show me active connections
right now"). Both count as a named trigger.
When NOT to use this skill
Reports are dashboards, not investigation tools. If the request is
investigative ("check CloudTrail", "what did this account do", "who's
behind this IP", "pivot from detection <id>", "investigate entity
<name>", "find Kerberoasting last 7 d", "sweep this CISA advisory"),
route to vectra-hunt instead. Both
vectra-reports-mcp and vectra-hunt go through the same MCP
run_investigation tool — the difference is the library and
intent (canned dashboard SQL vs investigation recipe library +
verdict workflow).
Full routing table lives in
reference/ROUTING.md — shared with
vectra-reports, so update it there.
If the user names neither a specific report nor a clear investigation question, list the available reports (from the catalogue below) and ask them to pick one — do not silently default to a generic report.
What ships with it
2 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 · 257 lines · 202 tokens per session scan A dcc280698a22
vectra-reports-mcp 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 202 tokens to every session and 3,003 once invoked, about $0.0010 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…