severity-scoring skillA
severity-scoring is agent-read markdown (skill) from gensecaihq/wazuh-autopilot: Compute a defensible priority (P1–P4), severity and confidence for a case from rule level, asset criticality, blast radius and ATT&CK tactic; use whenever you set or change case severity..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Severity Scoring Severity must be explainable. Use this formula, then sanity-check it. ## Inputs (each scored 0–10) | Factor | Weight | How to score | |---|---|---| | Rule level (L) | 0.30 | `min(10, rule.level * 10 / 15)` using the highest level in the case (see note below) | | Asset criticality (A) | 0.25 | 10 crown-jewel / domain controller / prod DB; 7 prod server; 4 internal workstation; 2 lab/test | | Tactic weight (T) | 0.20 | see table below, highest tactic present | | Blast radius (B) | 0.15 | 1 host = 2; 2–5 hosts = 5; >5 hosts or domain-wide identity = 9; org-wide = 10 | | Evidence strength (E) | 0.10 | 10 confirmed success (e.g. login after brute force, file dropped); 5 attempt; 2 anomaly only | `score = 0.30L + 0.25A + 0.20T + 0.15B + 0.10E` ### About Wazuh levels Wazuh levels describe the rule, not your environment. Some are misleading in context: - High-level rules can be environmental or operational. For example, rule 204 (agent event queue flooded, level 12) is a pipeline problem, and rule 1003 (oversized syslog message, level 13) is often a misbehaving device. Keep L from the level, but score E low unless there is attacker evidence. …
Read the whole file at its exact version.
How to install
mdr add gensecaihq/wazuh-autopilot/severity-scoring@v1.1mdr add gensecaihq/wazuh-autopilot/severity-scoring@sha256:5ae1b5860c231640Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_5hh4l3z7a2tptr7f)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3837 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
gensecaihq/wazuh-autopilot · 57 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5hh4l3z7a2tptr7f GET https://markdownregistry.com/api/v1/resolve?ref=gensecaihq/wazuh-autopilot/severity-scoring GET https://markdownregistry.com/api/v1/blob/5ae1b5860c23164063eb639411a167e6893346701a23a30d69ea8eb8c3d9a8e5
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.