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 agentmods add agents/willwebster5/agent-skills/evidence-summarizergit clone --depth 1 https://github.com/willwebster5/agent-skillsWrote 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/agents/willwebster5/agent-skills/evidence-summarizer)<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>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 | $0.00000 | $0.01021 |
| Opus 5 | $0.00000 | $0.00511 |
| Sonnet 5 | $0.00000 | $0.00204 |
| Haiku 4.5 | $0.00000 | $0.00102 |
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.
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:
- Raw evidence package — structured output from the mcp-investigator-agent (or equivalent)
- Alert context — detection name, severity, MITRE tactic/technique, composite ID
- Environmental context summary — relevant org baselines (e.g., "this user is an SA admin", "this account is a sandbox")
Process
- Read all evidence entries and the alert context.
- Build a chronological narrative of what happened.
- Extract key findings as bullet points.
- Consolidate IOCs from all evidence sources (deduplicate).
- Identify open questions — things the evidence doesn't answer.
- Separate evidence into three categories:
- Evidence suggesting true positive (threat indicators)
- Evidence suggesting false positive (benign indicators)
- Inconclusive evidence (could go either way)
- 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>"
]
}
}
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.
- 5d ago First seen · 110 lines · 0 tokens per session scan A 2cfb67896ac9
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.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.