incident-timeline skillA
incident-timeline is agent-read markdown (skill) from gensecaihq/wazuh-autopilot: Build an ordered, evidence-linked incident timeline with first/last seen, dwell time and pivot points; use when a case spans multiple alerts, hosts or stages and needs a clear narrative..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Incident Timeline
A timeline turns a pile of alerts into a story a responder or executive can act on.
NIST SP 800-61r3 expects incident documentation of what happened, when, and how it was
detected; the timeline is the backbone of that record.
## Procedure
1. `get_case` — gather attached alerts, entities, findings, actions.
2. Pull supporting events for the key entities over the incident window
(`search_security_events`, `get_wazuh_alerts` filtered by agent/user/ip).
3. Normalize every timestamp to UTC ISO 8601. A Wazuh alert's `timestamp` is when the
manager processed the event. The original event time is in the log itself
(`predecoder.timestamp`, or the time at the start of `full_log`, or
`data.win.system.systemTime` for Windows). Use the event time when they differ by more
than a few seconds, and note clock skew or delayed delivery (e.g. an agent reconnecting
and flushing its buffer).
4. Order events; collapse repetitive ones ("38 sshd failures 09:02–09:12"). Wazuh
composite rules summarize bursts: one rule 5763 or rule 5712 alert stands for several
single failures (rules 5716, 5760, 5710), so count the underlying failures, not the
composites.
…Read the whole file at its exact version.
How to install
mdr add gensecaihq/wazuh-autopilot/incident-timeline@v1.1mdr add gensecaihq/wazuh-autopilot/incident-timeline@sha256:8afb3a9e6485519ePin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_io3cjik5fvizq36p)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4053 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
gensecaihq/wazuh-autopilot · 57 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_io3cjik5fvizq36p GET https://markdownregistry.com/api/v1/resolve?ref=gensecaihq/wazuh-autopilot/incident-timeline GET https://markdownregistry.com/api/v1/blob/8afb3a9e6485519ecb338c61671bf00e8647d9631366b95c44a0dd85de7786f0
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.