siem-rule

siem-rule is a skill for Claude Code, Codex from woohyun212/security-skill. It costs 37 tokens per session (3,346 once invoked), scanned B, original, MIT.

A guide for creating SIEM detection rules from threat goals, indicators of compromise, or vulnerability reports. SIEM systems collect and search security logs; this skill works with Sigma, Splunk SPL, Elastic KQL, and Sentinel KQL.

In plain words
What is it for?
Use it to create detections, convert Sigma rules, review existing rules, respond to new threats or CVEs, and recommend tuning for false positives.
Why use it?
It removes the need to write each detection separately for different security-monitoring platforms. It also helps check rules against sample logs and reduce noisy alerts.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to create detections, convert Sigma rules, review existing rules, respond to new threats or CVEs, and recommend tuning for false positives.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/woohyun212/security-skill/siem-rule
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 woohyun212/security-skill --skill siem-rule
Clone the repo
git clone --depth 1 https://github.com/woohyun212/security-skill

Made for: Claude Code, Codex.

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 siem-rule

README.md
[![agentmods](https://agentmods.dev/badge/skills/woohyun212/security-skill/siem-rule/github.svg)](https://agentmods.dev/skills/woohyun212/security-skill/siem-rule)
Your own site
<a href="https://agentmods.dev/skills/woohyun212/security-skill/siem-rule"><img src="https://agentmods.dev/badge/skills/woohyun212/security-skill/siem-rule/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 siem-rule

Your own site · 80×15
<a href="https://agentmods.dev/skills/woohyun212/security-skill/siem-rule"><img src="https://agentmods.dev/badge/skills/woohyun212/security-skill/siem-rule.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,346 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00037 $0.03346
Opus 5 $0.00018 $0.01673
Sonnet 5 $0.00007 $0.00669
Haiku 4.5 $0.00004 $0.00335

Measured 9d ago against content hash 360786f2a7ff, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade B, and why

siem-rule scanned grade B with 1 finding 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 9d 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

- `jq` for JSON manipulation: `sudo apt install jq`
siem-rule/SKILL.md · 332 lines

How it starts

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

What this skill does

Guides the full lifecycle of a SIEM detection rule: define the threat objective, identify required log sources, write a platform-agnostic Sigma rule, convert it to Splunk SPL, Elastic KQL/EQL, and Microsoft Sentinel KQL, validate against test data, and document tuning recommendations. Covers endpoint, network, identity, and cloud detection categories.

When to use

  • Building new detections from a threat model, IOC, or observed TTP
  • Converting an existing Sigma rule to a platform-specific query
  • Auditing existing rules for performance, fidelity, or coverage gaps
  • Responding to a new CVE or threat actor report and needing a fast rule
  • Reducing alert fatigue by tuning false-positive-heavy detections

Prerequisites

  • sigma-cli for rule conversion: pip install sigma-cli
  • Sigma backends: sigma plugin install splunk elastic-lucene microsoft365defender
  • python3 for validation and formatting helpers
  • jq for JSON manipulation: sudo apt install jq
  • Access to at least one SIEM platform (Splunk / Elastic / Sentinel) or sample log data

Inputs

Variable Description Example
DETECTION_OBJECTIVE One-sentence description of what to detect "Detect PowerShell downloading and executing in-memory payloads"
LOG_SOURCE_TYPE Primary log source type windows_process_creation
MITRE_TECHNIQUE MITRE ATT&CK technique ID (optional) T1059.001
SIGMA_RULE_FILE Existing Sigma YAML file to convert (optional) /tmp/rule.yml
TEST_LOG_FILE Sample log file for validation (optional) /tmp/test_events.json

Workflow

Step 1: Define the detection objective

echo "=== Step 1: Define Detection Objective ==="

DETECTION_OBJECTIVE="${DETECTION_OBJECTIVE:-}"
MITRE_TECHNIQUE="${MITRE_TECHNIQUE:-}"

if [ -z "$DETECTION_OBJECTIVE" ]; then
    read -rp "What threat behavior do you want to detect? " DETECTION_OBJECTIVE
fi

if [ -z "$MITRE_TECHNIQUE" ]; then
    read -rp "MITRE ATT&CK technique ID (leave blank to skip): " MITRE_TECHNIQUE
fi

echo ""
echo "  Objective:        $DETECTION_OBJECTIVE"
echo "  MITRE technique:  ${MITRE_TECHNIQUE:-N/A}"
echo ""

# Suggest detection category based on objective keywords
python3 - "$DETECTION_OBJECTIVE" <<'PYEOF'
import sys, re

obj = sys.argv[1].lower()

categories = {
    'Endpoint – Process Creation':    ['powershell', 'cmd', 'wscript', 'mshta', 'rundll32', 'regsvr32',
                                       'process', 'spawn', 'execute', 'launch', 'child'],
    'Endpoint – Registry':            ['registry', 'regedit', 'hklm', 'hkcu', 'run key', 'persistence'],
    'Endpoint – DLL / Code Injection':['inject', 'dll', 'reflective', 'shellcode', 'virtualalloc', 'writeprocessmemory'],
    'Endpoint – PowerShell / Script': ['powershell', 'script', 'iex', 'invoke-expression', 'base64', 'bypass'],
    'Network – DNS':                  ['dns', 'tunnel', 'dga', 'domain generation', 'exfil'],
    'Network – Lateral Movement':     ['smb', 'rdp', 'wmi', 'lateral', 'pass the hash', 'psexec'],
    'Identity – Brute Force':         ['brute', 'password spray', 'login failure', 'authentication'],
    'Identity – Kerberos':            ['kerberoast', 'dcsync', 'golden ticket', 'silver ticket', 'kerberos'],
    'Cloud – IAM':                    ['iam', 'policy', 'privilege', 'assume role', 'access key'],
    'Cloud – Storage':                ['s3', 'blob', 'bucket', 'public access', 'storage'],
}

matched = []
for cat, keywords in categories.items():
    if any(kw in obj for kw in keywords):
        matched.append(cat)

if matched:
    print(f"  Suggested category: {matched[0]}")
    if len(matched) > 1:
        print(f"  Also relevant:      {', '.join(matched[1:])}")
else:
    print("  Category: General endpoint/network (review log sources in Step 2)")
PYEOF

Read the full file on GitHub · 332 lines

Files

What ships with it

1 file 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.

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. 9d ago First seen · 332 lines · 37 tokens per session scan B 360786f2a7ff

Subscribe to this mod's changes

siem-rule is a skill published in the GitHub repository woohyun212/security-skill (21 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 3,346 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens