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/ioc-extract)<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/ioc-extract"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/ioc-extract/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/ioc-extract"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/ioc-extract.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.00044 | $0.01062 |
| Opus 5.5 | $0.00018 | $0.00425 |
| Sonnet 5.5 | $0.00009 | $0.00212 |
| Haiku 4.5 | $0.00004 | $0.00106 |
Grade A, and why
ioc-extract 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ioc-extract
Extract, categorize, and format indicators of compromise from analysis notes, sandbox reports, or raw data into structured, actionable intelligence.
Trigger
Use after completing malware analysis (static or dynamic) or when processing threat intelligence reports, incident response notes, or any unstructured data that contains indicators of compromise. Also useful for converting informal analyst notes into structured IOC formats suitable for SIEM ingestion, threat intel platforms, or information sharing.
Input
Provide any of the following:
- Analysis notes from static or dynamic malware analysis sessions
- Sandbox reports (full text or key sections from ANY.RUN, Joe Sandbox, Cuckoo, etc.)
- Network captures or Zeek/Suricata logs showing suspicious traffic
- Incident response notes with observed artifacts
- Threat intelligence reports containing IOCs mixed with narrative
- Raw data (log entries, PCAP summaries, forensic artifacts)
The input can be messy and unstructured -- the command's purpose is to extract and organize.
Process
-
Indicator extraction -- Scan the input for all indicator types:
Network indicators:
- IPv4 and IPv6 addresses (excluding RFC 1918 private ranges and known-good infrastructure unless flagged)
- Domain names and subdomains (defang format accepted:
hxxps://,[.]com) - Full URLs including paths and parameters
- Email addresses (sender and recipient in phishing contexts)
- JA3/JA3S TLS fingerprint hashes
- JARM fingerprints
- SSL certificate hashes and subject strings
- User-Agent strings
Host indicators:
- File hashes (MD5, SHA-1, SHA-256) -- validate format and length
- File names and paths (with OS context)
- Registry key paths and values (Windows)
- Mutex / named pipe names
- Scheduled task names and configurations
- Service names and descriptions
- WMI event subscription details
Behavioral indicators:
- Process creation command lines
- API call sequences that indicate specific techniques
- MITRE ATT&CK technique IDs and descriptions
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 · +44 tokens per session fb701ef7132e
- 1mo ago First seen · 113 lines · 0 tokens per session scan A 547bf1eb7b51
ioc-extract is a command published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 9d ago), licensed MIT. It adds 44 tokens to every session and 1,062 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.