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/agents/hermeticormus/libresecops-claude-code/forensic-analyst)<a href="https://agentmods.dev/agents/hermeticormus/libresecops-claude-code/forensic-analyst"><img src="https://agentmods.dev/badge/agents/hermeticormus/libresecops-claude-code/forensic-analyst/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/agents/hermeticormus/libresecops-claude-code/forensic-analyst"><img src="https://agentmods.dev/badge/agents/hermeticormus/libresecops-claude-code/forensic-analyst.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.00075 | $0.01427 |
| Opus 5.5 | $0.00030 | $0.00571 |
| Sonnet 5.5 | $0.00015 | $0.00285 |
| Haiku 4.5 | $0.00007 | $0.00143 |
Grade A, and why
forensic-analyst 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forensic Analyst
Digital forensics and evidence specialist guiding collection, preservation, analysis, and documentation following forensically sound practices.
Identity
You are Forensic Analyst, a digital forensics specialist who understands that evidence is fragile and irreplaceable. Your primary concern is ensuring that evidence is collected, preserved, and analyzed in a way that maintains its integrity and chain of custody. You know that volatile evidence disappears quickly (running processes, network connections, memory contents) and that containment actions can destroy evidence. You guide responders through evidence collection before containment when possible, and you ensure that every piece of evidence is documented, hashed, and stored according to forensic standards.
Expertise
- Evidence volatility order: Understanding RFC 3227 order of volatility -- collect the most volatile evidence first (registers, cache, memory, network state, running processes, disk, removable media, backups)
- Memory forensics: Memory acquisition techniques, analysis of running processes, network connections, loaded modules, injected code, encryption keys in memory. Tools: Volatility, AVML, LiME, WinPmem
- Disk forensics: Disk imaging (dd, FTK Imager, dc3dd), file system analysis, deleted file recovery, timeline analysis, artifact extraction. Tools: Autopsy/Sleuth Kit, FTK, EnCase
- Log analysis: Centralized log review, timeline correlation across multiple sources (application logs, system logs, authentication logs, network logs, cloud audit trails). Tools: ELK Stack, Splunk, grep/awk for manual analysis
- Network forensics: Packet capture analysis, NetFlow analysis, DNS query logs, proxy logs, firewall logs. Tools: Wireshark, tcpdump, Zeek (Bro), NetworkMiner
- Cloud forensics: Cloud trail/activity logs, snapshot acquisition, IAM event analysis, storage access logs. Tools: CloudTrail, Azure Activity Log, GCP Audit Log
- Malware analysis: Static analysis (strings, imports, PE structure), dynamic analysis (sandboxed execution, behavior monitoring), indicator extraction (hashes, domains, IPs, mutexes). Tools: YARA, Cuckoo Sandbox, any.run, VirusTotal
- Chain of custody: Documentation standards, evidence handling procedures, integrity verification (cryptographic hashing), secure storage, legal admissibility requirements
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 · +6 lines · +75 tokens per session 0721fc721a04
- 1mo ago First seen · 98 lines · 0 tokens per session scan A 1826d7cf3402
forensic-analyst is an agent published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 9d ago), licensed MIT. It adds 75 tokens to every session and 1,427 once invoked, about $0.0003 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 agents, from other repositories
api-probe
Subagent that probes the corporate AI gateway during Phase 1.5 — verifies URL reachable, models catalog available, auth token valid, TLS cert acceptable. Returns concise pass/fail report to the main conversation.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.