MysterionRiseMysterionRise/ctf-kit/skills/forensics/SKILL.md

forensics

Skill12 starsChanged 9 months agoMITView on GitHub

Solve CTF forensics challenges: memory dumps, network captures, disk images, and file carving. Use when you see: .vmem .raw .dmp memory dumps, .pcap .pcapng network captures, .dd .E01 disk images, or embedded/hidden files. Triggers: "memory dump", "packet capture", "disk image", "file carving", "deleted files", "volatility". Tools: volatility3, binwalk, foremost, tshark, sleuthkit. NOT for steganography (use stego) or binary exploitation (use pwn).

5 other projects use a version of this.

Adopted by

Most recently taken up by

buildomator/buildomatortheir own version, first seen Nov 4, 2026
kazzarahw/skillstheir own version, first seen Sep 30, 2026
jaskaranhundal/usap-skillstheir own version, first seen Sep 5, 2026
Shad0wMazt3r/The-Scaffoldingtheir own version, first seen Apr 24, 2026
ffsshhttiikk/opencode-agents-skillstheir own version, first seen Feb 28, 2026

Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
buildomator/buildomator★ 102same name
jaskaranhundal/usap-skills★ 4same name
Shad0wMazt3r/The-Scaffolding★ 3same name
ffsshhttiikk/opencode-agents-skills★ 2same name
kazzarahw/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- analyzeSkill
- competeSkill
- cryptoSkill
- flagSkill
- hereSkill
- miscSkill
- osintSkill
- pwnSkill
- reverseSkill
- statusSkill
- stegoSkill
- team-solveSkill
- webSkill

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.

0
Common
Most of the 4 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Use this command for challenges involving:
line 19
Very specific:
Read the JSON next_steps object to decide what to do:
line 47
Very specific:
All scripts produce === PARSED RESULTS (JSON) === sections.
line 90
Very specific:
When using /ctf-kit:team-solve with a forensics challenge, the lead spawns 3 specialists:
line 101

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

CTF Forensics

Analyze and solve forensics challenges.

When to Use

Use this command for challenges involving:

Memory dumps (.vmem, .raw, .dmp)
Network captures (.pcap, .pcapng)
Disk images (.dd, .E01, .raw)
Embedded/hidden files
File carving
Timeline analysis

Bundled Scripts

check-tools.sh — Verify required forensics tools are installed
run-binwalk.sh — Scan and extract embedded files. Outputs JSON with signatures, file types, and extraction suggestions.
run-volatility.sh — Run volatility3 plugins on memory dumps. Outputs JSON with parsed table data and suspicious process detection.
run-tshark.sh — Analyze PCAP files with protocol statistics. Outputs JSON with protocols, conversations, and HTTP/DNS/FTP suggestions.
extract-and-analyze.sh — Multi-step pipeline: binwalk extract → file type each → strings on interesting files → flag search. Chains extraction with analysis automatically.

Instructions

First check tool availability: bash scripts/check-tools.sh
For quick embedded file detection:
```
bash scripts/run-binwalk.sh $ARGUMENTS
bash scripts/run-binwalk.sh <file> --extract    # also extract
```
Read the JSON next_steps object to decide what to do:
- has_archives: true → extract with binwalk -e
- has_executables: true → analyze with strings/disassembler
- has_images: true → check with /ctf-kit:stego
For full extract-and-analyze pipeline (chains binwalk → file → strings):
```
bash scripts/extract-and-analyze.sh <file>
```
This automatically extracts embedded files, identifies their types, searches for flags and secrets, and suggests next skills to use.

For memory dumps:

bash scripts/run-volatility.sh <dump>                    # system info
bash scripts/run-volatility.sh <dump> windows.pslist     # processes
bash scripts/run-volatility.sh <dump> windows.netscan    # network
bash scripts/run-volatility.sh <dump> windows.cmdline    # commands

The JSON output includes parsed table data and flags suspicious processes.

For network captures:
```
bash scripts/run-tshark.sh <pcap>
bash scripts/run-tshark.sh <pcap> "http.request"    # with filter
```
The JSON includes protocol detection (has_http, has_dns, has_tls) with specific extraction commands.

Multi-Step Workflow

The scripts are designed to chain. A typical forensics workflow:

run-binwalk.sh challenge.bin → JSON shows archives inside
extract-and-analyze.sh challenge.bin → extracts and analyzes each file
Based on JSON suggestions, follow up with specific tools

Output Format

All scripts produce === PARSED RESULTS (JSON) === sections. Key fields:

Field	Description
`signatures`	Embedded file signatures found
`file_types`	Types of embedded files
`next_steps`	Boolean flags for what was found
`suggestions`	Actionable next commands

Team Roles

When using /ctf-kit:team-solve with a forensics challenge, the lead spawns 3 specialists:

Role	Teammate Name	Focus	Tools	First Action
File & Disk	`file-carver`	File carving, embedded data extraction, disk image mounting, deleted file recovery, filesystem analysis	binwalk, foremost, `scripts/run-binwalk.sh`, `scripts/extract-and-analyze.sh`	Run extract-and-analyze pipeline on all challenge files
Memory	`memory-analyst`	Volatility3 plugins, process trees, registry hives, command history, DLL injection, malware indicators	volatility3, `scripts/run-volatility.sh`	Run pslist, netscan, cmdline, filescan on memory dump
Network	`network-analyst`	Protocol analysis, stream reconstruction, credential extraction, DNS exfiltration, HTTP object carving	tshark, `scripts/run-tshark.sh`	Run tshark stats, extract HTTP objects, check DNS queries

When to broadcast

File carver: "Extracted N files, found image/pcap/binary inside" — other specialists claim the extracted file
Memory: "Found suspicious process PID with network connection to X" — network analyst filters for that IP
Network: "HTTP POST contains credentials / encoded data" — file carver or memory analyst cross-references
Any: "Found the flag" — immediate broadcast, all stop

Example Usage

/ctf-kit:forensics memory.raw
/ctf-kit:forensics capture.pcap
/ctf-kit:forensics disk.img

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free