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.
git clone --depth 1 https://github.com/HermeticOrmus/LibreSecOps-Claude-CodeWrote 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/commands/hermeticormus/libresecops-claude-code/siem-setup)<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/siem-setup"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/siem-setup/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.
<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/siem-setup"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/siem-setup.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00026 | $0.01103 |
| Opus 5.5 | $0.00010 | $0.00441 |
| Sonnet 5.5 | $0.00005 | $0.00221 |
| Haiku 4.5 | $0.00003 | $0.00110 |
Grade A, and why
siem-setup 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.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/siem-setup
Design a SIEM architecture including log source prioritization, collection strategy, retention policies, and initial detection rule set.
Trigger
Use when deploying a new SIEM, migrating between SIEM platforms, or redesigning an existing SIEM architecture. Also useful for evaluating SIEM readiness and identifying critical gaps in current deployments.
Input
- Environment: Cloud (AWS/Azure/GCP), on-premises, hybrid, multi-cloud
- Scale: Number of endpoints, users, servers, cloud workloads
- Operating systems: Windows, Linux, macOS distribution
- Key applications: Active Directory, Office 365, AWS services, custom applications
- Current state: Existing log collection, current SIEM (if any), known gaps
- Compliance requirements: Regulatory frameworks requiring specific log retention or monitoring
- Budget context: License model preference (per-GB, per-EPS, open-source), operational budget range
- Team size: SOC analysts, detection engineers, SIEM administrators available
Process
-
Platform recommendation -- Based on environment, budget, and team:
- Splunk: Best query language, highest cost, strong ecosystem
- Elastic Security: Open-source core, strong endpoint integration, good for technical teams
- Microsoft Sentinel: Best for Azure/O365-heavy environments, consumption-based pricing
- For smaller teams/budgets: Wazuh (open-source), Graylog, Security Onion
-
Log source prioritization -- Ranked by detection value:
Tier 1 (Deploy first -- highest detection value):
- Windows Security Event Logs (Event IDs: 4624, 4625, 4648, 4672, 4688, 4698, 4720, 7045)
- Sysmon (process creation, network connections, file creation, registry, DNS)
- EDR telemetry (CrowdStrike, Defender for Endpoint, SentinelOne)
- DNS query logs (internal resolver)
- Authentication platform logs (Active Directory, Okta, Azure AD)
Tier 2 (Deploy second -- critical context):
- Cloud audit logs (CloudTrail, Azure Activity Log, GCP Audit Log)
- Proxy/web gateway logs
- Email gateway logs (for phishing detection)
- Firewall connection logs
- VPN authentication logs
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.
- 12d ago Changed · +5 lines · +26 tokens per session 778bfa7a883d
- 1mo ago First seen · 104 lines · 0 tokens per session scan A d78f70068f40
siem-setup is a command published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 9d ago), licensed MIT. It adds 26 tokens to every session and 1,103 once invoked, about $0.0001 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-03.
Other commands, from other repositories
verify
An independent recheck of a security assessment report that derives conclusions from its own evidence instead of accepting the original findings.
corporate-launcher
Build a secure, branded, organization-specific launcher around an AI coding CLI (Claude Code, Codex CLI, Gemini CLI, Cursor, or Cline) so the user can.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.