Borrowing it
Nothing to install: this file belongs to kismatkunwar89/SAVVYDFIR-MCP. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kismatkunwar89/SAVVYDFIR-MCP/master/.claude/skills/investigation-workflow/SKILL.mdgit clone --depth 1 https://github.com/kismatkunwar89/SAVVYDFIR-MCPWrote 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/kismatkunwar89/savvydfir-mcp/investigation-workflow)<a href="https://agentmods.dev/skills/kismatkunwar89/savvydfir-mcp/investigation-workflow"><img src="https://agentmods.dev/badge/skills/kismatkunwar89/savvydfir-mcp/investigation-workflow/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/kismatkunwar89/savvydfir-mcp/investigation-workflow"><img src="https://agentmods.dev/badge/skills/kismatkunwar89/savvydfir-mcp/investigation-workflow.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00084 | $0.03842 |
| Opus 5 | $0.00042 | $0.01921 |
| Sonnet 5 | $0.00017 | $0.00768 |
| Haiku 4.5 | $0.00008 | $0.00384 |
Grade A, and why
investigation-workflow scanned grade A with 0 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 12d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Investigation Workflow - 5-Phase DFIR Methodology
This workflow is an investigation loop, not a checklist. The parent agent keeps the case hypothesis, decides pivots, writes the narrative, and analyzes large artifacts inline using the heuristic slice delivered in each tool response. Durable CSV/storage handles keep raw data out of context.
MANDATORY TOOLS (gate-enforced - report will not finalize without these)
The evaluate_ir_coverage_gate enforces tool coverage before generate_report. Enforcement strength varies by tool:
| Tool | Enforcement | Why it's mandatory | Common skip-pattern that we explicitly reject |
|---|---|---|---|
list_processes, scan_processes, scan_network |
Presence + opportunistic success (failed retry triggers re-run) | Universal memory baseline | Skipping any breaks DKOM detection |
extract_mft_timeline, summarize_evtx, extract_registry_run_keys, get_amcache, extract_prefetch |
Presence + opportunistic success | Universal disk baseline | "Memory was enough" reasoning |
sigma_hunt (Chainsaw rule engine) |
Hard success - requires exit_code 0, duration > 0, audit completion hash, AND durable Chainsaw output (output_path or finding_ids_generated populated) | Rule-based EVTX detection. sigma_scan is an internal anomaly post-processor - NOT a substitute. Run2 evidence: calling only sigma_scan produces zero rule-based detections. |
Calling sigma_scan and skipping sigma_hunt |
Conditional detect_injection, list_dlls, analyze_vss, extract_shimcache, extract_srum |
Triggered by psscan-only PIDs, network followup PIDs, anti-forensics signals | Same enforcement as their class above | Ignoring next_required_tool returned by earlier tools |
Enforcement specifics:
- Hard success (sigma_hunt): the gate's
_needs_sigma_hunt_runrejects failed, timed-out, zero-duration, or output-less runs. There is no presence-only fallback. - Presence + opportunistic success (everything else): the gate accepts the tool if its name appears in executions. BUT if any matching execution has populated success metadata (exit_code/duration_seconds) AND none of them succeeded, the gate demands a retry. This protects legacy fixtures while still catching new failures.
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.
- 12d ago First seen · 229 lines · 84 tokens per session scan A 1e977a072587
investigation-workflow is a skill published in the GitHub repository kismatkunwar89/SAVVYDFIR-MCP (4 stars, last pushed 3mo ago), licensed MIT. It adds 84 tokens to every session and 3,842 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
forensics-osquery
SQL-powered forensic investigation and system interrogation using osquery to query operating systems as relational databases. Enables rapid evidence collection, threat hunting, and incident response across Linux, macOS, and Windows endpoints. Use when: (1) Investigating security incidents and collecting forensic…
ir-velociraptor
Endpoint visibility, digital forensics, and incident response using Velociraptor Query Language (VQL) for evidence collection and threat hunting at scale. Use when: (1) Conducting forensic investigations across multiple endpoints, (2) Hunting for indicators of compromise or suspicious activities, (3) Collecting…
performing-cloud-forensics-with-aws-cloudtrail
Perform forensic investigation of AWS environments using CloudTrail logs to reconstruct attacker activity, identify compromised credentials, and analyze API call patterns.
Incident Response & Digital Forensics
IR playbook execution, evidence collection, forensic timeline analysis, memory forensics, and post-incident reporting following NIST SP 800-61 and SANS PICERL methodology.
collecting-volatile-evidence-from-compromised-host
Collect volatile forensic evidence from a compromised system following order of volatility, preserving memory, network connections, processes, and system state before they are lost.
incident-response-expert
Expert in security incident response, NIST framework, digital forensics, containment strategies, and recovery procedures. Use when the user mentions forensics, NIST, containment, recovery, or cybersecurity, or when the task involves NIST Incident Response Lifecycle, Incident Classification, Incident Response Workflow…