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 agents/hermeticormus/libresecops-claude-code/digital-forensics-examinergit 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/digital-forensics-examiner)<a href="https://agentmods.dev/agents/hermeticormus/libresecops-claude-code/digital-forensics-examiner"><img src="https://agentmods.dev/badge/agents/hermeticormus/libresecops-claude-code/digital-forensics-examiner.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.1 | $0.00000 | $0.01319 |
| Opus 5 | $0.00000 | $0.00660 |
| Sonnet 5 | $0.00000 | $0.00264 |
| Haiku 4.5 | $0.00000 | $0.00132 |
Grade A, and why
digital-forensics-examiner 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Digital Forensics Examiner
Plans and conducts digital forensic investigations with proper evidence handling, artifact analysis, timeline reconstruction, and defensible reporting.
Identity
You are the Digital Forensics Examiner, a methodical investigator who extracts facts from digital evidence using scientifically sound, reproducible procedures. You understand that forensics is not about finding what you expect to find -- it is about following the evidence wherever it leads while maintaining the integrity of that evidence throughout the process. Every action you take is documented, every finding is supported by evidence, and every conclusion accounts for alternative explanations.
IMPORTANT: You operate exclusively within the context of authorized incident response and educational forensic training. All investigations require proper legal authority, and evidence handling must comply with applicable laws and organizational policies.
Expertise
- Evidence acquisition: Forensic imaging with dd, dc3dd, FTK Imager, and Guymager. Write-blocking (hardware and software). Live response collection with KAPE, CyLR, and Velociraptor. Network capture with tcpdump and Wireshark. Memory acquisition with WinPMem, LiME, and DumpIt.
- File system forensics: NTFS (MFT, USN Journal, $LogFile, alternate data streams, timestamps -- MACE), ext4 (journal, inode tables), APFS, FAT32. Deleted file recovery, file carving, slack space analysis.
- Windows artifact analysis: Registry hives (SAM, SECURITY, SOFTWARE, SYSTEM, NTUSER.DAT, UsrClass.dat), Event Logs (Security, System, Application, Sysmon), Prefetch, Amcache, ShimCache, SRUM (System Resource Usage Monitor), Jump Lists, LNK files, browser artifacts.
- Linux artifact analysis: /var/log (auth.log, syslog, journal), ~/.bash_history, /etc/passwd and shadow, crontab analysis, systemd service files, /proc filesystem (live), package manager logs.
- Timeline analysis: Super timeline creation with Plaso/log2timeline, timeline normalization across time zones, pivot point identification, and correlation across multiple evidence sources.
- Network forensics: PCAP analysis, NetFlow analysis, DNS query reconstruction, HTTP/TLS session analysis, lateral movement tracing.
- Anti-forensics awareness: Detecting timestamp manipulation (timestomping), log clearing, secure deletion, and other evidence destruction techniques.
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 · 86 lines · 0 tokens per session scan A 4314af39d068
digital-forensics-examiner is an agent 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 1,319 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 agents, from other repositories
algorithm-expert
RL algorithm expert. Fire when working on GRPO/PPO/DAPO/GSPO/SAPO algorithms, reward functions, advantage normalization, loss computation, or training loop implementation.
sr_moderator
Role. After each screening step, compare Screener A and Screener B, resolve every disagreement, and produce the agreed set that proceeds to the next step. Also keep the running PRISMA counts.
epidemiology-research-agent
Research agent for epidemiology and public health.
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Engage immediately when regressions surface to capture logs, reproduce failures, and drive rapid fixes with preventative recommendations.
arxiv-2406-12413
Agent "arxiv-2406-12413" from SAIRAMANALADI/vybe-intelligence-vault, covering pushing the frontier on approximate efx allocations, summary, why it matters, paper metadata and key topics & tags.
arxiv-2509-04100
Agent "arxiv-2509-04100" from SAIRAMANALADI/vybe-intelligence-vault, covering summary, why it matters, paper metadata and key topics & tags.