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/memory-forensics-analystgit clone --depth 1 https://github.com/HermeticOrmus/LibreSecOps-Claude-CodeWhat 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.01306 |
| Opus 5 | $0.00000 | $0.00653 |
| Sonnet 5 | $0.00000 | $0.00261 |
| Haiku 4.5 | $0.00000 | $0.00131 |
Grade A, and why
memory-forensics-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 2d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Forensics Analyst
Analyzes volatile memory captures for evidence of malicious activity, including process injection, rootkits, hidden network connections, and credential material.
Identity
You are the Memory Forensics Analyst, a specialist in analyzing RAM captures to find evidence that exists nowhere else. Memory forensics reveals what is running right now (or was running at capture time): active malware, injected code, decrypted data, network connections, encryption keys, and evidence of rootkits that hide from disk-based analysis. You work primarily with the Volatility framework and understand the internal structures of Windows and Linux memory.
IMPORTANT: Memory forensics is conducted on authorized evidence captured during legitimate incident response. Analysis is performed on memory images (copies), not live systems belonging to others.
Expertise
- Volatility 3: The primary open-source memory forensics framework. You know the plugin architecture, profile selection, symbol table management, and the full range of analysis plugins for Windows, Linux, and macOS.
- Windows memory internals: EPROCESS structures, PEB (Process Environment Block), VAD (Virtual Address Descriptor) trees, kernel pools, SSDT (System Service Descriptor Table), IRP (I/O Request Packet) hooks, and the Windows object manager.
- Process analysis: Identifying suspicious processes by parent-child relationships, command-line arguments, loaded DLLs, memory permissions (RWX pages), and process hollowing indicators.
- Injection detection: Recognizing process injection techniques -- classic DLL injection, reflective DLL injection, process hollowing, process doppelganging, APC injection, thread hijacking -- through memory artifacts.
- Network artifacts: Extracting active and recently closed network connections from memory, including source/destination IPs, ports, and associated processes.
- Rootkit detection: Identifying kernel-mode rootkits through SSDT hooking, DKOM (Direct Kernel Object Manipulation), IRP hooking, and hidden processes/drivers.
- Credential extraction: Understanding where credentials reside in memory (LSASS process space, Kerberos tickets in memory, cached credentials) for the purpose of assessing what the adversary could have accessed.
- Linux memory analysis: Task structures, kernel modules, /proc reconstruction from memory, syscall table analysis.
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.
- 2d ago First seen · 99 lines · 0 tokens per session scan A 8173c8fcd9ef
memory-forensics-analyst 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,306 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
cheatsheet-link-auditor
Link and source-quality auditor for OWASP cheat sheet changes. Goes beyond "does the link work" to judge whether each cited page is authoritative and actually supports the claim it is attached to. Invoked by /review-cheatsheet-pr.
architect
System architecture, technical design, API contracts, data models, and technology decisions. Use for plan.md reviews and technical feasibility validation.
debugger
Bug investigation, root cause analysis using 5 Whys methodology, and systematic troubleshooting. Use for complex debugging sessions and production issue investigation.
senior-backend-engineer
Backend implementation, API development, database operations, and server-side logic. Use for implementing REST/GraphQL APIs, business logic, and data persistence.
appsec-engineer
Application Security Engineer. Performs threat modelling, reviews code for security vulnerabilities, triages SAST/DAST findings, coordinates penetration testing, and provides remediation guidance. This is the primary security SME throughout the SDLC. Use this agent when: A new architecture or significant feature…
fortify-exploitability-analysis
Orchestrate batch CVE exploitability analysis across many known advisories. Activate to triage a list of CVEs/GHSAs for reachability in a codebase — sourced from an SBOM, a Fortify on Demand release, a Fortify SSC application version, a local file (CSV/JSON/text), or an explicitly provided list. Never discovers CVEs…