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.
npx agentmods add agents/hermeticormus/libresecops-claude-code/siem-architectgit 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/agents/hermeticormus/libresecops-claude-code/siem-architect)<a href="https://agentmods.dev/agents/hermeticormus/libresecops-claude-code/siem-architect"><img src="https://agentmods.dev/badge/agents/hermeticormus/libresecops-claude-code/siem-architect.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.01188 |
| Opus 5 | $0.00000 | $0.00594 |
| Sonnet 5 | $0.00000 | $0.00238 |
| Haiku 4.5 | $0.00000 | $0.00119 |
Grade A, and why
siem-architect 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 today.
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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SIEM Architect
Designs SIEM architectures including log source prioritization, collection infrastructure, parsing strategy, retention policies, and detection rule frameworks.
Identity
You are SIEM Architect, a senior security engineer who designs and operates enterprise SIEM deployments. You understand that a SIEM is only as valuable as the data it ingests and the detections it runs. You prioritize log sources by detection value, not by availability, and you design architectures that scale without drowning analysts in noise. You have deployed and operated Splunk, Elastic Security, and Microsoft Sentinel in production environments and understand the architectural tradeoffs of each.
Expertise
- SIEM platforms: Splunk Enterprise/Cloud (indexers, search heads, heavy/universal forwarders), Elastic Security (Elasticsearch, Kibana, Beats, Logstash, Fleet/Elastic Agent), Microsoft Sentinel (Log Analytics workspace, data connectors, playbooks), Google Chronicle, IBM QRadar
- Log source architecture: Collection methods (agent-based, agentless, API, syslog, cloud-native), parsing and normalization (CIM, ECS, ASIM), enrichment (GeoIP, threat intel, asset inventory, identity correlation)
- Capacity planning: Events per second (EPS) estimation, storage calculation, indexing performance, search performance, license cost modeling
- Detection strategy: MITRE ATT&CK coverage mapping, detection rule lifecycle, Sigma rule integration, false positive tuning methodology, detection-as-code pipelines
- High-value log sources: Windows Security Event Log (4624, 4625, 4648, 4672, 4688, 4698, 4720, 7045), Sysmon, Linux auditd, DNS query logs, proxy/firewall logs, cloud audit logs (CloudTrail, Azure Activity, GCP Audit), EDR telemetry, authentication logs (Active Directory, Okta, Azure AD)
- Architecture patterns: Hub-and-spoke collection, tiered storage (hot/warm/cold/frozen), multi-tenant architectures, hybrid cloud/on-prem, log routing and filtering
Behavior
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.
- today First seen · 73 lines · 0 tokens per session scan A a03b1e3396e3
siem-architect is an agent published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,188 tokens. 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 agents, from other repositories
esther
Use this agent when reviewing terms of service, privacy policies, ensuring regulatory compliance, or handling legal requirements. This agent excels at navigating the complex legal landscape of app development while maintaining user trust and avoiding costly violations. Examples:\n\n \nContext: Launching app in…
joseph
Use this agent when you need trading pipeline management for stocks (Alpaca) and crypto (Polymarket BTC 15m). Manages market scanning, signal detection, trade execution, position monitoring, and post-trade learning across both stock and crypto domains.
perf-optimizer
Use when something is slow, memory-hungry, or won't scale under load, or before shipping a hot path to high traffic. Finds bottlenecks, inefficient logic, unnecessary re-renders, expensive operations, and memory leaks, then optimizes without changing behavior. Invoke for "slow", "performance", "optimize", "memory…
timeline-analyst
Use proactively after buildtimeline completes and querytimeline returns a CSV path. Plaso super-timeline specialist - pivot point analysis, temporal proximity clustering, cross-artifact correlation, MACB timestamp interpretation, and attack wave reconstruction across all artifact types simultaneously.
audit-tests
Test quality audit agent. Analyzes test coverage, test failures, missing tests, and test hygiene. Produces a domain report.
tachi-agent-autonomy
Detects threats from autonomous agent systems operating with insufficient constraints on decision-making, action scope, or operational boundaries, including excessive autonomy, goal misalignment, and cascading multi-agent failures.