Memory Forensics

Name: Memory Forensics
Author: wshobson

Checked

wshobson·vlatest·security·MIT

Analyzes system memory to uncover hidden data, malware traces, and past activity – crucial for incident investigation & threat hunting.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

Run this in your project

terminal

$ npx skills add wshobson/agents --skill memory-forensics -a claude-code

Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

wshobson

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned 12 Oct 2026

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned wshobson/agents at 46891e7e60.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit: 46891e7e60
Manifest: plugins/reverse-engineering/skills/memory-forensics/SKILL.md
Scanned: 2 files, 450 lines

This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.

What each check looks for →

About this skill

What it does

The memory-forensics skill enables AI agents to analyze and extract information from system memory dumps. It supports identifying running processes, detecting anomalies in memory usage, and uncovering hidden or malicious activity by inspecting memory artifacts.

When to use it

Investigating suspicious behavior on a compromised system
Analyzing memory dumps for signs of malware or rootkits
Forensic analysis after a security incident
Troubleshooting unexpected application crashes or performance issues

Key capabilities

Memory dump parsing and analysis
Process and thread identification in memory
Detection of hidden processes or injected code
Extraction of artifacts such as network connections, loaded modules, and registry keys

Example prompts

"Analyze this memory dump for signs of malware."
"List all running processes from the provided memory image."
"Check for anomalies in memory usage patterns."

Tips & gotchas

Ensure you have proper access rights to memory dumps and system files.
Memory analysis can be resource-intensive; use dedicated tools or environments for large datasets.