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/log-query)<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/log-query"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/log-query/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/log-query"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/log-query.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.00041 | $0.01057 |
| Opus 5.5 | $0.00016 | $0.00423 |
| Sonnet 5.5 | $0.00008 | $0.00211 |
| Haiku 4.5 | $0.00004 | $0.00106 |
Grade A, and why
log-query 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/log-query
Build a detection or investigation query for a specific threat or scenario, with syntax for Splunk SPL, Elastic KQL, or Microsoft Sentinel KQL.
Trigger
Use when you need to:
- Write a detection rule for a specific MITRE ATT&CK technique
- Build an investigation query for an active incident
- Convert a Sigma rule to a specific platform syntax
- Create a threat hunting query
- Tune an existing detection rule to reduce false positives
Input
- Threat/scenario: What to detect or investigate. Can be:
- MITRE ATT&CK technique ID (e.g., "T1059.001 - PowerShell")
- Specific attack pattern (e.g., "DCSync attack detection")
- Investigation scenario (e.g., "trace lateral movement from compromised host")
- IOC search (e.g., "find all connections to this IP across last 30 days")
- Sigma rule to convert
- Platform: Splunk SPL, Elastic KQL/EQL, Microsoft Sentinel KQL, or Sigma (all platforms)
- Available log sources: What data is indexed (Sysmon, Windows Security, CloudTrail, etc.)
- Tuning context (optional): Known false positive sources to exclude, environment-specific filters
Process
-
Requirement analysis -- Understand what needs to be detected and the available data sources. Map the threat to specific observable events.
-
Log source identification -- Determine which log sources contain the events needed for detection:
- Process creation: Sysmon Event ID 1, Windows 4688, EDR process logs
- Network connections: Sysmon Event ID 3, firewall logs, proxy logs, Zeek conn.log
- Authentication: Windows 4624/4625, Okta system logs, Azure AD sign-in logs
- File operations: Sysmon Event IDs 11/15/23, auditd, EDR file logs
- Registry: Sysmon Event IDs 12/13/14, Windows Security logs
- DNS: Sysmon Event ID 22, DNS server query logs, Zeek dns.log
- Cloud: CloudTrail, Azure Activity, GCP Audit
-
Query construction -- Build the query with:
- Core detection logic (the pattern that identifies the threat)
- Context enrichment (user, host, process details for triage)
- False positive filtering (known-good patterns excluded)
- Performance optimization (indexed fields, efficient operators)
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 · +41 tokens per session 1a8f6bdcb82d
- 1mo ago First seen · 119 lines · 0 tokens per session scan A bdf4bc692b54
log-query is a command published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 9d ago), licensed MIT. It adds 41 tokens to every session and 1,057 once invoked, about $0.0002 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.