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/malware-triage)<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/malware-triage"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/malware-triage/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/malware-triage"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/malware-triage.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.00033 | $0.01030 |
| Opus 5.5 | $0.00013 | $0.00412 |
| Sonnet 5.5 | $0.00007 | $0.00206 |
| Haiku 4.5 | $0.00003 | $0.00103 |
Grade A, and why
malware-triage 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/malware-triage
Perform rapid initial assessment of a suspected malicious file, producing a structured triage report with file identification, risk indicators, and recommended analysis steps.
Trigger
Use when you first encounter a suspicious file and need to determine:
- What type of file it is (regardless of extension)
- Whether it warrants deeper analysis
- What analysis approach to take next (static-first vs dynamic-first)
- Initial risk classification for prioritization
Common entry points: incident response alerts, user-reported suspicious files, email attachment analysis, threat intel sample processing.
Input
Provide any combination of the following:
- File hashes (MD5, SHA-1, SHA-256) for reputation lookup guidance
filecommand output showing magic bytes / file type identificationstringsoutput (or a subset of interesting strings)- File metadata (name, size, source, timestamps, how it was obtained)
- PE/ELF header information from
readelf,pefile,dumpbin, or similar tools - VirusTotal or other reputation service results
- Context about where and how the file was found
At minimum, provide the file hash and file type. The more context provided, the more specific the triage will be.
Process
-
File identification -- Determine true file type from magic bytes, not extension. Identify polyglot files (files that are valid in multiple formats). Check for double extensions or right-to-left override characters in the filename.
-
Reputation check guidance -- Recommend hash lookups against VirusTotal, MalwareBazaar, CIRCL hashlookup, and AlienVault OTX. If results are provided, interpret detection ratios and family classifications.
-
Initial indicator assessment -- Review provided strings, imports, or metadata for immediate red flags:
- Network indicators (URLs, IPs, domains, user-agents)
- Suspicious API imports (process injection, keylogging, screen capture, crypto)
- Encoded/obfuscated content (Base64 blobs, XOR patterns, PowerShell encoded commands)
- Anti-analysis indicators (packer signatures, high entropy sections, anti-debug strings)
- Known malware family markers (mutex patterns, config structures, C2 protocols)
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 · +33 tokens per session 4bd24547a835
- 1mo ago First seen · 98 lines · 0 tokens per session scan A 120f8e7daa54
malware-triage is a command published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 9d ago), licensed MIT. It adds 33 tokens to every session and 1,030 once invoked, about $0.0001 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
quality
Run full Fettle quality scan on the current project.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.