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 Vigil-SOC/vigil --skill findings-and-telemetrygit clone --depth 1 https://github.com/Vigil-SOC/vigilWrote 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/vigil-soc/vigil/findings-and-telemetry)<a href="https://agentmods.dev/skills/vigil-soc/vigil/findings-and-telemetry"><img src="https://agentmods.dev/badge/skills/vigil-soc/vigil/findings-and-telemetry/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/vigil-soc/vigil/findings-and-telemetry"><img src="https://agentmods.dev/badge/skills/vigil-soc/vigil/findings-and-telemetry.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.00023 | $0.00271 |
| Opus 5.5 | $0.00009 | $0.00108 |
| Sonnet 5.5 | $0.00005 | $0.00054 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
findings-and-telemetry 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 2d 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
Findings and telemetry
You have two surfaces and they answer different questions.
Vigil's findings are what detection already scored: one record per alert or anomaly, carrying a severity, an anomaly score, predicted ATT&CK techniques and the entities involved. Search them to learn what has already been noticed.
Each search result names the hosts, users, addresses, domains, hashes, processes
and files its finding carries, under entities. Group findings by those: alerts
from different products that name one host or one user are one story, and a
host a finding names is a host you can rule on. When you need the record behind
an alert -- the command line, the parent process, the raw event -- open it with
get_finding, one finding at a time, for the few that matter.
The telemetry search, when this deployment has one, reaches the raw records behind those findings, in the SIEM's own query language. Go there for anything a detection did not already summarise -- volumes, intervals, who talked to whom.
Start from the findings and go to the telemetry to characterise what you found. A hypothesis that spans domains needs both.
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.
- 2d ago First seen · 27 lines · 23 tokens per session scan A 39d4376ada6e
findings-and-telemetry is a skill published in the GitHub repository Vigil-SOC/vigil (374 stars, last pushed today), licensed Apache-2.0. It adds 23 tokens to every session and 271 once invoked, about $0.0001 per session on Opus 5.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-10-15.
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.
scrape-batch
Extract many known URLs in one polite, rate-limited pass. Use when the user hands over a list of links, a set of search hits to read in full, or asks to "scrape these pages" / "pull the content from all of them". Drives extract(action="batch"), which fans out with per-domain rate limiting and returns partial results…
compare
Structured comparison of 2+ alternatives with consistent criteria and decision matrix.
research-topic
Multi-step research orchestration. Use when user asks "research X", "summarize current state of Y", "what's the latest on Z", or compares approaches. Calls extract(action="agent") which searches the web, extracts top results, then synthesises a citation-preserving Markdown answer with one configured LLM.
temporal-query
Answer time-travel questions over stored memory — what was believed at a past point in time, when a belief changed, and what replaced it. Use when the user says "as of", "back in", "at the time", "history of", "timeline", "what did I think then", or asks why a current memory contradicts an older one.
knowledge-audit
Review and clean up stored memories — find duplicates, contradictions, stale entries, and consolidate.