soc-metrics

soc-metrics is a skill for Claude Code from gensecaihq/Wazuh-Autopilot. It costs 56 tokens per session (859 once invoked), scanned A, original, MIT.

A guide to measuring security operations centre (SOC) performance. It explains metrics such as time to detect, acknowledge, contain and resolve incidents, along with false-positive and automation rates.

In plain words
What is it for?
Use it to prepare KPI reports, compare performance over time, and answer questions about alert quality, response speed, agent cost and latency.
Why use it?
It helps teams calculate these measures consistently and avoid misleading reports based only on averages or raw alert counts. It also adds context about the SOC's level of maturity.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it to prepare KPI reports, compare performance over time, and answer questions about alert quality, response speed, agent cost and latency.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gensecaihq/wazuh-autopilot/soc-metrics
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.

Any agent
npx skills add gensecaihq/Wazuh-Autopilot --skill soc-metrics
Clone the repo
git clone --depth 1 https://github.com/gensecaihq/Wazuh-Autopilot

Made for: Claude Code.

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 soc-metrics

README.md
[![agentmods](https://agentmods.dev/badge/skills/gensecaihq/wazuh-autopilot/soc-metrics/github.svg)](https://agentmods.dev/skills/gensecaihq/wazuh-autopilot/soc-metrics)
Your own site
<a href="https://agentmods.dev/skills/gensecaihq/wazuh-autopilot/soc-metrics"><img src="https://agentmods.dev/badge/skills/gensecaihq/wazuh-autopilot/soc-metrics/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.

agentmods 80×15 button for soc-metrics

Your own site · 80×15
<a href="https://agentmods.dev/skills/gensecaihq/wazuh-autopilot/soc-metrics"><img src="https://agentmods.dev/badge/skills/gensecaihq/wazuh-autopilot/soc-metrics.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 859 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00056 $0.00859
Opus 5.5 $0.00022 $0.00344
Sonnet 5 $0.00011 $0.00172
Haiku 4.5 $0.00006 $0.00086

Measured yesterday against content hash 6c9f5f05bdd4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-26, from the pricing page.

Security

Grade A, and why

soc-metrics 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 yesterday.

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.

backend/app/skills/soc-metrics/SKILL.md · 72 lines

How it starts

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

SOC Metrics

Metrics should drive improvement, not vanity. Define precisely, compute consistently, and always show the trend and the sample size.

Time metrics (per incident, then median and p90 over the period)

Metric Definition Start → End
MTTD — mean time to detect how long the attacker was active before detection first malicious activity → first alert
MTTA — mean time to acknowledge time until someone (agent or human) started work case created → first triage finding
MTTC — mean time to contain time to stop the harm case created → containment verified
MTTR — mean time to respond/resolve time to close out case created → resolved/closed

Report median and p90 alongside the mean — a few long incidents skew means. MTTD requires an incident timeline; mark it "n/a" where the start of malicious activity is unknown.

Volume and quality

Metric Formula Healthy signal
Alert-to-incident ratio alerts ingested ÷ cases opened falling over time with stable coverage
False-positive rate cases closed false_positive ÷ cases closed trending down; > 50% means tuning needed
Escalation rate cases reaching investigation ÷ cases opened stable, explainable
Automation rate actions auto-approved or auto-executed ÷ all executed actions increases only with low rollback rate
Rollback rate actions rolled back ÷ executed < 5%; spikes mean over-aggressive autonomy
Verification rate executed actions verified ÷ executed → 100%
Approval latency action proposed → approved (median) within policy expiry
Agent coverage active Wazuh agents ÷ expected assets → 100%
Telemetry loss alerts for rule 203 (event queue full) or rule 204 (queue flooded), and agents disconnected for > 1h (rule 504) zero; any non-zero means detection blind spots. Get detail from platform-engineer
MTTD first attacker event time (from the log, not the alert timestamp) → case opened falling; ingestion delay shows up as the gap between event time and alert time

Read the full file on GitHub · 72 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. yesterday First seen · 72 lines · 56 tokens per session scan A 6c9f5f05bdd4

Subscribe to this mod's changes

soc-metrics is a skill published in the GitHub repository gensecaihq/Wazuh-Autopilot (57 stars, last pushed 2d ago), licensed MIT. It adds 56 tokens to every session and 859 once invoked, about $0.0002 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-25.