More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Digital Forensics: Evidence Discipline for Incident Response

    1

    Conduct authorized forensics with evidence discipline — preserve first, build the timeline, then analyze memory, disk, and network — and report what happened with the unknowns stated, not invented.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Digital Forensics: Evidence Discipline for Incident Response

    Digital Forensics: Evidence Discipline for Incident Response

    Example session with this skill installed

    A server is flagged for unusual outbound traffic at 3 AM. We have a disk image and a memory dump. Walk me through the investigation with evidence discipline.

    • Read your context and instructions
    • Compiled the digital forensics

    Investigation — the 3 AM server (preserve → timeline → correlate)

    Preservation first: disk image hashed (SHA-256 recorded with the acquisition command, timestamp, and timezone); memory dump captured before anything else; images mounted read-only; chain-of-custody log opened. Nothing was analyzed on an original.

    Timeline built before artifact-chasing: the filesystem timeline shows a cluster at 02:47–03:05 — a binary written at 02:49, a new service installed at 02:51, a scheduled task created at 02:53. Event logs show a logon at 02:47 from an internal jump host unused for six months.

    Memory (Volatility, profile verified first): the new service is running, its command line points at the 02:49 binary, and it connected to an external IP at 02:55 and every 10 minutes after. Network: PCAP shows 40 MB leaving to that IP between 02:55 and 03:05, then beaconing. The 02:51 launch and the 02:55 connection are one finding, not two.

    IOCs with context: binary hash, external IP and domain, service name, scheduled task name, mutex — each annotated with why it is malicious (installed minutes before exfiltration; beaconing interval matches the connection pattern). Report: what happened in order, with evidence — and the unknown stated plainly: how the jump-host credential was obtained is unknown and is the open question for the next phase. Rubric score: 7/8.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Forensics is the opposite of exploration: every action must preserve the evidence it examines. This skill runs investigations in a fixed order — authorization and case setup, preservation (SHA-256 hashing, read-only mounts, chain-of-custody log, volatile evidence captured early), timeline construction before any artifact-chasing, memory analysis with Volatility, network evidence from PCAP correlated with the host timeline, and IOC extraction where every indicator carries its context: why it is malicious, not just that it appeared.

    A worked example investigates a server flagged for unusual outbound traffic: a 02:47–03:05 activity cluster, a new service, a scheduled task, a process launch at 02:51 and a first connection at 02:55 treated as one finding, 40 MB exfiltrated, beaconing every 10 minutes — and the open question (how the jump-host credential was obtained) stated as unknown rather than invented. A rubric gates the report: below 6 out of 8, the investigation produced leads, not findings.

    • It assumes authorized work: without authorization and scope, the skill stops before acquiring anything.
    • Memory analysis shows the machine's state at capture, not at the event — a dump taken hours later cannot speak for the event window.
    • An artifact that never existed on the target OS version is not evidence of absence; the skill requires knowing what should exist before concluding from a gap.
    • A finding resting on a single artifact is a lead, not a finding — corroboration is required, and the rubric enforces it.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 3 days ago

    Permissions

    No special permissions declared or detected

    Listed3 days ago

    What's inside

    Frequently Asked Questions

    Because a timeline turns isolated findings into a story and tells you where to look next. Chasing artifacts without one is wandering the image, finding interesting things, and building no case. The anomalies in the timeline — the 20 minutes where everything happened — are what the drill-down follows.

    It means the report states plainly what could not be determined — how a credential was obtained, what left in an unlogged window — instead of inventing a plausible story to fill the gap. Invented certainty is worse than a gap, because the gap gets investigated and the invention gets believed.

    Yes — the same discipline applies: preserve, timeline, memory, network, IOCs with context. The report shape stays the same; the artifacts differ. The one thing that does not change is the order: preserve first, analyze second.

    New in Security