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 skills/hermeticormus/libresecops-claude-code/forensic-methodologynpx skills add HermeticOrmus/LibreSecOps-Claude-Code --skill forensic-methodologygit 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/skills/hermeticormus/libresecops-claude-code/forensic-methodology)<a href="https://agentmods.dev/skills/hermeticormus/libresecops-claude-code/forensic-methodology"><img src="https://agentmods.dev/badge/skills/hermeticormus/libresecops-claude-code/forensic-methodology.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 | $0.00000 | $0.03423 |
| Opus 5 | $0.00000 | $0.01711 |
| Sonnet 5 | $0.00000 | $0.00685 |
| Haiku 4.5 | $0.00000 | $0.00342 |
Grade D, and why
forensic-methodology scanned grade D with 2 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.
Enumerates the file system for secretshighData exfiltration
Searching home directories for .env, .ssh, .aws or credential files is reconnaissance for credential theft.
ls -la "$user_dir/.ssh/" > "$EVIDENCE_DIR/users/$user/ssh_keys.txt" 2>/dev/null Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
# Run as root on the evidence system How it starts
The opening of the file, as written. The whole thing — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forensic Methodology
Evidence collection, preservation, analysis, and reporting methodology following NIST SP 800-86 and ISO 27037 standards.
Knowledge Base
The Forensic Process (NIST SP 800-86)
NIST defines four phases:
1. Collection: Identifying and gathering evidence from relevant sources. The priority is to preserve evidence integrity and collect volatile evidence before it is lost.
2. Examination: Processing the collected evidence to extract relevant data. This includes disk image mounting, log parsing, artifact extraction, and keyword searching.
3. Analysis: Interpreting the extracted data to answer the investigation questions. This includes timeline reconstruction, correlation across sources, and hypothesis testing.
4. Reporting: Documenting the findings, methodology, and conclusions in a format appropriate for the audience (technical, management, or legal).
Order of Volatility (RFC 3227)
Evidence must be collected in order of volatility -- most volatile first:
- CPU registers and cache (nanoseconds -- effectively uncollectable)
- Memory (RAM) (lost on power-off -- collect immediately)
- Network state (connections, routing tables, ARP cache -- changes constantly)
- Running processes (may be terminated or replaced)
- Disk (persists across reboots but can be overwritten)
- Remote logging (SIEM, syslog server -- may be rotated)
- Physical configuration (network topology -- changes infrequently)
- Archival media (backups, tapes -- most durable)
Evidence Integrity
Hashing: Every evidence item is hashed at collection time. SHA-256 is the standard. MD5 is computed as a secondary hash for compatibility but is not sufficient alone (collision vulnerabilities).
Write-blocking: Original evidence media must be accessed through write-blockers to prevent any modification. Hardware write-blockers (Tableau, WiebeTech) are preferred; software write-blockers (Linux mount with -o ro,noexec,noatime) are acceptable when hardware is unavailable.
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 · 261 lines · 0 tokens per session scan D 87ab77bba9b7
forensic-methodology is a skill 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 3,423 tokens. A static security scan graded it D with 2 findings (enumerates the file system for secrets, asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
implementing-devsecops-security-scanning
Integrates Static Application Security Testing (SAST), Dynamic Application Security Testing (DAST), and Software Composition Analysis (SCA) into CI/CD pipelines using open-source tools. Covers Semgrep for SAST, Trivy for SCA and container scanning, OWASP ZAP for DAST, and Gitleaks for secrets detection. Activates for…
building-devsecops-pipeline-with-gitlab-ci
Design and implement a comprehensive DevSecOps pipeline in GitLab CI/CD integrating SAST, DAST, container scanning, dependency scanning, and secret detection.
integrating-dast-with-owasp-zap-in-pipeline
This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application Security Testing in CI/CD pipelines. It addresses configuring baseline, full, and API scans against running applications, interpreting ZAP findings, tuning scan policies, and establishing DAST quality gates in GitHub Actions and GitLab…
implementing-runtime-application-self-protection
Deploy Runtime Application Self-Protection (RASP) agents to detect and block attacks from within application runtime, covering OpenRASP integration, attack pattern detection, and security policy configuration for Java and Python web applications.
integrating-dast-with-owasp-zap-in-pipeline
This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application Security Testing in CI/CD pipelines. It addresses configuring baseline, full, and API scans against running applications, interpreting ZAP findings, tuning scan policies, and establishing DAST quality gates in GitHub Actions and GitLab…
audit-production-readiness
Audit a repository or service for release-blocking bugs, security, data/privacy, AI-agent, supply-chain, operability, and scale risks. Use for deep code audits, threat models, pre-production reviews, vulnerability triage, incidents, defensive investigation, release gates, or evidence-based 10k-to-1M-user readiness.