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 commands/hermeticormus/libresecops-claude-code/hunt-hypothesisgit 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/hunt-hypothesis)<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/hunt-hypothesis"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/hunt-hypothesis.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.00902 |
| Opus 5 | $0.00000 | $0.00451 |
| Sonnet 5 | $0.00000 | $0.00180 |
| Haiku 4.5 | $0.00000 | $0.00090 |
Grade A, and why
hunt-hypothesis 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 4d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/hunt-hypothesis
Generate a structured threat hunting hypothesis with data sources, analysis approach, and expected indicators.
Trigger
Use when you need to:
- Start a threat hunt and need a structured hypothesis
- Investigate a specific ATT&CK technique proactively
- Follow up on threat intelligence with a targeted hunt
- Explore a detection gap identified during a red team exercise
- Conduct a periodic hunt against common adversary behaviors
Input
- Required: One of the following:
- ATT&CK tactic or technique (e.g.,
credential-access,T1003.001) - Threat intelligence indicator or report to investigate
- Detection gap description (e.g., "we have no detection for DNS tunneling")
- Broad category (e.g., "lateral-movement", "persistence", "exfiltration")
- ATT&CK tactic or technique (e.g.,
- Optional: Available data sources (SIEM platform, log types collected, EDR product)
- Optional flag:
--queries-- include ready-to-run SIEM queries - Optional flag:
--playbook-- generate a full hunt playbook with step-by-step instructions
Process
-
Hypothesis Formulation: Construct a testable hypothesis:
- Based on the input, what specific adversary behavior are we looking for?
- What would evidence of this behavior look like in our telemetry?
- What is the null hypothesis (expected benign baseline)?
-
Scope Definition: Define the hunt boundaries:
- Time window (last 7 days, 30 days, 90 days)
- Systems in scope (all endpoints, servers only, specific segments)
- Data sources to query
-
Data Source Mapping: Identify the specific data sources needed:
- Which log types contain the relevant telemetry?
- What fields are we analyzing?
- Are there data gaps that limit the hunt?
-
Analysis Approach: Design the analytical methodology:
- Statistical: Frequency analysis, baseline deviation, rare value identification
- Pattern matching: Known indicators, behavioral signatures
- Temporal: Time-series analysis, beaconing detection, periodicity analysis
- Relational: Process tree analysis, network graph analysis, user-entity mapping
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.
- 4d ago First seen · 114 lines · 0 tokens per session scan A f042df9f0e5d
hunt-hypothesis is a command 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 902 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-08-31.
Other commands, from other repositories
tachi.architecture
Generate an architecture description for tachi threat modeling input.
aod.blueprint
Unified project setup & story generation — auto-detects new vs existing projects.
sicario.assess
Assess the repository against SicarioSpec guardrails.
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.