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 executive-summarygit 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/executive-summary)<a href="https://agentmods.dev/skills/vigil-soc/vigil/executive-summary"><img src="https://agentmods.dev/badge/skills/vigil-soc/vigil/executive-summary/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/executive-summary"><img src="https://agentmods.dev/badge/skills/vigil-soc/vigil/executive-summary.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.00073 | $0.00490 |
| Opus 5.5 | $0.00029 | $0.00196 |
| Sonnet 5.5 | $0.00015 | $0.00098 |
| Haiku 4.5 | $0.00007 | $0.00049 |
Grade A, and why
executive-summary 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 25d 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
Executive summary
-
Gather data via tools (cases, findings, actions)
-
Analyze context: severity, timeline, impact
-
Determine report type from user request:
TECHNICAL REPORT (default):
- Executive Summary: Business impact, plain language
- Technical Details: Evidence for security team
- Timeline: Chronological events
- Actions Taken: Response measures
- Recommendations: Next steps
EXECUTIVE SUMMARY:
- Tailor to executive audience, minimize technical jargon
BOARD BRIEF (triggered by "board brief", "board report", "risk posture report"):
- Follow the board-brief template:
read_skill("executive-summary", "assets/board-brief.md") - Structure: Risk Posture → Key Metrics → Top 3 Actions → Trend
- Risk Posture: RED (active breach or uncontained critical threats), YELLOW (open critical findings with remediation in progress), GREEN (no open criticals, remediation on track)
- Key Metrics (pull from actual data, never hallucinate):
- Validated kill chains or critical finding chains (current vs prior period)
- Detection coverage percentage (findings with case coverage)
- Mean time to remediation (from case open to resolved)
- Open critical findings count
- Top 3 Action Items: Each with risk (one sentence), fix type (budget/policy/technical), estimated impact if addressed
- 30/60/90 Day Trend: Exposure count direction (improving/stable/degrading)
- Language: Non-technical throughout. No CVE numbers, no ATT&CK IDs in the main body. Use plain business language.
- Length: One page equivalent. Brevity is mandatory.
- Output: Markdown for chat, note PDF export is available
-
Tailor to audience: Board/CEO vs Executive vs Technical vs Compliance
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.
- 25d ago First seen · 44 lines · 73 tokens per session scan A c25acffe8030
executive-summary is a skill published in the GitHub repository Vigil-SOC/vigil (374 stars, last pushed today), licensed Apache-2.0. It adds 73 tokens to every session and 490 once invoked, about $0.0003 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-09-22.
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.