siem-log-management

siem-log-management is a plugin for Claude Code from HermeticOrmus/LibreSecOps-Claude-Code. Its manifest loads nothing; the 2 skills, 2 commands, 2 agents it bundles cost 345 tokens per session together, scanned A, original, MIT.

A SIEM and log-management tool for planning collected logs and writing detection or investigation queries. A SIEM is a system that gathers security events from many sources so they can be searched and correlated.

In plain words
What is it for?
Use it to plan log sources, design SIEM architecture, write queries for Splunk, Elastic, or Microsoft Sentinel, and correlate events during detection or threat hunting.
Why use it?
It helps turn scattered logs into useful evidence for finding suspicious activity. Cross-source correlation can connect events that would be easy to miss in separate systems.

Plugin for Claude Code

Written for Claude Code: a Claude Code plugin manifest.

Good fit Use it to plan log sources, design SIEM architecture, write queries for Splunk, Elastic, or Microsoft Sentinel, and correlate events during detection or threat hunting.

Compare 6 plugins from other repositories ↓
Install in Claude Code
/plugin marketplace add HermeticOrmus/LibreSecOps-Claude-Code
/plugin install siem-log-management
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.

Clone the repo
git clone --depth 1 https://github.com/HermeticOrmus/LibreSecOps-Claude-Code

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 siem-log-management

README.md
[![agentmods](https://agentmods.dev/badge/plugins/hermeticormus/libresecops-claude-code/siem-log-management/github.svg)](https://agentmods.dev/plugins/hermeticormus/libresecops-claude-code/siem-log-management)
Your own site
<a href="https://agentmods.dev/plugins/hermeticormus/libresecops-claude-code/siem-log-management"><img src="https://agentmods.dev/badge/plugins/hermeticormus/libresecops-claude-code/siem-log-management/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-log-management

Your own site · 80×15
<a href="https://agentmods.dev/plugins/hermeticormus/libresecops-claude-code/siem-log-management"><img src="https://agentmods.dev/badge/plugins/hermeticormus/libresecops-claude-code/siem-log-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured The manifest loads nothing itself; its 2 skills, 2 commands, 2 agents cost 345 tokens a session between them.
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.
Security

Grade A, and why

siem-log-management 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 12d 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/siem-log-management/.claude-plugin/plugin.json · 22 lines

What it actually says

{
  "name": "siem-log-management",
  "version": "1.0.0",
  "description": "SIEM and log management: SIEM architecture and log source planning, detection and hunting queries in Splunk SPL, Elastic KQL/EQL, and Sentinel KQL, and cross-source event correlation.",
  "author": {
    "name": "Diego Bodart",
    "url": "https://github.com/HermeticOrmus"
  },
  "homepage": "https://github.com/HermeticOrmus/LibreSecOps-Claude-Code",
  "repository": "https://github.com/HermeticOrmus/LibreSecOps-Claude-Code",
  "license": "MIT",
  "keywords": [
    "siem",
    "log-management",
    "splunk",
    "elastic",
    "microsoft-sentinel",
    "detection-engineering",
    "sigma"
  ]
}
Contents

What it installs

The manifest is a name and a version. 2 skills, 2 commands, 2 agents travel with it, and installing the plugin installs all of them — 345 tokens a session between them. Each is measured on its own page, and each can be installed alone.

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. 12d ago First seen · 22 lines scan A 042f1fdce23b

Subscribe to this mod's changes

siem-log-management is a plugin published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 9d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-10-01.