A command for investigating security events in a SIEM, a system that collects and searches logs. It runs a saved query over a chosen time range and checks the results against MITRE ATT&CK techniques and Sigma detection rules.

Use it to run a SIEM query, summarize its security findings, map them to known attack techniques, and review detection coverage.

It brings suspicious activity, affected users, addresses, files, commands, and sign-ins into one investigation note. It also shows whether existing detection rules cover the findings or leave gaps.

query — Command for Claude Code by omeryemba: A command for investigating security events in a SIEM…

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.

agentmods

npx agentmods add commands/omeryemba/mcp-hayabusa/query

Clone the repo

git clone --depth 1 https://github.com/omeryemba/mcp-hayabusa

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/omeryemba/mcp-hayabusa/query.svg)](https://agentmods.dev/commands/omeryemba/mcp-hayabusa/query)

Your own site

<a href="https://agentmods.dev/commands/omeryemba/mcp-hayabusa/query"><img src="https://agentmods.dev/badge/commands/omeryemba/mcp-hayabusa/query.svg" alt="Measured on agentmods" height="20"></a>

Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 359 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00009	$0.00359
Opus 5	$0.00005	$0.00179
Sonnet 5	$0.00002	$0.00072
Haiku 4.5	$0.00001	$0.00036

Measured 5d ago against content hash d0e8c2edfd56, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

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 5d 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.

.claude/commands/query.md · 69 lines

What it actually says

Workflow

You are performing a defensive security investigation.

Input

Arguments: $ARGUMENTS

Parse as:

query_file (required) — path to a file containing the SIEM query to run. If missing, stop and ask the user for a query file.
timerange (optional) — defaults to -24h if not given.

Example:

/query queries/suspicious_logons.txt -24h

Steps

Confirm query_file was supplied and exists; stop and ask if not. Read the query from it, then execute that query for the given timerange (default -24h) against SIEM data, if a SIEM MCP tool or resource is configured in this environment. If no SIEM integration is available, say so explicitly rather than silently skipping this step.
Analyse the results and extract:
- suspicious processes
- users
- IP addresses
- files
- commands
- authentication activity
Identify possible MITRE ATT&CK techniques from the findings.
Use the detection MCP resources to check:
- whether detection rules exist
- which Sigma rules provide coverage
- whether coverage gaps exist
Generate an investigation note.

Output

Investigation Summary

Findings

ATT&CK Mapping

Technique	Description

Detection Coverage

Technique	Status	Rule

Recommendations

Investigate uncovered techniques.
Review existing detections.
Improve detection coverage where gaps exist.

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.

5d ago First seen · 69 lines · 9 tokens per session scan A d0e8c2edfd56

Subscribe to this mod's changes

query is a command published in the GitHub repository omeryemba/mcp-hayabusa (0 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 359 once invoked, about $0.0000 per session on Opus 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-08-31.

Security blue-team claude claude-code cybersecurity digital-forensics evtx

query