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/artifact-routing/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/artifact-routing)<a href="https://agentmods.dev/skills/kismatkunwar89/savvydfir-mcp/artifact-routing"><img src="https://agentmods.dev/badge/skills/kismatkunwar89/savvydfir-mcp/artifact-routing/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/artifact-routing"><img src="https://agentmods.dev/badge/skills/kismatkunwar89/savvydfir-mcp/artifact-routing.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.00039 | $0.00907 |
| Opus 5 | $0.00019 | $0.00453 |
| Sonnet 5 | $0.00008 | $0.00181 |
| Haiku 4.5 | $0.00004 | $0.00091 |
Grade A, and why
artifact-routing 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Artifact Routing - Windows Forensics Mind Map
Execution Evidence
| Artifact | MCP Tool | What It Proves |
|---|---|---|
| Prefetch (.pf) | extract_prefetch() |
Binary executed, first/last 8 run times |
| Amcache.hve | get_amcache() |
Binary existed + SHA-1 hash (survives deletion) |
| ShimCache | run_analysis() on AppCompatCache CSV |
Binary existed on disk (not necessarily executed) |
| BAM/DAM | run_analysis() on registry export |
Binary executed by specific user (Win10+) |
| UserAssist | run_analysis() on registry export |
GUI program execution with count + timestamp |
Filesystem Evidence
| Artifact | MCP Tool | What It Proves |
|---|---|---|
| $MFT | extract_mft_timeline() |
All files that ever existed, SI vs FN timestamps |
| Deleted files | list_deleted_files() |
Files removed during/after attack |
| $UsnJrnl | run_analysis() on MFTECmd $J output |
File creation/deletion/rename journal |
| $LogFile | N/A (manual parsing) | NTFS transaction log |
Persistence Evidence
| Artifact | MCP Tool | What It Proves |
|---|---|---|
| Run/RunOnce | extract_registry_run_keys() |
Auto-start binaries |
| Services | summarize_evtx(channel="System") → Event 7045 |
New service installation |
| Scheduled Tasks | summarize_evtx(channel="Security") → Event 4698 |
Scheduled task creation |
| WMI | Manual: strings on OBJECTS.DATA |
WMI event subscriptions |
| Startup Folder | list_deleted_files() + extract_mft_timeline() |
LNK files in Startup |
Network Evidence
| Artifact | MCP Tool | What It Proves |
|---|---|---|
| Active connections | scan_network() |
C2 beacons, lateral movement, data exfil |
| DNS cache | run_analysis() on DNS cache export |
Resolved domains |
| Browser history | run_analysis() on SQLite export |
URLs visited |
| SRUM | run_analysis() on SRUM CSV |
Network usage per application |
Memory Evidence
| Artifact | MCP Tool | What It Proves |
|---|---|---|
| Process list | list_processes() |
Running processes from PEB linked list |
| Hidden processes | scan_processes() |
DKOM-hidden processes via pool tag scan |
| Code injection | detect_injection() |
PAGE_EXECUTE_READWRITE VAD regions |
| DLL list | list_dlls() |
Loaded DLLs per process |
| Credentials | Manual: vol3 windows.hashdump |
SAM hashes, LSA secrets |
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 · 67 lines · 39 tokens per session scan A 65301bf7f68a
artifact-routing is a skill published in the GitHub repository kismatkunwar89/SAVVYDFIR-MCP (4 stars, last pushed 3mo ago), licensed MIT. It adds 39 tokens to every session and 907 once invoked, about $0.0002 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…