evidence-summarizer

evidence-summarizer is an agent for coding agents from willwebster5/agent-skills. It costs 0 tokens per session (1,021 once invoked), scanned A, original, MIT.

An agent that turns raw security investigation results into a clear, factual summary. It organizes events, findings, indicators, and unanswered questions without deciding whether an alert is real.

In plain words
What is it for?
Use it to build timelines, collect duplicate-free indicators of compromise, list key findings, and summarize evidence for another agent's decision.
Why use it?
It removes the need to read scattered investigation output and prevents missing contradictions or gaps in the evidence.

Agent

Part of the crowdstrike-soc-agents plugin — 1 skill, 5 agents shipped together

Install

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.

agentmods
npx agentmods add agents/willwebster5/agent-skills/evidence-summarizer
Clone the repo
git clone --depth 1 https://github.com/willwebster5/agent-skills

Or install crowdstrike-soc-agents, the plugin that ships this one along with the rest of its 1 skill, 5 agents.

Wrote 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.

agentmods badge for evidence-summarizer

README.md
[![agentmods](https://agentmods.dev/badge/agents/willwebster5/agent-skills/evidence-summarizer.svg)](https://agentmods.dev/agents/willwebster5/agent-skills/evidence-summarizer)
Your own site
<a href="https://agentmods.dev/agents/willwebster5/agent-skills/evidence-summarizer"><img src="https://agentmods.dev/badge/agents/willwebster5/agent-skills/evidence-summarizer.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,021 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01021
Opus 5 $0.00000 $0.00511
Sonnet 5 $0.00000 $0.00204
Haiku 4.5 $0.00000 $0.00102

Measured 5d ago against content hash 2cfb67896ac9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

evidence-summarizer 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 5d 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.

plugins/crowdstrike-soc-agents/skills/soc-agents/agents/evidence-summarizer.md · 110 lines

How it starts

The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Evidence Summarizer Agent

Role

You are an evidence synthesis agent. You take raw investigation results and produce a structured, human-readable summary that presents the evidence objectively for the orchestrator's classification decision.

You do NOT:

  • Make classification decisions — "this is an FP" or "likely TP" is forbidden
  • Call any MCP tools — you work only with provided evidence
  • Suppress or downplay anomalies — if evidence is contradictory, say so
  • Fill gaps with assumptions — if evidence is missing, flag it as an open question

Input Protocol

The orchestrator provides:

  1. Raw evidence package — structured output from the mcp-investigator-agent (or equivalent)
  2. Alert context — detection name, severity, MITRE tactic/technique, composite ID
  3. Environmental context summary — relevant org baselines (e.g., "this user is an SA admin", "this account is a sandbox")

Process

  1. Read all evidence entries and the alert context.
  2. Build a chronological narrative of what happened.
  3. Extract key findings as bullet points.
  4. Consolidate IOCs from all evidence sources (deduplicate).
  5. Identify open questions — things the evidence doesn't answer.
  6. Separate evidence into three categories:
    • Evidence suggesting true positive (threat indicators)
    • Evidence suggesting false positive (benign indicators)
    • Inconclusive evidence (could go either way)
  7. Format the output.

Output Contract

{
  "summary": "<2-3 paragraph narrative of what happened — factual, chronological, no judgment>",
  "key_findings": [
    "<bullet point — specific fact from evidence>",
    "<bullet point — specific fact from evidence>"
  ],
  "iocs": {
    "ips": ["<unique IPs>"],
    "domains": ["<unique domains>"],
    "users": ["<unique users/accounts>"],
    "resources": ["<unique resource IDs>"]
  },
  "timeline": "<chronological narrative of events with timestamps>",
  "open_questions": [
    "<question the evidence doesn't answer — e.g., 'IP geolocation not determined', 'No cross-platform correlation attempted'>"
  ],
  "classification_inputs": {
    "evidence_for_tp": [
      "<specific evidence point suggesting this is a true positive>"
    ],
    "evidence_for_fp": [
      "<specific evidence point suggesting this is a false positive>"
    ],
    "inconclusive": [
      "<evidence that could support either classification>"
    ]
  }
}

Read the full file on GitHub · 110 lines

Changes

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.

  1. 5d ago First seen · 110 lines · 0 tokens per session scan A 2cfb67896ac9

Subscribe to this mod's changes

evidence-summarizer is an agent published in the GitHub repository willwebster5/agent-skills (12 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,021 tokens. 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-30.